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 |
|
tahoe3
Starting Member
1 Post |
Posted - 2002-07-29 : 15:51:19
|
I have recently purchased SQL 2000. I need to use SQL 2000 for a new application and want to migrate SQL 7 databases at a later time. Is there any problems with this?<edit>yes sir, Master Page, it has been so moved at your command</edit> Edited by - robvolk on 07/29/2002 16:44:30 |
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-07-29 : 16:08:26
|
| This is in the wrong forum. Move it to the Administration forum....Jay White{0} |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-07-29 : 18:11:07
|
quote: As far as having SQL 2000 and SQL 7.0 on the same machine, yes, you can do it, but only one of them can run at a time
Are you perhaps thinking of SQL7 and SQL 6.5 ? SQL7 and SQL2000 coexist quite happily on the same server and run quite happily at the same time. Most of our servers have a SQL7 instance that is winding down its life as we move everything across to 2000. SQL7 should be installed first and become the defacto default instance (although it has no concept of instances) and SQL2000 should be installed as a named instance. Whilst this is fine for DEV and QA servers, production servers should be version specific as the 2 instances will compete with each other for server resources. Having said that, depending on the relative usage of the 2 instances they can coexist quite happily in a production environment - our intranet production db server runs SQL7 and SQL2000 quite happily.HTHJasper Smith |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-07-29 : 20:32:25
|
| #@$!%#$@! forgot about named instances. Never actually ran both of them together either. Thanks! |
 |
|
|
|
|
|