The following command line options are available for use with dbdeploy.
Short | Long | Description | Example |
c | ConnectionString | The connection string that will be used to connect to the database to evaluate dbdeploy scripts. | DatabaseDeploy -c "Server=localhost; Database=MyDatabase; User ID=MyUser; Password=MyPassword; Trusted_Connection=False; Encrypt=True; Connection Timeout=30; " |
d | DatabaseManagementSystem | The database to use. Currently, only mssql is supported. | DatabaseDeploy -d mssql |
p | DatabaseScriptPath | The path where database scripts can be found. | DatabaseDeploy -p "c:\temp\scripts" |
n | LastChangeToApply | The number of the last script to apply to the database. Defaults to 0, or all available scripts. | DatabaseDeploy -n 45 |
f | OutputFile | The name of the file that will be created for the updates that need to be run. Defaults to DbDeploy | DatabaseDeploy -f "c:\temp\update.sql" |
r | Recursive | Whether or not the path should be crawled recursively looking for database scripts. | DatabaseDeploy -r |
o | RootDirectory | The path where dbdeploy should start running. | DatabaseDeploy -o "c:\temp" |
l | ScriptListFile | The file that will contain a list of all of the scripts found. | DatabaseDeploy -l "c:\temp\scripts.txt" |
w | SearchPattern | The wildcard pattern that should be used to match for scripts. | DatabaseDeploy -w "*.sql" |
u | UndoOutputFile | The file that will contain undo scripts. | DatabaseDeploy -u "c:\temp\undo.sql" |
t | UseTransactions | Whether or not transactions should be used. Personally, I'd put them in the script. | DatabaseDeploy -t |
s | Schema | The schema to use for scripts. | DatabaseDeploy -s dbo |
g | ChangeLog | The name of the ChangeLog table. | DatabaseDeploy -g changelog |