Instances of SQL Server have disappeared

Hi,

We had 5 instances of SQL Server running on one of our machines and everything looked to be working fine. Today I installed another instance for a new application and once done and rebooted the new instance didn't show in the SQL Server Enterprise Manager. At this point we decided to uninstall it. After that 4 of the existing instances have diapered as well even though they are running and responding requests from their respective applications.

I did some googling and all I could see is something related to a command called nscontrol but I couldn't find any nscontrol executable on that machine.

Does anyone have any idea what this problem could be?

Thanksnscontrol is related to SQL Notification Services. I don't think that would be part of your solution.

I'm confused why you are installing a new instance of SQL Server for each application?

In any case, are you having any better luck? If not, can you go to the Windows command prompt on the server where SQL Server is running and type in osql -L and see if your instances are all listed? Have you checked your system's event log for any clues? How about the SQL Server error log?

I know that you should be able to run up to 16 instances of SQL Server, so you are probably not hitting that limitation.

Terri|||I'm with Terri. Instead of running 5 instances of SQL Server, why not use 1? And use 5 different databases? Seems like a better solution to me. Probably less overhead too.|||Sorry for not posting sooner, someone here has experienced something similar and the solution was to reregister every instance in Enterprise Manager. We can't explain why this thing happens but looks like this is what had to be done.

With respect to using instances rather then databases, the theory here is that we try to stay away from database administration and delegate it to the groups that actually need that application and databases that is why we give different instances to different groups of people. I hope that this explains somehow our situation.|||Glad you got it sorted out.

Yes, I had done research after you had made that post and read the cases for having multiple instances on the same server. That does make sense. Just keep in mind you can't have more than 16 instances :-)

Terri|||Yes, we knew about 16 instances limit.

Thanks

'Instances' of SQL Server 2000?

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:
>

'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

Instances of SQL

Hi,

Is it possible to install more than one instance of SQL on the same server?
I am thinking of the SQL that comes with Windows 2003 SBS (Small business)

--
Thank you
Please post onlyYes. Sql2k supports named instances.

http://msdn.microsoft.com/library/e...nstall_259u.asp

"!!bogus" <hello@.microb.com> wrote in message
news:Dwavc.95442$tb4.3789522@.news20.bellglobal.com ...
> Hi,
> Is it possible to install more than one instance of SQL on the same server?
> I am thinking of the SQL that comes with Windows 2003 SBS (Small business)
> --
> Thank you
> Please post only|||"!!bogus" <hello@.microb.com> wrote in message news:<Dwavc.95442$tb4.3789522@.news20.bellglobal.com>...
> Hi,
> Is it possible to install more than one instance of SQL on the same server?
> I am thinking of the SQL that comes with Windows 2003 SBS (Small business)

SQL2000 supports multiple instances (see Books Online), but you need
to consider the impact on the server resources - you will need to
manage CPU and memory carefully to give each instance enough to work
with, as well as leaving enough for the OS and other applications. I
don't know anything about SBS specifically, but my feeling would be
that since SBS already installs a bunch of different applications on
the same server, you probably don't want to add the complexity of
multiple MSSQL instances.

Depending on what you want to achieve, you might want to look at MSDE,
which is a free version of MSSQL with some limitations:

http://www.microsoft.com/sql/msde/

Simon

instances of MSDE

I can install instances of MSDE without any problem. But
for some reasons the password (or the instance) get
corrupted after I try to upsize a table from MS Access to
an existing database in MSDE (I'll stop doing this).
But now I have multiple instances which I would like to
clean up. Does anybody know how to uninstall them?
Thanks
Perry
Hi ,
You can use the following information to uninstall msde.
A)Remove the following registry:
1) Remove the following ID_Number from your MSDE 2.0 instance
HKEY_CLASSES_ROOT\Installer\Products\ID_Number
-- It has key value name 'ProductName' which displays the instance name.
For example, "ProductName" = Microsoft SQL Server Desktop Engine
(MYINSTANCE)
2)If you had patch applied on this MSDE 2.0 instance, you need to remove
ID_Number
for that MSDE 2.0 instance:
HKEY_CLASSES_ROOT\Installer\Patches\ID_Number
3) For MSDE 2.0 Default instance, remove
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Your_instance_name
4)If you have the following key points to MSDE 2.0 productGUID, then remove
the
InstanceComponentSet.x
For example, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Component
SetInstanceComponentSet.x
-- For example, InstanceComponentSet.1 the has value matching the
productGUID of
sqlrun01.msi.
5)Remove :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\Produ
ctGUID
-- the Product GUID which refers to your MSDE 2.0 instance.
6)Remove the Sql server service key:
For MSDE 2.0 default instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLServer
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$Your_Instance_Nam
e
7)Remove the Sql server agent service key:
For MSDE 2.0 default instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLServerAgent
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent$Your_Instance_
Name
B)Remove the MSDE 2.0 instance data and program install directory:
For example, G:\Program Files\Microsoft SQL
Server\MSSQL$Your_instanceName\data
For example, G:\Program Files\Microsoft SQL
Server\MSSQL$Your_instanceName\binn
Now rerun the msde setup from the command prompt
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.

Instances list on remote IP

Is there a way to get all the SQL Server instances with SQL SMO from a
remote computer?
I got few instances on some remote IP and
how to list them, how to pass to the function this address - could it be
done at all?
Second question:
Locally I'm using SmoApplication.EnumAvailableSqlServers, but
I've got SQLEXPRESS and MSDE SP 4, and got MYCOMPUTERNAME\SQLEXPRESS and
MYCOMPUTERNAME\MSDE2000 but if I do that:
DataTable dt = SmoApplication.EnumAvailableSqlServers(false);
if (dt.Rows.Count > 0)
{
foreach (DataRow dr in dt.Rows)
{
ddlSQLServerInstances.Items.Add(new
ListItem(dr["Name"].ToString(), dr["Name"].ToString()));
}
}
In my dropdownlist appears only MYCOMPUTERNAME, nothing more...
I'll be happy for any suggestions.
Thank you!!!I had the same problem and it turned out to be that the firewall is blocking
the packets. I think one needs to have UDP 1343 open outbound, but unless I
turn off the firewall I still do not get non-local server instances in the
enumeration; The data seems to be sent back on random UDP ports > 2700, (th
e
port range is not confirmed) and I'm not sure if one can specify ranges usin
g
the built-in Windows XP SP2 firewall.
If anyone has a solution for this that lets me use the same firewall and
still get the enumeration, please reply. I'm curious.
"christof" wrote:

> Is there a way to get all the SQL Server instances with SQL SMO from a
> remote computer?
> I got few instances on some remote IP and
> how to list them, how to pass to the function this address - could it be
> done at all?
> Second question:
> Locally I'm using SmoApplication.EnumAvailableSqlServers, but
> I've got SQLEXPRESS and MSDE SP 4, and got MYCOMPUTERNAME\SQLEXPRESS and
> MYCOMPUTERNAME\MSDE2000 but if I do that:
> DataTable dt = SmoApplication.EnumAvailableSqlServers(false);
> if (dt.Rows.Count > 0)
> {
> foreach (DataRow dr in dt.Rows)
> {
> ddlSQLServerInstances.Items.Add(new
> ListItem(dr["Name"].ToString(), dr["Name"].ToString()));
> }
> }
> In my dropdownlist appears only MYCOMPUTERNAME, nothing more...
> I'll be happy for any suggestions.
> Thank you!!!
>

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