Our application requires multiple instances of SQL Server 2000 in order to h
ave multiple databases, which the app clients use. Has something to do with
the name of the SQL Server instance; each instance needs to be named differe
ntly.
How does this work? Do I install SQL Server multiple times in different loca
tions, or is it simply a defined thing in SQL Server? Is there a 'per instan
ce' licensing issue, or will my one SQL Server license cover the multiple in
stances of SQL Server on on
e server system?
Thanks,
JohnI believe Standard edition is licensed per instance but Enterprise Edition
can be installed with multiple instances on a server. It's best to check
the EULA to be totally certain though. But having to buy one new copy of SE
could be worth looking at why this very odd requirement was "assumed" in the
application's design IMO.
hth
Eric
John wrote:
> Our application requires multiple instances of SQL Server 2000 in
> order to have multiple databases, which the app clients use. Has
> something to do with the name of the SQL Server instance; each
> instance needs to be named differently.
> How does this work? Do I install SQL Server multiple times in
> different locations, or is it simply a defined thing in SQL Server?
> Is there a 'per instance' licensing issue, or will my one SQL Server
> license cover the multiple instances of SQL Server on one server
> system?
> Thanks,
> John|||> Our application requires multiple instances of SQL Server 2000 in order to
have multiple databases
That's the part I don't get. Why can't the application use multiple
databases in a single instance?
> How does this work? Do I install SQL Server multiple times in different
locations
For multiple instances, yes.
> Is there a 'per instance' licensing issue
Depending on the edition of SQL Server, the licensing model you're using,
the OS, etc. You really should verify licensing compliance with a local
Microsoft rep. They can give you the legal answer as opposed to collating a
variety of opinions here.
http://www.aspfaq.com/
(Reverse address to reply.)|||It is poor design IMO, but I have to live with it. On the matter of the mult
iple instances, what is meant by 'instance'? multiple installations? multipl
e 'spawnings' of SQL Server under a parent 'SQL Server manager-like' server
process? does it end up loo
king like multiple servers systems each running a SQL Server, each with diff
erent names, data paths, etc, but actually all running on the same server sy
stem?
John
"Eric Sabine" wrote:
> I believe Standard edition is licensed per instance but Enterprise Edition
> can be installed with multiple instances on a server. It's best to check
> the EULA to be totally certain though. But having to buy one new copy of
SE
> could be worth looking at why this very odd requirement was "assumed" in t
he
> application's design IMO.
> hth
> Eric
> John wrote:
>
>|||Think of an instance of how many times you ran setup.exe through completion
of the wizard. Every instance after the default (if the default is taken
at first install) has the name of the server _and_ instance name as the name
of the sql server itself.
John wrote:[vbcol=seagreen]
> It is poor design IMO, but I have to live with it. On the matter of
> the multiple instances, what is meant by 'instance'? multiple
> installations? multiple 'spawnings' of SQL Server under a parent 'SQL
> Server manager-like' server process? does it end up looking like
> multiple servers systems each running a SQL Server, each with
> different names, data paths, etc, but actually all running on the
> same server system?
> John
> "Eric Sabine" wrote:
>
Showing posts with label multiple. Show all posts
Showing posts with label multiple. Show all posts
Friday, March 30, 2012
'Instances' of SQL Server 2000?
Our application requires multiple instances of SQL Server 2000 in order to have multiple databases, which the app clients use. Has something to do with the name of the SQL Server instance; each instance needs to be named differently.
How does this work? Do I install SQL Server multiple times in different locations, or is it simply a defined thing in SQL Server? Is there a 'per instance' licensing issue, or will my one SQL Server license cover the multiple instances of SQL Server on on
e server system?
Thanks,
John
I believe Standard edition is licensed per instance but Enterprise Edition
can be installed with multiple instances on a server. It's best to check
the EULA to be totally certain though. But having to buy one new copy of SE
could be worth looking at why this very odd requirement was "assumed" in the
application's design IMO.
hth
Eric
John wrote:
> Our application requires multiple instances of SQL Server 2000 in
> order to have multiple databases, which the app clients use. Has
> something to do with the name of the SQL Server instance; each
> instance needs to be named differently.
> How does this work? Do I install SQL Server multiple times in
> different locations, or is it simply a defined thing in SQL Server?
> Is there a 'per instance' licensing issue, or will my one SQL Server
> license cover the multiple instances of SQL Server on one server
> system?
> Thanks,
> John
|||> Our application requires multiple instances of SQL Server 2000 in order to
have multiple databases
That's the part I don't get. Why can't the application use multiple
databases in a single instance?
> How does this work? Do I install SQL Server multiple times in different
locations
For multiple instances, yes.
> Is there a 'per instance' licensing issue
Depending on the edition of SQL Server, the licensing model you're using,
the OS, etc. You really should verify licensing compliance with a local
Microsoft rep. They can give you the legal answer as opposed to collating a
variety of opinions here.
http://www.aspfaq.com/
(Reverse address to reply.)
|||It is poor design IMO, but I have to live with it. On the matter of the multiple instances, what is meant by 'instance'? multiple installations? multiple 'spawnings' of SQL Server under a parent 'SQL Server manager-like' server process? does it end up loo
king like multiple servers systems each running a SQL Server, each with different names, data paths, etc, but actually all running on the same server system?
John
"Eric Sabine" wrote:
> I believe Standard edition is licensed per instance but Enterprise Edition
> can be installed with multiple instances on a server. It's best to check
> the EULA to be totally certain though. But having to buy one new copy of SE
> could be worth looking at why this very odd requirement was "assumed" in the
> application's design IMO.
> hth
> Eric
> John wrote:
>
>
|||Think of an instance of how many times you ran setup.exe through completion
of the wizard. Every instance after the default (if the default is taken
at first install) has the name of the server _and_ instance name as the name
of the sql server itself.
John wrote:[vbcol=seagreen]
> It is poor design IMO, but I have to live with it. On the matter of
> the multiple instances, what is meant by 'instance'? multiple
> installations? multiple 'spawnings' of SQL Server under a parent 'SQL
> Server manager-like' server process? does it end up looking like
> multiple servers systems each running a SQL Server, each with
> different names, data paths, etc, but actually all running on the
> same server system?
> John
> "Eric Sabine" wrote:
sql
How does this work? Do I install SQL Server multiple times in different locations, or is it simply a defined thing in SQL Server? Is there a 'per instance' licensing issue, or will my one SQL Server license cover the multiple instances of SQL Server on on
e server system?
Thanks,
John
I believe Standard edition is licensed per instance but Enterprise Edition
can be installed with multiple instances on a server. It's best to check
the EULA to be totally certain though. But having to buy one new copy of SE
could be worth looking at why this very odd requirement was "assumed" in the
application's design IMO.
hth
Eric
John wrote:
> Our application requires multiple instances of SQL Server 2000 in
> order to have multiple databases, which the app clients use. Has
> something to do with the name of the SQL Server instance; each
> instance needs to be named differently.
> How does this work? Do I install SQL Server multiple times in
> different locations, or is it simply a defined thing in SQL Server?
> Is there a 'per instance' licensing issue, or will my one SQL Server
> license cover the multiple instances of SQL Server on one server
> system?
> Thanks,
> John
|||> Our application requires multiple instances of SQL Server 2000 in order to
have multiple databases
That's the part I don't get. Why can't the application use multiple
databases in a single instance?
> How does this work? Do I install SQL Server multiple times in different
locations
For multiple instances, yes.
> Is there a 'per instance' licensing issue
Depending on the edition of SQL Server, the licensing model you're using,
the OS, etc. You really should verify licensing compliance with a local
Microsoft rep. They can give you the legal answer as opposed to collating a
variety of opinions here.
http://www.aspfaq.com/
(Reverse address to reply.)
|||It is poor design IMO, but I have to live with it. On the matter of the multiple instances, what is meant by 'instance'? multiple installations? multiple 'spawnings' of SQL Server under a parent 'SQL Server manager-like' server process? does it end up loo
king like multiple servers systems each running a SQL Server, each with different names, data paths, etc, but actually all running on the same server system?
John
"Eric Sabine" wrote:
> I believe Standard edition is licensed per instance but Enterprise Edition
> can be installed with multiple instances on a server. It's best to check
> the EULA to be totally certain though. But having to buy one new copy of SE
> could be worth looking at why this very odd requirement was "assumed" in the
> application's design IMO.
> hth
> Eric
> John wrote:
>
>
|||Think of an instance of how many times you ran setup.exe through completion
of the wizard. Every instance after the default (if the default is taken
at first install) has the name of the server _and_ instance name as the name
of the sql server itself.
John wrote:[vbcol=seagreen]
> It is poor design IMO, but I have to live with it. On the matter of
> the multiple instances, what is meant by 'instance'? multiple
> installations? multiple 'spawnings' of SQL Server under a parent 'SQL
> Server manager-like' server process? does it end up looking like
> multiple servers systems each running a SQL Server, each with
> different names, data paths, etc, but actually all running on the
> same server system?
> John
> "Eric Sabine" wrote:
sql
Instances in Virtual SQL Servers
Can someone explain setting up instances in virtual SQL Servers? I know that you can have multiple virtual SQL Servers on a cluster, but does each default instance, or is it one default instance on the cluster no matter how many virtual servers you have?
Thank you.
On a cluster you get one default instance and 15 named instances OR 16 named
instances. Of course you don't have to create all the instances, these are
just maximum numbers. The number of hosts in the cluster doesn't matter
towards the instance count.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"walkman" <walkman@.discussions.microsoft.com> wrote in message
news:232E50F3-15CA-40DA-9ABA-4026EA8400B6@.microsoft.com...
> Can someone explain setting up instances in virtual SQL Servers? I know
that you can have multiple virtual SQL Servers on a cluster, but does each
default instance, or is it one default instance on the cluster no matter how
many virtual servers you have?
> Thank you.
|||Thank you. I was confused in that I thought each virtual machine would have its own default instance.
"Geoff N. Hiten" wrote:
> On a cluster you get one default instance and 15 named instances OR 16 named
> instances. Of course you don't have to create all the instances, these are
> just maximum numbers. The number of hosts in the cluster doesn't matter
> towards the instance count.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "walkman" <walkman@.discussions.microsoft.com> wrote in message
> news:232E50F3-15CA-40DA-9ABA-4026EA8400B6@.microsoft.com...
> that you can have multiple virtual SQL Servers on a cluster, but does each
> default instance, or is it one default instance on the cluster no matter how
> many virtual servers you have?
>
>
|||Each Virtual Server gets a single instance. It can be either a named
instance or a default instance, however only one such virtual server per
cluster can hold a default instance. This is because of how SQL stores the
binaries for each instance locally on each host node.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"walkman" <walkman@.discussions.microsoft.com> wrote in message
news:1C60B13E-E2CC-4001-ABD5-55665EE35419@.microsoft.com...
> Thank you. I was confused in that I thought each virtual machine would
have its own default instance.[vbcol=seagreen]
> "Geoff N. Hiten" wrote:
named[vbcol=seagreen]
are[vbcol=seagreen]
know[vbcol=seagreen]
each[vbcol=seagreen]
how[vbcol=seagreen]
|||Don't feel bad. You are not alone. This is confusing at the beginning.
Here are some additional references that you may find useful:
================================================== ====
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/SQL/techinf...vercluster.asp
Microsoft SQL Server 2000 High Availability Series
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
Microsoft Webcasts
Introduction to Microsoft SQL Server 2000 Clustering
http://support.microsoft.com/default...lurb051001.asp
Microsoft SQL Server 2000 Virtual Server: Things You Should Know
http://support.microsoft.com/default...lurb032602.asp
Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack
http://support.microsoft.com/default...lurb061002.asp
Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
http://support.microsoft.com/default...lurb101802.asp
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
Q243218 INF: Installation Order for SQL 2000 Enterprise Edition
http://support.microsoft.com/?kbid=243218
Q260758 - INF: Frequently Asked Questions - SQL Server 2000 - Failover Clustering
http://support.microsoft.com/?kbid=260758
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Thank you.
On a cluster you get one default instance and 15 named instances OR 16 named
instances. Of course you don't have to create all the instances, these are
just maximum numbers. The number of hosts in the cluster doesn't matter
towards the instance count.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"walkman" <walkman@.discussions.microsoft.com> wrote in message
news:232E50F3-15CA-40DA-9ABA-4026EA8400B6@.microsoft.com...
> Can someone explain setting up instances in virtual SQL Servers? I know
that you can have multiple virtual SQL Servers on a cluster, but does each
default instance, or is it one default instance on the cluster no matter how
many virtual servers you have?
> Thank you.
|||Thank you. I was confused in that I thought each virtual machine would have its own default instance.
"Geoff N. Hiten" wrote:
> On a cluster you get one default instance and 15 named instances OR 16 named
> instances. Of course you don't have to create all the instances, these are
> just maximum numbers. The number of hosts in the cluster doesn't matter
> towards the instance count.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "walkman" <walkman@.discussions.microsoft.com> wrote in message
> news:232E50F3-15CA-40DA-9ABA-4026EA8400B6@.microsoft.com...
> that you can have multiple virtual SQL Servers on a cluster, but does each
> default instance, or is it one default instance on the cluster no matter how
> many virtual servers you have?
>
>
|||Each Virtual Server gets a single instance. It can be either a named
instance or a default instance, however only one such virtual server per
cluster can hold a default instance. This is because of how SQL stores the
binaries for each instance locally on each host node.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"walkman" <walkman@.discussions.microsoft.com> wrote in message
news:1C60B13E-E2CC-4001-ABD5-55665EE35419@.microsoft.com...
> Thank you. I was confused in that I thought each virtual machine would
have its own default instance.[vbcol=seagreen]
> "Geoff N. Hiten" wrote:
named[vbcol=seagreen]
are[vbcol=seagreen]
know[vbcol=seagreen]
each[vbcol=seagreen]
how[vbcol=seagreen]
|||Don't feel bad. You are not alone. This is confusing at the beginning.
Here are some additional references that you may find useful:
================================================== ====
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/SQL/techinf...vercluster.asp
Microsoft SQL Server 2000 High Availability Series
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
Microsoft Webcasts
Introduction to Microsoft SQL Server 2000 Clustering
http://support.microsoft.com/default...lurb051001.asp
Microsoft SQL Server 2000 Virtual Server: Things You Should Know
http://support.microsoft.com/default...lurb032602.asp
Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack
http://support.microsoft.com/default...lurb061002.asp
Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
http://support.microsoft.com/default...lurb101802.asp
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
Q243218 INF: Installation Order for SQL 2000 Enterprise Edition
http://support.microsoft.com/?kbid=243218
Q260758 - INF: Frequently Asked Questions - SQL Server 2000 - Failover Clustering
http://support.microsoft.com/?kbid=260758
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Subscribe to:
Posts (Atom)