eoincampbell / parachute Goto Github PK

would need to ignore connection string initial catalog and connect to Master for create + any other server level roles/privileges/schemas etc...

No 3rd Party Requirements.

• Specify Server
• Specify Database
• Specify User
• Specify Password

OR superceded by

• Specify Connection String.

The folder structure should be configurable based on some configuration/xml file which dictates the order/depth through which scripts should be executed.

A standard example should be provided

Ability to handle GO; statements

Ability to handle SQL Comments in code blocks

Information Feedback for PRINT & ErrorCodes <= 10

Exception Thrown on ErrorCodes >10

Tracking table required to monitor scripts.

Includes Major, Minor, Build, Rev numbers.
Message
Date Applied to Database

Create a Console Application - parachute.exe

Possible Solution to explore.

Each script location as well as having a path (which could be relative or absolute) would also have a "label" or "name"

The path used as the hash should be the name, followed by the last folder name of the curent scriptlocation.

e.g.

<scriptLocation 
    name="SPROCS" 
    path="..\scripts\stored procedures\" 
    recursive="true" 
    runOnce="false" />

In this situation, the path contains the following files.

• D:\Work\Install\scripts\stored procedures\dbo.GetFoo.sql
• D:\Work\Install\scripts\stored procedures\dbo.GetBar.sql
• D:\Work\Install\scripts\stored procedures\borkSchema\bork.AddFoo.sql
• D:\Work\Install\scripts\stored procedures\borkSchema\bork.AddBar.sql

these would be logged with the paths

• SPROCS\stored procedures\dbo.GetFoo.sql
• SPROCS\stored procedures\dbo.GetBar.sql
• SPROCS\stored procedures\borkSchema\bork.AddFoo.sql
• SPROCS\stored procedures\borkSchema\bork.AddBar.sql