June 14, 2007 at 10:14 am
Hi All - I'd really appreciate a heads up from more knowledgable DB admins....
Due to two systems in my organization needing the SQL Server 2005 back end because of going to a dot-net front end, the current SQL Server 2000 box in use is going to have a side by side install of SQL Server 2005.
I would really like to understand what I am most likely going to need to change in order to cope with the 2000 install no longer being the default instance.
Right now, when I use query analyzer I just pick the server name off the list to connect to the DB. On my DTS packages, I've got the same "SQL Server" list that only has the server name linked to my connection objects.
So I'm anticipating that I'll need to re-link all of the DTS packages to what I think will become a named instance of SQL Server 2000. I'd appreciate a heads up on what that will involve and how I connect up once my current DB is not the default instance on my SQL box. I don't have enough time to test all the current DB features and the reporting services interface in use under 2005 in order to make the transition to 2005 simultaneously.
thanks for any advice..... Mark
June 14, 2007 at 1:12 pm
- third party applications that have config files
- third party applications that have hard coded default instance code
- any external vbs (or other) scripts with path references
- anyone using EM or QA will have to re-register their servers
- not sure about shared folders or not...
hope that helps!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply