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 - 2003-02-06 : 08:34:44
|
| Terry writes "This question has more to do with looking for recommendations...of course the actual rename is the easy part. I've searched quite a bit on the web and can't find an article. SQL server version: 2000 - 8.00.534 here's the scenario: we have an enterprise-wide application already in place using 81614616 KB disk space [from sp_spaceused minus the unused portion], critical deliverables scheduled weekly, etc.the DBA wants to rename the production database in the next release scheduled for June 2003 (large amount of code, basically a re-write of the legacy system to be ported over). In the meantime, they have already renamed the database on our DEV and TEST servers. my argument is that they should schedule a separate release just for the production db name change to mitigate risk and ferret out any db objects that may be referencing the old name. but I'm looking for "official recommendations" or a list of possible risks and things that may break the release. I'm a developer with previous DBA experience looking for evidence to back up my point of view.if this is something you could provide, I would appreciate it." |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-06 : 11:49:03
|
| Well you have already provided the evidence by saying to mitigate risk and ferret out any db objects... |
 |
|
|
|
|
|
renaming a production database