Post reply

Hosting SQL2000 AND 2005

  • April 23, 2008 at 3:09 pm

    #186948

    Is that ok to install sql 2000 and 2005 on same box.if so what precautions need to be taken?

  • April 24, 2008 at 1:53 am

    #806397

    You can install both version on the same box. But you'll have to look at your performance if it is workable.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • April 24, 2008 at 6:56 am

    #806531

    Thank you . i am looking for that information.

  • April 25, 2008 at 7:00 am

    #807135

    I would recommend installing SQL 2000 FIRST then SQL 2005.

    Have a good day,

    Norene Malaney

  • April 25, 2008 at 7:06 am

    #807139

    can please you explain why you think 2000 be installed before 2005?

  • April 25, 2008 at 7:24 am

    #807156

    Yes, they'll run together just fine. Make sure you have enough memory, processor, disk space, etc. (no different than running mulitple instances of either product). You'll also need to keep the SQL Browser Service (new in 2005) running in order to talk to the 2005 instance while the 2000 instance is running.

    Kendal Van Dyke
    http://kendalvandyke.blogspot.com/[/url]

  • April 25, 2008 at 7:34 am

    #807168

    This is just a principal that I usually follow - install the early version first - and then the later version. I guess I want to make sure that if some of the same files are used by both versions of the app - that the file being used is the most up-to-date version of the file.

    Have a good day,

    Norene Malaney

  • April 25, 2008 at 4:56 pm

    #807440

    Rajan John (4/25/2008)

    can please you explain why you think 2000 be installed before 2005?

    From my personal experience, installing 2000 first followed by 2005, installing 2005 first followed by 2000 broke some functionality in SQL 2005. I don't remember all the details, but it was enough to remove them both and start over.

    Installing 2000, then 2005, then 2008 beta, then removing 2008 is something I would totally not suggest.....again from personal experience...I think I see a total OS wipe in my near future, but thats what the test machine is for 🙂

  • April 25, 2008 at 5:30 pm

    #807447

    I think there are some things that are overwritten with 2005, so if you do 2005 first, things will break.

    As far as issues, one has to be a named instance. Some applications don't like that. Be sure ports are not a problem as only one can be 1433.

    Memory is usually the biggest issue. You have to decide how much to allocate to each instance. I wouldn't let them fight for memory. While SQL Server will give up memory to other applications, it does so begrudgingly, so it might be slow.

  • April 28, 2008 at 12:58 am

    #807612

    Hi

    Adding on to what others have said..

    Try and keep your 2000 & 2005 database files on separate disks if possibe. This will give you better read/write performance specially write performance.

    "Keep Trying"

  • April 29, 2008 at 8:03 am

    #808365

    I had an experience of connection string issues. On a single machine when I tried to connect to SQL 2K that had 2k5 installed on it The connection was dissallowed, look into the intricacies of the same as well. I had resolved issue as well.

    Regards,

    Rajesh

  • April 29, 2008 at 8:33 am

    #808396

    Just to add confirmation to what has been said earlier.

    If SQLSERVER 2000 is installed first Installing SQLSERVER 2005 on the same box has not caused any issues for us as long as the resources are there to handle both.

    If the installation is performed in the opposite manner, SQLSERVER 2000 will overwrite some files and 2005 will cease to function properly. It may also cause degredation in performance for that box.

    I am not aware of any issues due to conflicts with editions. We have installed developer editions on the same computer. We have not tried this with other editions. But the order still will matter.

    Q

    Please take a number. Now serving emergency 1,203,894

  • April 29, 2008 at 9:16 am

    #808462

    For best results sharing one system with 2 software packages that might have issues, VMWare is your friend.

    You haven't mentioned whether this is a development/personal/business production or what installation of the 2 different SQL server packages.

  • April 29, 2008 at 10:03 pm

    #808765

    Both were standard editions and SQL2k5 was installed earlier than sql2k but when I tried connecting to 2k the default connection to 2k was dissallowed as saying server doesnt allow anonymous connections. This was only resolved after I uninstalled SQL2k5.

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply