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 |
|
volliefireman
Starting Member
9 Posts |
 Posted - 2003-02-10 : 11:31:11
|
| After looking thru the forum, and other places on the internet, I have not found answers to my questions, so here it goes:1. After migrating from SQL 7 to SQL 2000, and assuming there is no code changes to SP, is there a problem moving back to SQL 7 should the need arise?2. We have our SQL 7 in a NT 4 Clustered Environment. Due to the large volume of connections to our server, we need to keep the same name for our SQL 2000 virtual server. After migrating the databases, can we un-cluster the SQL 2000 and recluster with the old SQL 7 name? What problems will this cause, if any?3. If we must change to a new server name, can anyone recommend a way of changing various client ODBC to the new name with a minimal of problems?Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-10 : 12:17:29
|
| I don't know the answers to your first two questions, but the answer to the third question is yes. You can easily change the server name in the ODBC connection. You would just have to deploy a registry modification. Look in the registy under Software\MS...ODBC Data Sources (I believe). You will find your DSN. You can easily modify it here, then export the key value and then deploy it to your clients. If you need help on this, just let me know and I'll provide more details. |
 |
|
|
|
|
|
More Migration Questions