Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts

Friday, March 30, 2012

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

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.

Instance/sqlservr.exe problem

Hi! I have SQL 2000 server with several instance. Every instance start own
sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
time, but I don't know to which instance it belongs?
regards, Tomatoma
DBCC MEMORYSTATUS on the both instances
"toma" <toma@.kolumbus.fi> wrote in message
news:ab32h.43057$8W7.25630@.reader1.news.jippii.net...
> Hi! I have SQL 2000 server with several instance. Every instance start own
> sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100%
> CPU time, but I don't know to which instance it belongs?
> regards, Toma
>|||From Task Manager, you can find the process ID of the sqlservr.exe process.
If the ProcessID column is not displayed, Go to Views -> Select Columns...
and click on PID.
In the errorlog of a SQL instance, the process ID of that instance is
reported at the beginning of the errorlog. Alternatively, you can query the
process ID of the instance with SERVERPROPERTY('ProcessID').
Linchi
"toma" wrote:

> Hi! I have SQL 2000 server with several instance. Every instance start own
> sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CP
U
> time, but I don't know to which instance it belongs?
> regards, Toma
>
>|||You can get the PID you see in Task Manager by executing the
following on an instance:
SELECT SERVERPROPERTY('ProcessID')
-Sue
On Wed, 1 Nov 2006 17:37:38 +0200, "toma" <toma@.kolumbus.fi>
wrote:

>Hi! I have SQL 2000 server with several instance. Every instance start own
>sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
>time, but I don't know to which instance it belongs?
>regards, Toma
>

Instance/sqlservr.exe problem

Hi! I have SQL 2000 server with several instance. Every instance start own
sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
time, but I don't know to which instance it belongs?
regards, Toma
toma
DBCC MEMORYSTATUS on the both instances
"toma" <toma@.kolumbus.fi> wrote in message
news:ab32h.43057$8W7.25630@.reader1.news.jippii.net ...
> Hi! I have SQL 2000 server with several instance. Every instance start own
> sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100%
> CPU time, but I don't know to which instance it belongs?
> regards, Toma
>
|||From Task Manager, you can find the process ID of the sqlservr.exe process.
If the ProcessID column is not displayed, Go to Views -> Select Columns...
and click on PID.
In the errorlog of a SQL instance, the process ID of that instance is
reported at the beginning of the errorlog. Alternatively, you can query the
process ID of the instance with SERVERPROPERTY('ProcessID').
Linchi
"toma" wrote:

> Hi! I have SQL 2000 server with several instance. Every instance start own
> sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
> time, but I don't know to which instance it belongs?
> regards, Toma
>
>
|||You can get the PID you see in Task Manager by executing the
following on an instance:
SELECT SERVERPROPERTY('ProcessID')
-Sue
On Wed, 1 Nov 2006 17:37:38 +0200, "toma" <toma@.kolumbus.fi>
wrote:

>Hi! I have SQL 2000 server with several instance. Every instance start own
>sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
>time, but I don't know to which instance it belongs?
>regards, Toma
>

Instance/sqlservr.exe problem

Hi! I have SQL 2000 server with several instance. Every instance start own
sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
time, but I don't know to which instance it belongs?
regards, Tomatoma
DBCC MEMORYSTATUS on the both instances
"toma" <toma@.kolumbus.fi> wrote in message
news:ab32h.43057$8W7.25630@.reader1.news.jippii.net...
> Hi! I have SQL 2000 server with several instance. Every instance start own
> sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100%
> CPU time, but I don't know to which instance it belongs?
> regards, Toma
>|||From Task Manager, you can find the process ID of the sqlservr.exe process.
If the ProcessID column is not displayed, Go to Views -> Select Columns...
and click on PID.
In the errorlog of a SQL instance, the process ID of that instance is
reported at the beginning of the errorlog. Alternatively, you can query the
process ID of the instance with SERVERPROPERTY('ProcessID').
Linchi
"toma" wrote:
> Hi! I have SQL 2000 server with several instance. Every instance start own
> sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
> time, but I don't know to which instance it belongs?
> regards, Toma
>
>|||You can get the PID you see in Task Manager by executing the
following on an instance:
SELECT SERVERPROPERTY('ProcessID')
-Sue
On Wed, 1 Nov 2006 17:37:38 +0200, "toma" <toma@.kolumbus.fi>
wrote:
>Hi! I have SQL 2000 server with several instance. Every instance start own
>sqlservr.exe task on Task Manager. Now one of sqlservr.exe is take 100% CPU
>time, but I don't know to which instance it belongs?
>regards, Toma
>

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 Uniunstall problem with "Uninst.isu" file

