Good morning!

Okay, this question is regarding putting a second instance of SQL2000 on the
SBS2003 box. Client has an application that makes use of SQL and they
have - against our suggestions and recommendations - decided to install a
second installation of SQL on the existing SBS2003 box instead of purchasing
SQL2005 for their new server.

Client is upgrading that application (many many patches behind) to the
latest and greatest and apparently there is a huge difference in the GUI so
they want to have some training on the new Interface. Not a bad idea!

Anyway, any assistance in installing a second instance of SQL on the SBS2003
box would be greatly appreciated. I presume that it is simply taking the
SBS2003 install CDs and installing SQL again?

I am sure that there are a whole slew of questions that I should have
regarding the installation....I am taking these to the application Tech
Support so that I do things the correct way for their application.

Thanks,

Cary

Cary Shultz wrote:

>Good morning!
>
>Okay, this question is regarding putting a second instance of SQL2000 on
>the SBS2003 box. Client has an application that makes use of SQL and they
>have - against our suggestions and recommendations - decided to install a
>second installation of SQL on the existing SBS2003 box instead of
>purchasing SQL2005 for their new server.
>
>Client is upgrading that application (many many patches behind) to the
>latest and greatest and apparently there is a huge difference in the GUI
>so they want to have some training on the new Interface. Not a bad idea!
>
>Anyway, any assistance in installing a second instance of SQL on the
>SBS2003 box would be greatly appreciated. I presume that it is simply
>taking the SBS2003 install CDs and installing SQL again?
>
>I am sure that there are a whole slew of questions that I should have
>regarding the installation....I am taking these to the application Tech
>Support so that I do things the correct way for their application.

SBS has multiple SQL instances OOB.

So my only concern would be in trying to limit the number of
business-installed instances to the smallest number possible.

And if you have WSUS3/WSS3 installed, you may need to take particular
care, since those now use a SQL2005 based instance ("Windows Internal
Database"), and installation of SQL2000 when you already have both is
somewhat fussy.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Well, you put a lot here, and so I just want to make sure we are on the same
page, so read below each of your paragraphs for my
advice/thoughs/rants/whatevers.


"Cary Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
news:%23PP$2rYuIHA.1872@TK2MSFTNGP04.phx.gbl...
> Good morning!
>
> Okay, this question is regarding putting a second instance of SQL2000 on
> the SBS2003 box. Client has an application that makes use of SQL and they
> have - against our suggestions and recommendations - decided to install a
> second installation of SQL on the existing SBS2003 box instead of
> purchasing SQL2005 for their new server.
This itself shouldn't be a problem, but the client should be made very aware
that every new instance of SQL will degrade the performance of the system.
They should also check with the application vendor. I have to assume, based
on the "second installation of SQL" that you aren't running SQL enterprise
and will be installing an MSDE instance. That (as well as SQL Express 2005)
has connection and memory limits that may make the applicatoin inoperable.
It is best to ensure the plan fits the needs of the app as well as the
server.

> Client is upgrading that application (many many patches behind) to the
> latest and greatest and apparently there is a huge difference in the GUI
> so they want to have some training on the new Interface. Not a bad idea!
Shouldn't impact SQL.

> Anyway, any assistance in installing a second instance of SQL on the
> SBS2003 box would be greatly appreciated. I presume that it is simply
> taking the SBS2003 install CDs and installing SQL again?

I would not use the SBS CD's for this. You have two scenarios:

1) If you are using SBS standard then the SQL instances that are installed
by SBS are specifically for SBS. You should install SQL based on the
application vendor's recommendations. Many smaller applications have their
own MSDE installs pre-bundled, so no need to use the SBS CD's.

2) You are using SBS Premium which comes with SQL Server. If this is the
case, and you are trying to use it for the application, you don't need to
re-install it from the CD. You can use the SQL management tools to make
another new instance. SQL Server is built to run multiple instances, so
"installing" isn't necessary once the initial server is set up. Again,
regarding instance name, protocols used, etc, it is best to refer to the
application vendor.



> I am sure that there are a whole slew of questions that I should have
> regarding the installation....I am taking these to the application Tech
> Support so that I do things the correct way for their application.
Yup.

> Thanks,
>
> Cary


Good Luck!

-Cliff

Steve,

Thanks for the information. No WSUS here....just one application that makes
use of SQL2000.

Cary

