We wanted to allow our Wix MSI installer to specify connection string and credentials, and needed some way to pass these into the scripts, so once again, using tokens and some conditional logic.We wanted to maintain a history of what scripts were executed and when.We found if you didn't wait a few seconds after creating a new databases via a script, the SQL Server might fail sometimes (because it hasn't had time to create the db files) when it went on to create tables, etc. Execution of some scripts requires a wait period after execution, e.g. FileMaker 10 was released on January 5, 2009, before that years Macworld Conference & Expo, and offered scripts.So our scripts use a token and based upon the db choice replaces with the correct type. 2005+ have nvarchar(max), whereas 2000 only supports ntext. We need to support installations on SQL Server 2000, 20, and there are changes to data types between versions, e.g.Multiple output options Multi-database processing Visual object filtering. It also ensures scripts are only applied once. Script both objects and data from various databases simultaneously. We ended up using a combination of SSMS script generation to extract schema and data, and then use our own database tool which allows keyword parsing and token based replacement in scripts.

Script database sql