I am currently evaluating DBGhost for our development effort. I am having issues right at the start regarding our use of sequences. Any attempt to get the GUI to do anything at all results in an unsupported object type (SO) exception. I had a brief email exchange with Jon Woolgar last week during which he mentioned a fix for this. I would like an ETA please.
Also, we are highly interested in the command line interface. The documentation on this seems to be sparse. Running the ChangeManagerCmd program with no parameters on the line yields a usage statement which mostly seems to ask for connection credentials. It also refers to a configuration file, alternately referred to as sessionSettings.xml or sessionfile.xml. I can find no documentation nor example of such a file.
For closure. The SO issue was a result of new code that handles 2012 sequence objects. One piece of code accidentally looked for SO's even when connected to earlier SQL versions. This was fixed just after it was found.
Regarding the commandline help issue The help file's command-line topic contains this extract:
Generic Options The following is the generic way to call all the command line executables (except the installer EXEs created by Packager Plus):
The settings file is created by using the appropriate GUI and selecting "save settings" at the end of the wizard. This XML file contains all of the options chosen during the GUI session and can also be hand edited to suit different scenarios. For example the server name and database name settings are likely candidates for amending depending on the environment.
Example "c:\program files\db ghost\ChangeManagerCmd.exe" "c:\my files\DatabaseUpgradeSettings.xml"
ChangeManagerCmd Specific Options The following parameters can be set in the ChangeManagerCmd
/treatwarningsaserrors By default, the return code (errorlevel) returned by the ChangeManagerCmd.exe is 0 even if warnings are issued during the process. This option makes the tool return 1 if any warnings are issued. /silent Suppresses all console output, except the completion message. /showerrorsandwarningsonly Suppresses all console output, except for warnings and errors and the completion message. The /silent flag over-rides this flag. /scriptserver /buildserver /sourceserver /targetserver Specifies the server name for the relevant action. NOTE: the /buildserver setting overrides the /sourceserver setting when both are specified. /scriptdatabase /builddatabase /sourcedatabase /targetdatabase Specifies the database name for the relevant action. NOTE: the /builddatabase setting overrides the /sourcedatabase setting when both are specified. /scriptuser /builduser /sourceuser /targetuser Specifies the user name for the relevant action. NOTE: the /builduser setting overrides the /sourceuser setting when both are specified. if this option is not specified the credentials from the XML project file are used instead. /scriptpassword /buildpassword /sourcepassword /targetpassword Specifies the password for the relevant action.
Example "c:\program files\db ghost\ChangeManagerCmd.exe" "c:\my files\DatabaseUpgradeSettings.xml" /treatwarningsaserrors /silent