SQLS Description

If you start the exe you should see something like this:

On the left you have some options, in the middle you will have a list of scripts and finally some buttons to organise the order of these scripts.


The options you can set are:
  • Change No This is the OVSC change no
  • Description This a brief description of the change i.e. (DS2699 IFRS Colorado)
  • SQL Server This is the SQL Server the scripts will be applied against
  • Database This is the database on the above server that the scripts will be applied against.
  • Input Path This is the source of all the scripts
  • Output Path This is where the scripts and bat file will be copied to.
  • Clear Output Folder Clears the output path folder of all files.
  • Order by Prefixes/Extensions. When filling the list, it will order then items by the following:
  • tbl*, .tab Table Changes
  • idx*, .idx Index Changes
  • data*, .dat Data Input/Delete
  • fn*, .udf Functions
  • vu*, .viw Views
  • sp*, .prc Stored Procedure
  • job*, .job SQL Agent Jobs
  • .usr SQL Database Users
  • .lgn SQL Logins
  • x* Executes (i.e. running procs/tidy ups after imp)
  • Use Input Disables the ‘Output Path’, and ‘Clear Output’ folder options, the bat file will be created in the Input Path and no copying will be done.
  • Bare Disables the ‘Change No’ and ‘Description’, and the resulting batch file will have no user friendly prompts/info. Enter a change no first, as the batch file uses this as part of the resultant error text file.
  • Use SQL 2000 or SQL 2005/8 This generates the script using osql (for 2000) or sqlcmd (for 2005/8)

Once the above has been set properly, the ‘Get .SQL Files’ button will fill the middle list box with all the scripts it finds.

The ‘All’ button checks all the items; ‘None’ un-checks them all. The ‘up/down’ arrows reorder the items i.e. if you want to avoid SQL server complaining about dependant procedures.

‘View’ shows a syntax highlighted copy of the script.

‘Save’/’Load’ saves/loads the settings and the list to/from an XML file.

Finally ‘Generate’ will generate the batch file.

Last edited Jun 3, 2010 at 7:43 AM by cjb110, version 4


No comments yet.