January 11, 2009 at 1:30 pm
Hi,
we are planning to do upgrade from 2000 to 2005 and we want change databases names.can we change the daatabses names before upgrade or after upgrade? and before changing the database names what are the things to consider?
January 11, 2009 at 2:17 pm
It doesn’t matter if you’ll change the database’s name before or after the upgrade, but why do you want to change the database’s name? If you’ll change the databases’ names you have to make sure to modify all the places that reference the databases such as connection strings, SSIS packages, scripts etc’.
Also today I would upgrade to SQL Server 2008 and not to SQL Server 2005.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
January 11, 2009 at 4:35 pm
I agree with the 2008 suggestion. Don't upgrade to 2005. 2008 is exactly the same process and the compatibility is virtually the same.
As far as a database name change. It will really depend on how strict your coding standards have been in your applications. If you have a single connection string in each application and no developer has used a 4-part name in a query, you may not have many issues. On the other hand, if you have a lot of applications using ODBC connections, config files, and hard-coded connection strings, you may have a lot to change.
The only thing you can do with a database name change is test everything. I would recommend you test the name change in the same environment you are using to test the application with SQL 2005 (or 2008 now, hopefully). If you don't have this environment - get one before doing any kind of upgrade and test the application. You are very likely to find a surprise or two - don't skip the testing step.
January 11, 2009 at 9:41 pm
In my openion, it doesn't make much differnece if you cahnge before or after the upgrade.
On Database side it's very easy to change the dbname. But more work needs to be done from Application point of view.
Most important thing is you need to stimulte the same test environment as production to eleminate the probable issues on the database. You need to thoroughly test the Appliaction after the rename.
It is not a fun to rename production database. 😛
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
January 12, 2009 at 3:59 am
I would do the database name change AFTER the upgrade, particularly if this is a side by side upgrade, as it would make the backout procedure easier.
---------------------------------------------------------------------
January 12, 2009 at 4:03 am
I would check first all the reference and then test it in a test environment which you have now, then it really dosnt matter when u rename, just making sure that it does not break any links with applications and other databases is the main thing to consider before name change.
January 13, 2009 at 10:25 am
When you say 'upgrade' what do you mean?
SQL2005( level 80 Compatibility) = SQL2000 behaviour?
or
SQL2005 ( level 90 Compatiblity) = Full on SQL 2005 ?
Changing the name may be the least of your woes.
--Shaun
Hiding under a desk from SSIS Implemenation Work :crazy:
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply