Andy Leonard has a four-parter four us on database solutions in SQL Server Management Studio. Part one provides an introduction:
I like Microsoft Visual Studio a lot. I know some members of the team that developed Visual Studio, and they are scary-smart individuals who have forgotten more about developing software than I will ever know.
For some reason, I am not fond of SQL Server projects in Visual Studio. I believe the reason is that I am not familiar with the template. Please note I used the word fond intentionally. It’s an emotion. In this case, it’s all about me. I believe my emotion would change if I took the time to learn more about the Visual Studio SQL Server project template.
I continue to attempt to learn VS database projects. In the meantime, I prefer SQL Server Management Studio solutions.
One solution is to add instrumentation to T-SQL scripts. I personally like to write T-SQL scripts that idempotent (a fancy way to describe “re-executable with the same results”). One way to write idempotent T-SQL is:
1. First check for the current state
2. Provide feedback (instrumentation) on the status
3. Provide more feedback on actions driven by the status (yep, more instrumentation)
Click the “New Query” button in SSMS and add the following T-SQL:
Note the DDL to manage stored procedures is very similar to the DDL for managing views.
If all goes according to plan, the first execution of the s.i DDL T-SQL statement should generate the following messages:
Andy also shows how to use SQLCMD to create a proper deployment script.