October 25, 2007 at 7:48 am
Hello all,
I have a server that has Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2) and is also running a local instance of Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2). I would like to know if it is possible to either upgrade the standard sql2K server to MSSQL 2005 or unistall it and then install SQL2005. I am not sure if one can run both MSDE and 2005 on the same server? Do you guys have any ideas?
Thanks in advance.
Jerry
October 25, 2007 at 7:57 am
Yes, you can upgrade your 2000 SE instance to 2005 EE, DE or SE...and also you can have multiple instances of sql server running a single box....
--Ramesh
October 29, 2007 at 7:30 am
I just hit this myself. I need to maintain my MSSQL2K install and run MSSQL2K5 simultaneously on the same box. The MSSQL2K5 sees the MSSQL2K installation and wants me to run the install from the commandline with the SKUUPGRADE flag, but never gives me the option to just install 2K5 completely separately. How is this done?
Thanks,
Bret
October 29, 2007 at 7:39 am
Bret A Schuhmacher (10/29/2007)
I just hit this myself. I need to maintain my MSSQL2K install and run MSSQL2K5 simultaneously on the same box. The MSSQL2K5 sees the MSSQL2K installation and wants me to run the install from the commandline with the SKUUPGRADE flag, but never gives me the option to just install 2K5 completely separately. How is this done?Thanks,
Bret
Which edition of SQL you are working with?
--Ramesh
October 29, 2007 at 7:43 am
I've got MSSQL2K (v8.00.2039, w/SP4) installed and I want to install MSSQL2K5 Enterprise (or any other edition, if another works better) alongside the 2K version so I have complete access to both. I'm doing this on my laptop running XP Pro.
Thanks,
Bret
October 29, 2007 at 7:48 am
Would it be easier/better to just run MSSQL2K5 in a VMWare instance? I won't have my MS Dev Studio available (I'm trying to develop a UDF in .NET for 2K5), but I could make do.
Thanks,
Bret
October 29, 2007 at 8:01 am
When exactly you're encountering with this (on what page)?
--Ramesh
October 29, 2007 at 8:05 am
I'm just going through the 2K5 install and it doesn't ask where to put the 2K5 server or any files - it just assumes I want to upgrade my current install.
October 29, 2007 at 9:53 am
SQL Server Installer, by default, installs in the windows drive....(That doesn't mean, the installer will upgrade the existing instance).
Just go through the installation from the start, when you reach the instance selection/upgrade selection page you have to select named instance ( in case if the existing instance is the default one) and type the name of the instance and proceed further with the installation. Thats it.
--Ramesh
October 29, 2007 at 9:54 am
If you're doing both installs as "default" instances - it's inferring from the name that you're asking it to upgrade. Meaning you can only have one default instance of SQL server per machine, no matter which version it is.
Use distinct instance names - and you should have no issues with maintaining both versions on a single machine. I'm running two right now (on this very machine:)).
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 29, 2007 at 10:05 am
Unfortunately, one of the precursor steps (where it checks about 30 different things and reports info/warning/errors in a grid) sees the previous MSSQL2K install and the subsequent step of the install has everything greyed out except installing documentation. I'm doing the install in a VMWare instance and am making better progress (after upgrading the heck out of the base OS install). I'd really like both instances on the same windows partition so I'll have all my dev tools available.
Bret
October 30, 2007 at 1:54 pm
I ran into a couple of issues installing a separate instance of 2005 on a box that already had 2000. One issue was a conflict with JDBC drives ... it seemed to over-ride what was being used by 2000. I can't remember the other problem ... it was during testing. I uninstalled 2005, and everything was fine again. I ended up doing my 2005 testing on a VM machine instead.
October 30, 2007 at 2:00 pm
Thanks - turns out the issue was a program called NeatReceipts which had installed a base version of MSSQL2K5, making my install of MSSQL2K5 an *upgrade* to the current version on my system. I didn't realize I had a version of MSSQL2K5 on my box, leading to all my problems. I need NeatReceipts and didn't want to hose its database, so I installed my MS Visual Studio into my VM environment with a full MSSQL2K5 install and it's all good.
Thanks for the reply.
Bret
Viewing 13 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply