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

Instances

How to see the no of instances created for my server.

if it is sql server 2005

sqlcmd -L : it will list all the instances in the network , you can identify by machine name what all the instance in your machine

for SQL 2000

osql -L

|||yes. They give the list of sql servers in the list.
But what i want is
the instances created for my server only.|||

Launch the services console: services.msc - it should list a separate SQL Server service for each instance.

You can also check the registry: HKLM\Microsoft SQL Server\Instance Names.

Thanks
Laurentiu

sql

Instance wil not come online

2 out of 4 instances on my 3 node cluster wil not come online on one off
the clusternodes, unless I add an alias (which I removed after
installing sp3). The application eventlog complains about not being able
to connect to the instance. I can connect to the instance remotely, but
apparently the clusterservice can not. I can not find any differences in
the registry of files. Reinstalling sql did not help. Any ideas?
Hans
Hans de Bruin wrote:
> 2 out of 4 instances on my 3 node cluster wil not come online on one off
> the clusternodes, unless I add an alias (which I removed after
> installing sp3). The application eventlog complains about not being able
> to connect to the instance. I can connect to the instance remotely, but
> apparently the clusterservice can not. I can not find any differences in
> the registry of files. Reinstalling sql did not help. Any ideas?
>
udp 1434 isn't always responding. So when the is no entry in
hkey-local_machine\software\mssqlserverclient\..\lastco nnect on my
workstation osql wil not connect. All nodes and instances report to be
8.00.818 (sp3 + latest hotfix). accoording to netstat al de nodes are
listening to udp 0.0.0.0:1434. Could W2k3 still be blocking 1434 or is
there a problem with registering the instance with the udp thing?
Hans
|||Hans de Bruin wrote:
> Hans de Bruin wrote:
>
> udp 1434 isn't always responding. So when the is no entry in
> hkey-local_machine\software\mssqlserverclient\..\lastco nnect on my
> workstation osql wil not connect. All nodes and instances report to be
> 8.00.818 (sp3 + latest hotfix). accoording to netstat al de nodes are
> listening to udp 0.0.0.0:1434. Could W2k3 still be blocking 1434 or is
> there a problem with registering the instance with the udp thing?
>
hmm, on ether node:
clear the node of all sql instances:
clear the registry on the client.
fail over one sql instance to the node.
connect to the instance: success
fail over a second instance to the node
connect to the second instance: timout on udp 1434
clear the registry on the client.
connect to the fisrt instance again: success
move the fist instance to an other node.
connect to the fisrt second again: success
So I am only able to connect to the fist activated instance on a node
useing udp 1434. Where did I go wrong?
Hans
|||Hans,
I have seen a similar problem to yours in one of our clusters.
Can you post the errors in the eventlog.
Thanks,
PK
Message posted via http://www.sqlmonster.com
|||PK via SQLMonster.com wrote:
> Hans,
> I have seen a similar problem to yours in one of our clusters.
> Can you post the errors in the eventlog.
> Thanks,
> PK
>
It looks like this one:
http://groups.google.nl/groups?threa...GP11.phx. gbl
My instances were running without local admin rights. After I
fixed this, udp1434 was behaving normally, and I could remove the
alias on the clusternodes.
I want to run some of the instances without local admin rights so I can
give developers sysadmin rights on their instance without giving them
access to the whole system.
Hans
|||Hans de Bruin wrote:
> PK via SQLMonster.com wrote:
>
> It looks like this one:
> http://groups.google.nl/groups?threa...GP11.phx. gbl
oops try this one:
http://groups.google.nl/groups?threa...0a% 40phx.gbl

