Hi all,
I am a developer new to working with SQL Server. I am on 2008, and have created n number of stored procedures. Each stored procedure has been put in its own file on my system, and stored in source control. This is so that, as I continue to update the system, I can just grab the one stored procedure I am working on updating, run it to update it in the database, and then commit my changes.
The problem is that when the DBA makes changes to the database and I run his script to drop and recreate mine accordingly, I lose all of my stored procedures. I have looked online for a way in MS SQL Server to just have one master .sql file that I can call that will call all of the others and recreate all my procedures in the database. My search has been fruitless so far. It almost seems like there is no way to do this. Am I correct? Please someone tell me I've missed something, and then it would be great if you could fill me in on what it is I've missed.
Thanks for your help
I am a developer new to working with SQL Server. I am on 2008, and have created n number of stored procedures. Each stored procedure has been put in its own file on my system, and stored in source control. This is so that, as I continue to update the system, I can just grab the one stored procedure I am working on updating, run it to update it in the database, and then commit my changes.
The problem is that when the DBA makes changes to the database and I run his script to drop and recreate mine accordingly, I lose all of my stored procedures. I have looked online for a way in MS SQL Server to just have one master .sql file that I can call that will call all of the others and recreate all my procedures in the database. My search has been fruitless so far. It almost seems like there is no way to do this. Am I correct? Please someone tell me I've missed something, and then it would be great if you could fill me in on what it is I've missed.
Thanks for your help
Comment