SBS 2003 R2 with SQL 2005 and we need SQL 2000

Discussion in 'Windows Small Business Server' started by Joe, Jan 16, 2007.

  1. Joe

    Joe Guest

    We have just migrated a NT4 domain to SBS2003 and all is well other than the
    fact that a piece of software on the site needs SQL 2000.

    SQL 2005 has been installed on the server by the SBS setup, and Backup Exec
    is now probably using it.

    Can we downgrade SQL2005 to SQL2000 on the licence we have?

    Joe.
     
    Joe, Jan 16, 2007
    #1
    1. Advertisements

  2. Joe

    Joe Guest

    Yes, I have installed SQL2005 and BackupExec and I now find out that SQL2005
    has problems with the software....

    Thanks for the answer.

    Did you have any issues un-installing it etc.

    Joe.
     
    Joe, Jan 16, 2007
    #2
    1. Advertisements

  3. You need to exercise downgrade rights on SBS2003 R2 to SBS2003 SP1. That's
    the *whole* of SBS, you don't get to downgrade "bits".

    You should have done this before installing SBS, and I'm not sure there's
    any way to do this without a reinstall at this point. It's not even cleat
    that you can still legally downgrade, having installed SBS2003 R2.
     
    Steve Foster [SBS MVP], Jan 16, 2007
    #3
  4. Joe

    Joe Guest

    Thanks for that...but we hadn't been told they even needed sql let alone
    that they needed SQL 2000! Its a bit pants to think that because of software
    conflicts that I can't down grade a version of software I've bought to allow
    my software to work.

    To downgrade a SBS install....where does one start?

    Joe.
     
    Joe, Jan 16, 2007
    #4
  5. Joe

    Joe Guest

    After a chat with the clients we have decided to try to go ahead with a SQL
    2005 setup, but now I can't find the SQL Enterprise manager!

    Anyone help? We have installed the SQL 2005 disk that came with SBS Premium
    and all went ok but now all we have in the program files for SQL are as
    follows

    Configuration tools with the following options

    sql server configuration manager
    sql error and usage reporting
    sql server surface area configuration.

    Joe


     
    Joe, Jan 16, 2007
    #5
  6. It's not a technical issue at all really. It's a legal issue.

    SBS is a suite. You buy the suite. You get what's in the bundle. You don't
    get to pick and choose - if that's what you need, SBS is not the solution.

    SBS2003 R2 Premium includes SQL2005WE. SBS2003 Premium (with or without
    SP1) includes SQL2000Std.

    However, because Microsoft _have_ recognised that there are some who need
    or want to stay at SQL2000, they have made downgrade rights *for the
    suite* available. This allows you to buy SBS2003 R2, but choose to install
    only SBS2003 SP1 (you have to obtain SBS2003 SP1 media from MS). There are
    those who argue Microsoft should have gone further, but remember there was
    no obligation on them to even go this far. It would have been very nice if
    we'd got the choice, but we haven't, and we have to make the best of what
    we do have (or vote with our feet/wallets).

    If you want SQL2000, you need to exercise downgrade rights, and then you
    give up (well, postpone - you can move *the suite* forwards again later
    when you're ready) *all* the R2 "goodies" - no integrated WSUS, no
    expanded CAL rights, no SQL2005.

    The interesting angle for you is that you've already gone ahead and
    deployed the R2 functionality. I don't know what the legal position on
    downgrade rights is under that scenario. You need to talk to Microsoft.

    With FDISK probably. AFAIK, there's no technical way to remove the R2
    portions of the install once it's on. Not to mention that there's no
    SQL2000 included in the R2 installation media.

    Please note I don't like this mess any more than you do. It's not of my
    making, nor do I have any power to wave a magic 2x4 and make it all
    better. I'm simply telling you how it is.
     
    Steve Foster [SBS MVP], Jan 16, 2007
    #6
  7. Joe

    Joe Guest

    Thanks for the reply, if nothing else it has brough a very happy smile to my
    tired addled brain! As with all of these things the job/ client/ a
    conversation took over and now we are moving on with an attempt to get the
    updated client software and install it on SQL2005.

    I think the most annoying thing of the whole lot is that apparently no
    matter how much planning on migrations that you do there is always 1 tiny,
    incey wincey little thing that always stabs you, and this is this one.

    2 quick questions that you may be able to answer but I am in search of a SQL
    newsgroup...

    How do I get NTBackup to backup my SQL files?
    How do I stop VSS services stopping and not backing up the system state when
    SQL is installed onto a server?

    Thanks,

    Joe

    I don't think when I did my ms courses that I'd ever have to deal with SQL,
    I even managed to avoid it for the last few years, but obviously God has
    decided that this year I'll get my bapitism....
     
    Joe, Jan 17, 2007
    #7
  8. Sort out the VSS and it's automatic (assuming the SQL database and log
    files remain on a VSS-enabled partition).
    Make sure all the SQL databases are set to the Simple recovery model. Or
    move the SQL databases and logs to a volume that has VSS disabled if you
    need Full recovery.

    In the latter scenario, you'd do SQL backups to disk, and then pick those
    up in the regular backup.
     
    Steve Foster [SBS MVP], Jan 17, 2007
    #8
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.