>
> My instances were running without local admin rights. After I
> fixed this, udp1434 was behaving normally, and I could remove the
> alias on the clusternodes.
> I want to run some of the instances without local admin rights so I can
> give developers sysadmin rights on their instance without giving them
> access to the whole system.
>
|||Hans de Bruin wrote:
> 2 out of 4 instances on my 3 node cluster wil not come online on one off
> the clusternodes, unless I add an alias (which I removed after
> installing sp3). The application eventlog complains about not being able
> to connect to the instance. I can connect to the instance remotely, but
> apparently the clusterservice can not. I can not find any differences in
> the registry of files. Reinstalling sql did not help. Any ideas?
>
Apparently what happens is this:
- i1 come online the node as non admin and takes hold of udp 1434
- the MSCS tries to connect to the i1 and requests for the portnumber.
- i1 looks in its own the reqistry and finds the port number.
- MSCS gets an anwser an connects. i1 is online.
- i2 tries to come online on the node as either admin or non admin.
- the MSCS tries to connect to the i2 and requests for the portnumber.
- i1 tries to looks in i2's reqistry and gets an access denied.
- MSCS does not get any anwser and makes interesing calls to wins and
dns, fails to figure out the portnumer or pipename and fails i2
- i3 tries to come online on the node as either admin or non admin.
- the MSCS tries to connect to the i3 and requests for the portnumber.
- i1 tries to looks in i3's reqistry and gets an access denied.
- MSCS does not get any anwser and makes interesing calls to wins and
dns, fails to figure out the portnumer or pipename and fails i3
...
conclussion:
When running multiple sql instances (clustered or not) sql needs to run
as an local admin or system account or you need to hack the registry
permissions to let udp 1434 work, or or you need create an alias on the
server and the clients so sqlserveragent and the clients can connect.
Hans

Instance name already exists

Hello all...
Win2k3 enterprise
SQL 2000
2 nodes
I had 2 instances of SQL installed. I had to run setup to remove clustered
SQL so I could break the disk array and make it larger.
Now, I install instance 1 on node 1 just fine.
But when I run setup on node 2 to install instance 2, it tells me that
instance name already exists.
I thought when I "un-clustered" SQL that both instances would have been
removed. I can see both instance names in C:\program files\Microsoft sql
server\
How do I go about getting rid of the second instance name now, so I can
reinstall it?
Thanks in advance.
Jeff
Hi Jeff,
I would first try to uninstall the second instance the regular way i.e using the setup CD and choosing uninstall (the same way you uninstalled the first instance). If this doesn't work then you will need to manually uninstall
it. For more info, review
HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual Instance
http://support.microsoft.com/?kbid=290991
HTH,
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 Uttam,
I had tried the setup cd and it does not recognize the instance for
uninstall (only when I go to install the instance...go figure). But I did
not find the article you mention, so I will try that.
Jeff
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:RaXEsKppEHA.752@.cpmsftngxa06.phx.gbl...
> Hi Jeff,
> I would first try to uninstall the second instance the regular way i.e
using the setup CD and choosing uninstall (the same way you uninstalled the
first instance). If this doesn't work then you will need to manually
uninstall
> it. For more info, review
> HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual
Instance
> http://support.microsoft.com/?kbid=290991
> HTH,
> 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
>

Instance Licencing

Hi,

We are have a 5 user licenced microsoft sql server 2000 cd. We need to
set this up to run two instances of the server, as we need different
setups on both databases. Does anyone know if with one cd you can do
this, so that the user licences installed are shared between the two
instances? Also do you need a aeperate server licence per instance or
if using the user license model we can install both instances from the
same cd.

Thanks for your help & time

DavidDavid wrote:

Quote:

Originally Posted by

Hi,
>
We are have a 5 user licenced microsoft sql server 2000 cd. We need to
set this up to run two instances of the server, as we need different
setups on both databases. Does anyone know if with one cd you can do
this, so that the user licences installed are shared between the two
instances? Also do you need a aeperate server licence per instance or
if using the user license model we can install both instances from the
same cd.
>
Thanks for your help & time
>
David

It's my understanding that with Enterprise version you can install
multiple instances per server but with Standard you can't (or you're
not supposed to). I'm pretty sure you would be able to use the same CD
to do so.

Installing two instances of Report server

Can we install two instances of report server on the same machine?. We want to use the same hardware for two different methods of custom authentication. Both the server applications would then talk to the same database.

cvajre,

Here's a step by step way of implementing 2 reporting instances.

http://bloggingabout.net/blogs/mglaser/archive/2006/12/18/multiple-reporting-services-instances-on-one-machine.aspx

Ham

installing the sample databases and documentation

There are two instances: SQL2005 and SQL2005Express on two different units. While there is Visual Studio 2005 Team Edition also installed on the units have not attempted these component installs through either yet. Have spent the better part of two days, following all the directions having searched help locally, online, technet,and applied their advice respectively. While I've taken out the old instances, downloaded updated ones in both my SQL Server instances they do not show as installed under Programs->SQL Server (whichever instance)->Tutorials ...However they do show installed in Control Panel and they can be found via Explorer (AdWorks DBCI+AdWorks BICI and Express instance on the other unit. Have also download SP2 and installed it, but this has proved of no help. @. My wits' end, any help will be appreciated.

Documentation and sample databases are an option during installation.

Books Online appears as an installed program in Add/Remove Programs but the sample databases do not.

If AdventureWorks was installed with 2005 but did not appear in Object Explorer you can attach it. Attach is on the right-click menu of Databases in Object Explorer.

|||

You can also find the SQL Server 2005 documentation available online at:

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

It has many great tutorials to get started.

Thanks,
Sam Lester (MSFT)

|||Thank you for your suggestion Lester, however before my initial post had already consulted books online, and downloaded the latest version to stay in sync with the software. Part of my frustration comes from following their directions but failing to achieve similar outcomes. Adventure Works databases are definitely resident on my computer, though not in the same directories in the Explorer file hierarchy indicated by the manuals/instructions. The directions have been exhaustively followed a number of times, replete with uninstalls then reinstalls - all to no avail. This is the case in both units, each with a different operating system and different version of SQL. Am still stymied.

Installing SQL Server 2000 Instance

I am trying to install a new instance and it asks me to kill the tasks
for sql server other instances that are running. this occurs are the
MDAC 2.6 setup. I have MDAC 2.8 installed on the box but this still
comesup.
I have not seen this in the past, or encountered this problem,
is there a way to avoid this or not to kill the tasks as i think it
will stop the service for the other instances and thus give me some
downtime which i dont want.
Any suggestion or idea will be great.
Hi
"rubeel@.gmail.com" wrote:

> I am trying to install a new instance and it asks me to kill the tasks
> for sql server other instances that are running. this occurs are the
> MDAC 2.6 setup. I have MDAC 2.8 installed on the box but this still
> comesup.
> I have not seen this in the past, or encountered this problem,
> is there a way to avoid this or not to kill the tasks as i think it
> will stop the service for the other instances and thus give me some
> downtime which i dont want.
> Any suggestion or idea will be great.
>
You could use the MDAC component checker to make sure that you have the
version of MDAC you think is there.
Which versions of SQL Server are each of the instances running? What
components have you installed?
John
|||It is SQL server 2000 on a Win2k Box. all Enterprise.
The problem is that when i try to install a new instance it tries to
install MDAC 2.6 and says that the sqlservr task(which are as many as
the instances, around 14) needs to be stopped. I cant do that on the
prod box and it is causing a dilemma for me. I didnt have a problem a
couple of weeks back when i did the same and it installed the
instance.
I thought it was a service problem so i scheduled a reboot last nite
and that didnt help.
Rubeel

Installing SQL Server 2000 Instance

I am trying to install a new instance and it asks me to kill the tasks
for sql server other instances that are running. this occurs are the
MDAC 2.6 setup. I have MDAC 2.8 installed on the box but this still
comesup.
I have not seen this in the past, or encountered this problem,
is there a way to avoid this or not to kill the tasks as i think it
will stop the service for the other instances and thus give me some
downtime which i dont want.
Any suggestion or idea will be great.Hi
"rubeel@.gmail.com" wrote:
> I am trying to install a new instance and it asks me to kill the tasks
> for sql server other instances that are running. this occurs are the
> MDAC 2.6 setup. I have MDAC 2.8 installed on the box but this still
> comesup.
> I have not seen this in the past, or encountered this problem,
> is there a way to avoid this or not to kill the tasks as i think it
> will stop the service for the other instances and thus give me some
> downtime which i dont want.
> Any suggestion or idea will be great.
>
You could use the MDAC component checker to make sure that you have the
version of MDAC you think is there.
Which versions of SQL Server are each of the instances running? What
components have you installed?
John|||It is SQL server 2000 on a Win2k Box. all Enterprise.
The problem is that when i try to install a new instance it tries to
install MDAC 2.6 and says that the sqlservr task(which are as many as
the instances, around 14) needs to be stopped. I cant do that on the
prod box and it is causing a dilemma for me. I didnt have a problem a
couple of weeks back when i did the same and it installed the
instance.
I thought it was a service problem so i scheduled a reboot last nite
and that didnt help.
Rubeel

Installing SQL Server 2000 Instance

I am trying to install a new instance and it asks me to kill the tasks
for sql server other instances that are running. this occurs are the
MDAC 2.6 setup. I have MDAC 2.8 installed on the box but this still
comesup.
I have not seen this in the past, or encountered this problem,
is there a way to avoid this or not to kill the tasks as i think it
will stop the service for the other instances and thus give me some
downtime which i dont want.
Any suggestion or idea will be great.Hi
"rubeel@.gmail.com" wrote:

> I am trying to install a new instance and it asks me to kill the tasks
> for sql server other instances that are running. this occurs are the
> MDAC 2.6 setup. I have MDAC 2.8 installed on the box but this still
> comesup.
> I have not seen this in the past, or encountered this problem,
> is there a way to avoid this or not to kill the tasks as i think it
> will stop the service for the other instances and thus give me some
> downtime which i dont want.
> Any suggestion or idea will be great.
>
You could use the MDAC component checker to make sure that you have the
version of MDAC you think is there.
Which versions of SQL Server are each of the instances running? What
components have you installed?
John|||It is SQL server 2000 on a Win2k Box. all Enterprise.
The problem is that when i try to install a new instance it tries to
install MDAC 2.6 and says that the sqlservr task(which are as many as
the instances, around 14) needs to be stopped. I cant do that on the
prod box and it is causing a dilemma for me. I didnt have a problem a
couple of weeks back when i did the same and it installed the
instance.
I thought it was a service problem so i scheduled a reboot last nite
and that didnt help.
Rubeel

Installing SQL Express SP1 with existing User Instances

Hi,

I've read the readme for the Service Pack 1 for Microsoft SQL Server 2005.

http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/ReadmeSQL2005SP1.htm

But I'm not quite clear on what will happen if you currently have SQL Server Express 2005 installed with User Instances, and then you launch the installer for SP1.

Will it also update the User Instance? If so, how could I tell? When I go to the registry for the User Instance it has the older version value ie.

HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\[instance name]\MSSQLServer\CurrentVersion = 9.00.1399.06

Shouldn't it be saying 9.00.2047.00?

Does this mean that I have to uninstall the User Instance before installing SP1?

Any help will be appreciated.

Thanks

Sam

User instances work by cloning the actual instance at startup time, so as long as the main instance is updated then all should work.|||

User Instances are upgrade automatically as Euan says. You really shouldn't be using the registry to judge the success of an upgrade, it's complex and undocumented. You're not looking at the main Key for the SQL version installed.

Rather, after you perform the upgrade, go into the query tool of choice (Managment Studio, SQLCmd, etc.) and run the following:

SELECT @.@.version

This will return the Edition and Version of the server you connected to. If it is not 2047, then you didn't upgrade that Instance.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

Hi Euan and Mike,

Your comments have been helpful.

What I found was that I actually hadn't upgraded our instance of SQL properly.

I've been using the command line for the SQL installer and worked out that the way for it to update the existing instance (and subsequent user instances) was to use

SQLEXPR.EXE /qb INSTANCENAME=<MyInstance> UPGRADE=SQL_Engine

Using these options for the installer I could confirm the upgrade both in the registry and more importantly using

SELECT @.@.version

Thanks

Sam