I am attempting to uninstall an instance of SQL Server 2000. When I run the SS2000 "change/uninstall" process in "Add/Remove Programs" (Control Panel), I get an error message stating that ...

"Unable to locate the installation log file 'C:\Program Files\Microsoft SQL Server\....\Uninst.isu Uninstallation will not continue."

I have looked in the directory and the file is not there.How do I uninstall SS2000?

Hi,

I am facing the same problem in fact I have manually removed all traces of sql server 2000 in program files. It is still exisiting in add/remove programs. How to remove it from there.

Thanks,

Bharath

|||

Even I am facing the same problem.

Can anyone help us., Please...

sql

Instance Uniunstall problem with "Uninst.isu" file

I am attempting to uninstall an instance of SQL Server 2000. When I run the SS2000 "change/uninstall" process in "Add/Remove Programs" (Control Panel), I get an error message stating that ...

"Unable to locate the installation log file 'C:\Program Files\Microsoft SQL Server\....\Uninst.isu Uninstallation will not continue."

I have looked in the directory and the file is not there.How do I uninstall SS2000?

Hi,

I am facing the same problem in fact I have manually removed all traces of sql server 2000 in program files. It is still exisiting in add/remove programs. How to remove it from there.

Thanks,

Bharath

Instance Uniunstall problem with "Uninst.isu" file

I am attempting to uninstall an instance of SQL Server 2000. When I run the SS2000 "change/uninstall" process in "Add/Remove Programs" (Control Panel), I get an error message stating that ...

"Unable to locate the installation log file 'C:\Program Files\Microsoft SQL Server\....\Uninst.isu Uninstallation will not continue."

I have looked in the directory and the file is not there.How do I uninstall SS2000?

Hi,

I am facing the same problem in fact I have manually removed all traces of sql server 2000 in program files. It is still exisiting in add/remove programs. How to remove it from there.

Thanks,

Bharath

|||

Even I am facing the same problem.

Can anyone help us., Please...

Instance specified not valid

Hi,

I'm trying to install MSDE SP3 which I downloaded from MS at http://www.asp.net/msde/.
Following the instructions as best I can I unzipped the file into a Folder now called MSDE located on C: I then went to a command prompt and typed in the command given to start the install:

setup SAPWD=testsite SecurityMode=SQL

Hit enter and the installer started up and ran for a few secs and then came back with

The Instance named specified is invalid

There was no mention of including an instance name or the format for it.

Suggestions please?

Also, if I want to completly uninstall MSDE if I need to how would I do it?

Thanks,
BobWell, I had this message come up if I tried to run setup for the instance that was already on the system.

I used this setup to install msde on my machine.

setup instancename="netsdk" sapwd="your password for sa" securitymode=sql

Reason for using instance name netsdk was that it seems that SDK kit needs this instance to install pubs and nwind database.

After executing this i did not get any error messages but when I started service manager I could not see any servers listed. It took me solid two hours to come up with idea to look into error log and there it was.

2004-03-09 11:57:44.50 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)

2004-03-09 11:57:44.50 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-03-09 11:57:44.50 server All rights reserved.
2004-03-09 11:57:44.50 server Server Process ID is 3456.
2004-03-09 11:57:44.50 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-03-09 11:57:44.52 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2004-03-09 11:57:44.63 server SQL Server configured for thread mode processing.
2004-03-09 11:57:44.63 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-03-09 11:57:44.63 spid2 Warning ******************
2004-03-09 11:57:44.63 spid2 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-03-09 11:57:44.63 spid2 Starting up database 'master'.
2004-03-09 11:57:44.98 spid5 Starting up database 'model'.
2004-03-09 11:57:44.98 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-03-09 11:57:45.03 spid2 Server name is 'PC0491-EPITKA\NETSDK'.
2004-03-09 11:57:45.03 spid2 Skipping startup of clean database id 5
2004-03-09 11:57:45.03 spid2 Skipping startup of clean database id 6
2004-03-09 11:57:45.03 spid2 Starting up database 'msdb'.
2004-03-09 11:57:45.17 server SQL server listening on Shared Memory.
2004-03-09 11:57:45.17 server SQL Server is ready for client connections
2004-03-09 11:57:45.38 spid5 Clearing tempdb database.
2004-03-09 11:57:46.12 spid5 Starting up database 'tempdb'.
2004-03-09 11:57:46.20 spid2 Recovery complete.
2004-03-09 11:57:46.20 spid2 SQL global counter collection task is created.
2004-03-09 11:57:46.22 spid2 Warning: override, autoexec procedures skipped.
2004-03-09 11:57:56.94 spid51 Error: 15457, Severity: 0, State: 1
2004-03-09 11:57:56.94 spid51 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2004-03-09 11:57:57.08 spid51 Error: 15457, Severity: 0, State: 1
2004-03-09 11:57:57.08 spid51 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2004-03-09 11:57:57.34 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.

There is a line that says servername, I typed it in and I was able to start service. Log should be under c:\program files\microsoft sql server\mssql${your instance name}\log.

I am very new to windows world since I worked on Unix platform for past six years, so for you gurus out there this migth be something that does not need to be explained. Anyway I hope this helps.sql

Instance rename

Is it possible to rename an instance?
I expect the answer is no , but.....
Thanks in advanceI don't think it's possible to rename an instance without reinstalling, or
at least I've never tried and never seen a technique documented.
You could, however, create an alias that points to that instance...
"Jim Campau" <Jim_Campau@.bausch.com> wrote in message
news:edPkJDYRDHA.2228@.tk2msftngp13.phx.gbl...
> Is it possible to rename an instance?
> I expect the answer is no , but.....
> Thanks in advance
>|||you have to rename the Computer to rename your SQL Server. If you are
talking about renaming a named instance of SQL Server, it's not possible.
To rename named instance of sql server:
Install new instance with the new name.
Move your databases from the old instance to the newly instance (using
backup/restore or DTS).
Uninstall the old instance.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_
afterinstall_5r8f.asp
-Vishal
"Jim Campau" <Jim_Campau@.bausch.com> wrote in message
news:edPkJDYRDHA.2228@.tk2msftngp13.phx.gbl...
> Is it possible to rename an instance?
> I expect the answer is no , but.....
> Thanks in advance
>

Instance Port

Hi,
Anybody can tell me how can I get the port number of an
instance name in SQL Server 2000.
Thanks in advance.
Javier RosasJavier,
Refer to this url.
http://support.microsoft.com/default.aspx?scid=kb;[LN];265808
- Vishal
"Javier Rosas" <jrosashe@.accival.com.mx> wrote in message
news:031401c3ae15$1303d3b0$a401280a@.phx.gbl...
> Hi,
> Anybody can tell me how can I get the port number of an
> instance name in SQL Server 2000.
> Thanks in advance.
> Javier Rosas|||The best place is the header of the errorlog for the
instance. The port that the instance listens on is
identified there along with the IP address.
You could also use the Server Network Configuration to
check the configured port. But there is a chance that it's
not the port the instance is currently using.
Linchi
>--Original Message--
>Hi,
>Anybody can tell me how can I get the port number of an
>instance name in SQL Server 2000.
>Thanks in advance.
>Javier Rosas
>.
>

instance of sql server

I am learning SQL Server 2005 and I was told to install a second instance of
SQL Server 2005 on my machine. How can I install a second instance of SQL
Server 2005 on my machine

I already installed SQL Server 2005, I guess this is my first instance. To
install a second instance, do I just run setup again?Yes, just run setup again to create a 'named' instance. Setup will ask you
for an instance name.

A computer can have up to 1 default instance (probably what you installed
initially) but many named instances. To connect to the default instance
after installation, specify only the computer name. For the named instance,
specify computer name and instance name separated by a backslash
('ComputerName\InstanceName').

--
Hope this helps.

Dan Guzman
SQL Server MVP

"David" <david_vcp@.hotmail.com> wrote in message
news:bMKdnc_BtsngZ9fZRVn-rg@.comcast.com...
>I am learning SQL Server 2005 and I was told to install a second instance
>of SQL Server 2005 on my machine. How can I install a second instance of
>SQL Server 2005 on my machine
> I already installed SQL Server 2005, I guess this is my first instance.
> To install a second instance, do I just run setup again?

Instance not showning up

Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris

> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com

Instance not showning up

Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!
Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris

> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com
sql

Instance not showning up

Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
--
David Gugick
Imceda Software
www.imceda.com

Instance NetSDK

Dear
I have a question about SQL Server / MSDE. Iâ'm trying install and to configure the documentation of the .NET Framework 1.1 but I have a problem because is necessary contain a instance: â'Local\NetSDKâ' (Local is the same the principal instance) second information about details of the configuration
Iâ'm working with Microsoft SQL Server 2000 â' Personal Edition and I have listed in SQL Server Service Manager only: â'Localâ'
How I make to create the instance: â'NetSDKâ'
Your
ThankI'm not sure why that SDK needs an instance of SQL Server with that
particular name, but I'd have thought it would create the instance during
it's installation...
Anyway, to create a named instance of SQL Server, you have to install it
again & you get the chance to provide the instance name during the
installation process.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Rogério Toledo" <anonymous@.discussions.microsoft.com> wrote in message
news:B75B10E3-3740-45BC-93D5-39158618C2D1@.microsoft.com...
> Dear,
> I have a question about SQL Server / MSDE. I'm trying install and to
configure the documentation of the .NET Framework 1.1 but I have a problem
because is necessary contain a instance: "Local\NetSDK" (Local is the same
the principal instance) second information about details of the
configuration.
> I'm working with Microsoft SQL Server 2000 - Personal Edition and I have
listed in SQL Server Service Manager only: "Local".
> How I make to create the instance: "NetSDK"?
> Yours
> Thanks
>

Instance naming problems

When I try to Add New Item - Database in VS C# Express, I get "An error has occurred while establishing a conncection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)"

When I open the management studio, I can connect to a database named Dev, and when I try to "Browse for more" from the server selector combobox, it is the only one found. I believe "Dev" was my old MSDE name, although this is also what my "Computer Name" is set to. Unfortunetly the setup of SQL Express didn't ask me what to name my instance.

I thought maybe the SQL Server 2005 Express Toolkit installation didn't actually contain the server software, and only installed the tools, as during the installation the section where I select components only listed things like client tools and what not, with not mention of the server software.

So I thought maybe it didn't install the server, so I downloaded the server installation that is by itself, and installed it, this time I saw the check for hide advanced options, so I went through the advanced options this time. I've have been through this same setup before at work, and both times it has confused me. It seems very different from installing previous versions of SQL server.

Where I choose to create a new instance or upgrade, I choose to upgade, and it is not clear what I'm upgrading, the selector does not display instance names.

At another point it asks me about configuring it to use the Local service, local system, or network account. The documentation of how these differ is vauge. For example, the network account is described basically as "don't use this" without saying what it is.

I was accustomed to just a local account, and network account settings from previous versions, and network was always the logical choice for me to use intergrated security. I don't understand what the new catagories represent and what will be functionally different in the way I connect.

So I'm really confused, and getting back to the instance names. In the surface area configuration as well as the VS Express, it only sees the name as MSSQLSERVER

For example if I "add new connection" from database explorer and click advanced, the datasource drop down lists only ".\MSSQLSERVER"

So I'm thoroughly confused at this point and not sure what to do.

Let's see if I can help you some:

* By default, if you install the SQL Server Express engine and you do not specify the instance name the instance name would be SQLEXPRESS.

* Connect to a named instance by specifying "<Computer Name>\<Instance Name>" (without the quotes). ".\<Instance Name> will also work when connect to a local instance.

* For the service account, using Network Service or domain account without administrator rights on the local server is recommended. Network Service work best if SQL Server does not need to perform functions on the network which requires more permission than Network Service has. If this is the case, use a low-privilege domain account.

* Use SQL Server Configuration Manager to view all SQL services (instances) installed. (I am not sure if SQL 2000 instance include MSDE are shown -- if not use SQL Manager or Control Panel | Services to see if MSDE is installed)

Hope this helps,

Peter Saddow

Instance name specified is invalid

I am trying to apply the sql2kdesksp3a to a new
installation of SQL desktop. When I try and apple the SP
I recieve the error The instance name is invalid. I have
tried searching for the instance in the registry that is
reffered to on KB 311762 but I can not find any
references to the MSI file used for install. I am using a
select CD from Microsoft to install SQL Desktop. I dont
understand why this should be so hard I have not loaded
any 3rd part apps just XP and the SQL desktop and
Analysis services
no
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.