Customizing Your Workflow Studio Database
Workflow Studio creates a database automatically as part of the configuration process, but if you are using a database server where your database administrator does not provide the permissions to create the database then you will need to have them run the configuration or provide them with the SQL scripts to manually create the database.
Workflow Studio SQL Scripts
When Workflow Studio is installed there is a sub-folder created in the "%Program Files%\Citrix\Workflow Studio" called SQLSetup. In this folder are all the scripts that are used to initially create the database, batch files that will create or remove all the tables, and a PowerShell script that will generate customized versions of these files with a different database name.

Generating Custom SQL Scripts
The default scripts are designed to create a database named WFDB. If you want to create a Workflow Studio database with a name other than WFDB you can run a PowerShell script we provide.
The syntax for running the PowerShell script is (NewDatabaseName should be the customized database you would like to use):
cd $ENV:SystemDrive"\Program Files\Citrix\Workflow Studio\SQLSetup"
.\SetDBName.ps1 NewDatabaseName
This will result in new database scripts generated in the folder that you can run against your SQL Server to create a custom database.

Running Custom SQL Scripts
The syntax for running the SQL scripts is (DBServer should be the server name of your SQL Server):
Install.NewDatabaseName.bat DBServer
Using Your Custom Database
Once the database is configured and your SQL administrator has given you access, you will be able to login to Workflow Studio.

Comments (1)
Jan 03, 2011
Ole Kristian Lona says:
There seems to be a small error in the script, as it also changes the only line ...There seems to be a small error in the script, as it also changes the only line in the table called "Version". Here, it changes the Component name that MUST be set to "WFDB" to whatever your new database is called. This is quite simple to just change back in the database, but should probably be corrected in the script?
Regards,
Ole Kristian