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 |
|
MBeal
Posting Yak Master
110 Posts |
 Posted - 2003-04-04 : 09:35:36
|
| Some time ago our company purchased some new equipment and we decided to upgrade from SQL7 to SQL2000. We contracted another company to assist us with this installation. They suggested that we just install another instance of SQL instead of doing a clean install. When we look at our SQL Server Group in Enterprise Manager, the server name has a slash (example: RS035\RS035 (Windows NT)).One of the main reasons for the switch is that we want to introduce log shipping, and unfortunately because of the instance issues, we have run into problems that we cannot overcome.My concern is that I need to make certain everything continues to run properly after we make the switch. Primarily SQL Agent Jobs, DTS packages, but also various other items where paths have been entered to include the instance (RS035\RS035) (for example Data Junction is used to import text files into a database for reporting purposes).Is there any source of information that can assist me in this process. Recommendations or suggestions that could help me along the way? The last thing I want to do is make the switch and have everything stop working all at once. I really don't know where to begin. Should I be scripting everything out? This seems like such a huge endeavor and I am fearful about making a mistake?MBeal |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2003-04-04 : 10:15:40
|
| The best way to prevent mistakes and things not working in a case like this is to test and document the change process until a monkey could perform the conversion following your documentation. That way you know you're not missing anything when it comes time to do the real conversion. Moving from a named instance to default instance or an instance with a different name is just like moving to a new server. You'll have to be aware of any pieces of the server that point to the server name and change them accordingly.Jeff BanschbachConsultant, MCDBA |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-04-04 : 12:50:34
|
| MBeal,What problems are you encountering with the named instance? We use log shipping here over named instances, and we have zero problems with it. Just as efelito said using a named instance is no different than using the default instance on a different server.Tara |
|
|
|
|
|
|
Instances of SQL