SQL MSDE and full standard install

  • I was asked to install SQL Standard edition for a 3rd party vendor coming in to install their software.

    I noticed that there was already a SQL server manager running in the tray, but there were no tools listed in the programs menu.

    I was told that someone has installed SQLMSDE on the server and just do a full standard install.

    I went ahead with the install, but when I went to apply the sp3a I received an error message that says 'a later service pack has already been applied'.

    I then noticed that there were two instances on the server -

    1st install created GPDB01, my install created GPDB01\GPDB01

    The @@version on the 1st install (GPDB01) is -

    Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)

     May  3 2005 23:18:38

     Copyright (c) 1988-2003 Microsoft Corporation

     Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 1)

    The @@version on my install (GPDB01\GPDB01) is 8.0 194

    Microsoft SQL Server  2000 - 8.00.194 (Intel X86)

     Aug  6 2000 00:57:48

     Copyright (c) 1988-2000 Microsoft Corporation

     Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

    I went to lunch and the vendor started his install, but it ended up on the GPDB01 database.

    My questions are -

    Can I uninstall MSDE version of SQL and move the databases for the standard install?

    Are there any adverse effect in using the MSDE version rather than the standard?

    How would I apply a SP to the 2nd instance?

    Thanks in advance for any  help.

    Susan

  • Hi Susan,

    we had a similiar problem with trying to get 2 MSDE instances - one named, one default - onto the one box when the named instance had been installed first.  We ended up removing the named instance but the default instance still couldn't be installed\service packed.  We had to remove the named instance from the registry key "HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstalledInstances".  It seems that the uninstaller doesn't do this. This then allowed the Service Pack to run.  So I would suggest trying to temporarily remove the default instance this time from the "InstalledInstances" key and see if it makes a difference (back up the registry first in case it goes horribly wrong 0-:  )

    If nothing else works I would actually remove the default MSDE instance, leaving you with the standard named instance, moving the databases across beforehand.  If you remove the default instance from the key then you should be able to SP it.  Or backup all the databases on both instances, remove both, wipe the InstalledInstances key and start again with standard as a default instance.

     

    Keep smiling (-:

    Anthony K.

  • Thanks for the advice Anthony, I'll probably end up just wiping it and starting over.

    Enjoy your weekend.

     

    Susan

  • Susan,

    Please, note that if your server is DELL some DELL server utilities do install MSDE. I was surprised too when found MSDE on a brand-new server. Then the server support who installed Windows told me he installed optional DELL server utilities.

    Regards,Yelena Varsha

  • That's exactly what happened.

    What did you do?

    I'm thinking of uninstalling everything and starting from scratch..

     

  • I talked to this server support person and we decided we did not need these features that use MSDE and we uninstalled them, MSDE included. Then I installed SQL Server Standard as a default instance without problems.

    Also, I had cases when ONLY Client Tools like Enterprise Manager were installed and I too could not install Standard as Default instance. So I had to uninstall client tools and install Standard Edition (with Client Tools included)

    Regards,Yelena Varsha

Viewing 6 posts - 1 through 5 (of 5 total)

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