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 |
|
chih
Posting Yak Master
154 Posts |
 Posted - 2008-01-09 : 01:13:11
|
| Hi everyone,I really need your help!! How you manage development server and production server?My current situation:Our programmers develop new Stored Procedures on development server. When all testing is completed, we then deploy them to production server.Challenges:Programmer (Eric) modified a Stored Procedure (SP_1) on development server. He did not deploy it on production server because SP_1 is not completed yet. Programmer (John) got request and needed to modify SP_1 on development serverSo now there is a problem in SP_1. if John deploy SP_1 on production server, it will overwrite the current version and cause errors.Anyone can solve this problem? Will it be better if we have another testing server?many thanks |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2008-01-09 : 03:09:43
|
| Not necessarily an extra server but it needs to have different uses.Consider sp1 a major release and your other update an emergency release.Both should be tested so your test system should be able to be set up to mirror the live system and then the release applied (the emergency release is still a release so should be dealt with in the same way but with abbreviated requirements).Keep all the releases in your source control system. This means the release to update the live system and the base code structure which will give you the live system (this can be scripted after the release is made in test).Now the emergency release just goes through.You will have 3 (at least) source control environments live, test and dev.The release scripts are extrated from the source control system - i.e the test release is extracted from the dev source control system. This prevents anythiong being released which hasn't gone though source control.This means that when the SP is updated in dev it will be noticed that it is already locked out and someone is working on it.At this point the problem will be dealt with - best is to just inform the developer, get them to release the lock, update the module and leave the developer to incorporate the changes. (Note this may be completed after the emergency release).Another option is to branch in the source control system (most allow this but it is to be avoided if possible) then deal with the issue later. This is common if the developers don't work for the same department or there are political issues with development project time/effort being impacted by support or requirement changes.Note you will have the same issue if there are two major developments going on at the same time impacting the same code - it's common in this situation for the planned schedule for those releases to change.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
chih
Posting Yak Master
154 Posts |
Posted - 2008-01-09 : 18:52:33
|
| Thank you nr. It is really help. The problem is we don't have source control.Any recommendation for the source control tools?Kind Regards, |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-09 : 22:51:15
|
| You can google it. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2008-01-10 : 03:19:17
|
| I've used SourceSafe and Subversion (with TortoiseSVN client) recently - both are fine.I used PVCS a long time ago.Any source control system should be ok as long as it's configured properly.Make sure the item has to be checked out to make changes.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
MuadDBA
628 Posts |
Posted - 2008-01-10 : 12:14:32
|
| Microsoft Team Edition for SQL Server comes with source control embedded, I think.Also, there is SourceIntegrity. |
|
|
|
|
|
|
How to manage development and production servers??