Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2005-04-18 : 07:12:49
|
| Todd Raymond writes "In our company, we have 4 application developers and one DBA. We're trying to figure out the best way for us to work together with regards to our SQL Server Development. Using Vault or SourceSafe, we know how to develop the application code, even stored procedures can be dealt with using source control. Where we are stumped is this: How do we deal with DDL Changes in a distributed team environment ( no offices, we all work out of our homes).Are there any best practices with regards to source control and versioning of a Database?Thanks in advance for your thoughts.Todd A. Raymond" |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-18 : 08:29:09
|
| http://www.nigelrivett.net/SQLServerReleaseControl.htmMeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-04-18 : 09:36:01
|
| You can script changes "after the fact" as Derrick has described.We script all DDL changes as we go along (we often use the Enterprise Manager "Design Table" facility, but we always push the "Make me a script button" and never the "Save changes" button.We name each script PATCH_01.SQL ... and then once the Dev. is completed we can run them in turn on QA / Production databases when appropriate.Kristen |
|
|
|
|
|
|
Sql Server Development in a Distributed Team Environment