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 |
|
sumwanlah
Starting Member
43 Posts |
 Posted - 2002-07-15 : 12:03:27
|
| I know both SQL7 and SQL2k can co-exist. Of course only one can run at a time. Also you install SQL2k as a named instance, then convert all SQL7 databases to SQL2k.I'm running many web apps connecting to SQL7 and all these are connected to the server via DSN connections.When I do switch to SQL2k, do I have to change all DSNs to point to the named instance? Say the original SQL7 is called 'ADAM', and say the SQL2k is called 'ADAM\EVE', does this mean that 'ADAM\EVE' will be the new server that the DSNs should point to?I really wonder if there is a way to leave the DSNs as they are right now, with the databases upgraded to run in SQL2k, with the option of falling back to the default SQL7 instance...In case I've lost you guys since the first word, all this will be one a single box of course...------------------------What goes around...? Is the belt around my waist! |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-07-15 : 12:07:17
|
| No, you MUST change the DSN to point to the named instance. The only way to have SQL 2K use "ADAM" is to re-install it as the default instance and give up the 7.0 instance completely. |
 |
|
|
sumwanlah
Starting Member
43 Posts |
Posted - 2002-07-16 : 02:25:21
|
| Ok... That's sounds fair enough... Cos, I'm actually very ready to do an in-place upgrade. Just that my mgmt do not really understand a couple of things. They are concerned that by installing 2k over 7, many, many things will change.My plan is, just in case I get shot down by these people, is that if ever the in-place upgraded server is ever riddled with probs, then I will just uninstall 2k, reinstall 7, then restore all the backed-up databases. This is fine right?------------------------What goes around...? Is the belt around my waist! |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-07-16 : 10:07:04
|
| Well, you shouldn't even consider migrating to SQL 2000 if you haven't done extensive testing to see if there are going to be problems. If there's any question in your mind, or your boss's mind, you'd better clear them up before you go forward. Test everything before you migrate.Having said that, if it does fail for some reason, I don't see any major problems with wiping out SQL 2000 and do a fresh install of 7.0. The big thing to do is make sure you get the service packs installed RIGHT AWAY after the reinstall. |
|
|
|
|
|
|
|
|
DSN Settings for SQL2k Named Instances