tymberwyld (2/10/2008)
Ok, so last post (I hope). Would someone tell me how to simply add a Stored Procedure script to an existing project and manage it within the project (which includes scripting it to the dev database as many times as needed)?
A few options:
1. Copy and paste from wherever the sproc has been written
2. The sproc is written in the dev database and gotten into the project using a schema compare
3. The sproc is written in the datadude project and gotten into te dev database using a schema compare
tymberwyld (2/10/2008)
Assuming only one Proc has changed, do you still have to perform a diff just to move the changes to say Staging / Production?
Presume by "diff" you mean a schema compare? If so, the answer is 'yes'. I don't see it as a problem that only one object had changed. Here's a tip for you: Don't close down the schema compare window when you have finished propogating changes to somewhere. If you leave it open you can just keep hitting refresh each time you need to propogate some changes and it remembers how you previously set it up i.e. It you don't have to go through setting things to be ignored because you've already done it. I fid this to be a huge time saver.
Another tip: filter the results of the schema compare to show changes only (there's a filter button near the top left of the schema compare window)
-Jamie
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson