MS SQL Server - SQL Instances

Author

SQL Instances

siskokid480

2006-10-24, 6:33 pm

I currently have an application that uses SQL Enterprise 2000. I am looking
to install another application that also requires SQL Enterprise 2000 on the
same server. I am guessing that this is possible, as I am aware that it will
support up to 16 instances. But I am unsure of how the whole licensing works.
Will the already installed SQL need to be upgraded to support both
applications, as far as licensing goes. Or is it that I will have to run a
another setup process for the second application?

Could some one provide some insight or advise on how this scenarios work for
install and licensing.

Thanks in advance.

Tibor Karaszi

2006-10-24, 6:33 pm

One option is to just create a new database for the second application. But assuming that you have
reasons to separate these into distinct instances. Just install the second instance. However,
regarding licensing, the answer might differ depending on whether you run Per Processor or per
server/cal.

This URL is for 2005, and one Q is exactly your question. If you look around on the web site, you
might find a similar FAQ for 2000. If not, I'd contact MS, they should have the answer for you.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/

"siskokid480" < siskokid480@discussi
ons.microsoft.com> wrote in message
news:051F97F7-68E3-4D47-9CB3- 46F69C17BE72@microso
ft.com...
>I currently have an application that uses SQL Enterprise 2000. I am looking
> to install another application that also requires SQL Enterprise 2000 on the
> same server. I am guessing that this is possible, as I am aware that it will
> support up to 16 instances. But I am unsure of how the whole licensing works.
> Will the already installed SQL need to be upgraded to support both
> applications, as far as licensing goes. Or is it that I will have to run a
> another setup process for the second application?
>
> Could some one provide some insight or advise on how this scenarios work for
> install and licensing.
>
> Thanks in advance.

siskokid480

2006-10-24, 6:33 pm

Thanks for the reply.

The SQL Enterprise version is running under a "Per Processor" licensing,
where I have two processors. If I create a second database will it be a
licensing issue? What would be the advantages in creating a seperate
instance. Excuse my stupidity, but Installing a second instance means simply
running the SQL setup program, correct?

Thanks again.

"Tibor Karaszi" wrote:

> One option is to just create a new database for the second application. But assuming that you have
> reasons to separate these into distinct instances. Just install the second instance. However,
> regarding licensing, the answer might differ depending on whether you run Per Processor or per
> server/cal.
>
> This URL is for 2005, and one Q is exactly your question. If you look around on the web site, you
> might find a similar FAQ for 2000. If not, I'd contact MS, they should have the answer for you.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www. solidqualitylearning
.com/
>
>
> "siskokid480" < siskokid480@discussi
ons.microsoft.com> wrote in message
> news:051F97F7-68E3-4D47-9CB3- 46F69C17BE72@microso
ft.com...
>
>

Tibor Karaszi

2006-10-24, 6:33 pm

> The SQL Enterprise version is running under a "Per Processor" licensing,
> where I have two processors. If I create a second database will it be a
> licensing issue?

You always have the ability to have several databases in one instance, without any influence of
licensing, whatsoever.

> What would be the advantages in creating a separate
> instance.

Conflicting configuration requirements at the system database level, for example. Like system
database collation, sp_configure setting, etc. Or, the ability to SQL Server service pack "one
application" without affecting the other "application".

> Excuse my stupidity, but Installing a second instance means simply
> running the SQL setup program, correct?

No need for excuses :-). Yes, run setup again and install the new instance.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/

"siskokid480" < siskokid480@discussi
ons.microsoft.com> wrote in message
news:2AFB2CB9-C9F5-4A65-96C8- EFAB5F425EE7@microso
ft.com...[color=darkred]
> Thanks for the reply.
>
> The SQL Enterprise version is running under a "Per Processor" licensing,
> where I have two processors. If I create a second database will it be a
> licensing issue? What would be the advantages in creating a seperate
> instance. Excuse my stupidity, but Installing a second instance means simply
> running the SQL setup program, correct?
>
> Thanks again.
>
> "Tibor Karaszi" wrote:
>

siskokid480

2006-10-24, 6:33 pm

With that info, you have help me be in a position to make a good decision.
Thanks again for your help. It is appreciated.

"Tibor Karaszi" wrote:

>
> You always have the ability to have several databases in one instance, without any influence of
> licensing, whatsoever.
>
>
>
> Conflicting configuration requirements at the system database level, for example. Like system
> database collation, sp_configure setting, etc. Or, the ability to SQL Server service pack "one
> application" without affecting the other "application".
>
>
>
> No need for excuses :-). Yes, run setup again and install the new instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www. solidqualitylearning
.com/
>
>
> "siskokid480" < siskokid480@discussi
ons.microsoft.com> wrote in message
> news:2AFB2CB9-C9F5-4A65-96C8- EFAB5F425EE7@microso
ft.com...
>
>

Sponsored Links