SQL 2000 Enterprise Manager & SQL 2005 Management Studio

  • Hello everyone. I am new to administering SQL servers and I inherited an existing SQL installation and have a question about it.

    The current installation has SQL 2000 and Enterprise Manager installed on it. SQL 2005 was apparently installed on it later in a named instance and both versions are actively in use.

    Enterprise Manager is still installed and useable, but SQL 2005 Management Studio is not installed. Can they both safely coexist on the same machine? If not, are there any caveats to uninstalling Enterprise Manager and installing SQL Studio?

    Thanks for the help.

  • Yes you can run then both side by side on the same machine. One thing i would say is make sure that the sql 2000 instance is service packed up to SP4. There seems to be quite a few issues when the SP level is less than 4 and you install sql 2005.

  • Animal Magic (4/21/2008)


    Yes you can run then both side by side on the same machine. One thing i would say is make sure that the sql 2000 instance is service packed up to SP4. There seems to be quite a few issues when the SP level is less than 4 and you install sql 2005.

    Just out of Curiosity, Isnt SP4 a bit flacky? We have SQL 2000 but we have kept it at SP2. SP3 was nasty and SP4 still has issues.

    On the test network I have both SQL 2000 and SQL 2005 installed side by side. SQL 2005 is a named Instance. Works fine for me.

    -Roy

  • Fair enough. All i know is there have been a few machines which had SP3 on which i also put SQL 2005 on that ran into little issues. Especially once the DTS components were installed for sql 2005, that just screwed EM completely.

    Any machines where SP4 has been installed have always been ok.

    Maybe its a coincidence 🙂

  • Roy Ernest (4/21/2008)


    Animal Magic (4/21/2008)


    Yes you can run then both side by side on the same machine. One thing i would say is make sure that the sql 2000 instance is service packed up to SP4. There seems to be quite a few issues when the SP level is less than 4 and you install sql 2005.

    Just out of Curiosity, Isnt SP4 a bit flacky? We have SQL 2000 but we have kept it at SP2. SP3 was nasty and SP4 still has issues.

    On the test network I have both SQL 2000 and SQL 2005 installed side by side. SQL 2005 is a named Instance. Works fine for me.

    ps, i thought SP2 was still vulnerable to the slammer worm? I could be wrong as ive only been in this game a little while, but i thought the minimum SP level should be 3a?

  • SP3 and SP3a was soo bad that they had to keep on sending Hot fixes and patches for them. SP3 was the worst SP MS has ever released for SQL Server I think.

    SP2 had a patch for the Slammer worm.

    -Roy

  • Roy Ernest (4/21/2008)


    SP3 and SP3a was soo bad that they had to keep on sending Hot fixes and patches for them. SP3 was the worst SP MS has ever released for SQL Server I think.

    SP2 had a patch for the Slammer worm.

    Thanks for the info 🙂 You learn something new every day

  • Thanks for all of the replies. I think I'll try installing the Management Studio on our Development servers tomorrow and if everything goes ok, I will then deploy it to Production.

    Thanks again!

Viewing 8 posts - 1 through 7 (of 7 total)

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