"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0fqd7fweavpn4018@msnews.microsoft.com...
> Cary Shultz wrote:
>
>>Good morning!
>>
>>Okay, this question is regarding putting a second instance of SQL2000 on
>>the SBS2003 box. Client has an application that makes use of SQL and they
>>have - against our suggestions and recommendations - decided to install a
>>second installation of SQL on the existing SBS2003 box instead of
>>purchasing SQL2005 for their new server.
>>
>>Client is upgrading that application (many many patches behind) to the
>>latest and greatest and apparently there is a huge difference in the GUI
>>so they want to have some training on the new Interface. Not a bad idea!
>>
>>Anyway, any assistance in installing a second instance of SQL on the
>>SBS2003 box would be greatly appreciated. I presume that it is simply
>>taking the SBS2003 install CDs and installing SQL again?
>>
>>I am sure that there are a whole slew of questions that I should have
>>regarding the installation....I am taking these to the application Tech
>>Support so that I do things the correct way for their application.
>
> SBS has multiple SQL instances OOB.
>
> So my only concern would be in trying to limit the number of
> business-installed instances to the smallest number possible.
>
> And if you have WSUS3/WSS3 installed, you may need to take particular
> care, since those now use a SQL2005 based instance ("Windows Internal
> Database"), and installation of SQL2000 when you already have both is
> somewhat fussy.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.

Cliff,

I usually do put a lot! More often than not, probably way too much....

see in-line.....

"Cliff Galiher" <cgaliher@gmail.com> wrote in message
news:96387045-D99B-41A0-8909-A1F88A196357@microsoft.com...
> Well, you put a lot here, and so I just want to make sure we are on the
> same page, so read below each of your paragraphs for my
> advice/thoughs/rants/whatevers.
>
>
> "Cary Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
> news:%23PP$2rYuIHA.1872@TK2MSFTNGP04.phx.gbl...
>> Good morning!
>>
>> Okay, this question is regarding putting a second instance of SQL2000 on
>> the SBS2003 box. Client has an application that makes use of SQL and
>> they have - against our suggestions and recommendations - decided to
>> install a second installation of SQL on the existing SBS2003 box instead
>> of purchasing SQL2005 for their new server.
> This itself shouldn't be a problem, but the client should be made very
> aware that every new instance of SQL will degrade the performance of the
> system. They should also check with the application vendor. I have to
> assume, based on the "second installation of SQL" that you aren't running
> SQL enterprise and will be installing an MSDE instance. That (as well as
> SQL Express 2005) has connection and memory limits that may make the
> applicatoin inoperable. It is best to ensure the plan fits the needs of
> the app as well as the server.


Cliff, should have written "second instance". And, we have been very very
very clear with the client. The apps vendor has suggested that doing this
will bring the system to its knees, if not downright crash the server. So,
we are preparing a disaster recovery plan for this. This is what the client
wants to do...even against our recommendations. So, we are preparing for
the worst.

>
>> Client is upgrading that application (many many patches behind) to the
>> latest and greatest and apparently there is a huge difference in the GUI
>> so they want to have some training on the new Interface. Not a bad idea!
> Shouldn't impact SQL.

No, you are correct. Should not impact SQL. This is just a bit of that
"extra" that I put in my posts (and answers when I am on the other end).

>
>> Anyway, any assistance in installing a second instance of SQL on the
>> SBS2003 box would be greatly appreciated. I presume that it is simply
>> taking the SBS2003 install CDs and installing SQL again?
>
> I would not use the SBS CD's for this. You have two scenarios:
>
> 1) If you are using SBS standard then the SQL instances that are installed
> by SBS are specifically for SBS. You should install SQL based on the
> application vendor's recommendations. Many smaller applications have
> their own MSDE installs pre-bundled, so no need to use the SBS CD's.

This would not be the case....

>
> 2) You are using SBS Premium which comes with SQL Server. If this is the
> case, and you are trying to use it for the application, you don't need to
> re-install it from the CD. You can use the SQL management tools to make
> another new instance. SQL Server is built to run multiple instances, so
> "installing" isn't necessary once the initial server is set up. Again,
> regarding instance name, protocols used, etc, it is best to refer to the
> application vendor.

This would be the case and is something that I discovered before reading
your post. But, Thanks! It is good to know that 1) my thought process was
a little bit off initially and 2) that I did correctly correct my thought
process.

>
>
>
>> I am sure that there are a whole slew of questions that I should have
>> regarding the installation....I am taking these to the application Tech
>> Support so that I do things the correct way for their application.
> Yup.

Doing that in a few moments.....


>
>> Thanks,
>>
>> Cary
>
>
> Good Luck!
>
> -Cliff
>