Need help urgently.
I have on win 2000 machine a default SQL Server (local) & a named SQL Server
instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to
startup on reboot or manual. The default server on the other hand is runnin
g. But I cannot use the default server as it requires access within the loca
l machine only.
I tried uninstalling the patch, but it still cannot get the SQL server runni
ng again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stop
ped, while the Default Instance (Local) is started. Click start, and return
Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon|||Error listing end at the last restart after patch install. That is, never re
start again.
Almon
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Friday, March 30, 2012
named server failed logon after installing MS04-011 patch
Need help urgently
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine)
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance'
Additional info: On logon, following error massage
"NtUninstall Q8877565\WinSys.cer" not foun
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again
Any idea what's wrong and how I may recover the Instance
Almo|||Error listing end at the last restart after patch install. That is, never restart again
Almo
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine)
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance'
Additional info: On logon, following error massage
"NtUninstall Q8877565\WinSys.cer" not foun
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again
Any idea what's wrong and how I may recover the Instance
Almo|||Error listing end at the last restart after patch install. That is, never restart again
Almo
named server failed logon after installing MS04-011 patch
Need help urgently.
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only.
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.
What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon
|||Error listing end at the last restart after patch install. That is, never restart again.
Almon
sql
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only.
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.
What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon
|||Error listing end at the last restart after patch install. That is, never restart again.
Almon
sql
named pipes under alias
I have a SQLSERVER INSTANCE A, to which I want to connect from a Client as TEST, using the SQL Server alias functionality under the client network utility program. The alias is working fine with the TCP\IP connection but it fails when I try to connect to the SQL Server using the named pipes. In my case I'm trying to connect to a named instance of SQL Server 2000 using the following pipe: \\servername\pipe\mssql$instancename\sql\query
Any help?I have just tried this. Pain in the neck, too. When you change the name of the alias, the client network utility is all helpful, and changes the actual path, and server name. So you have to get the right path, and save it of in notepad or something. Change the name of the alias, replace the name of the server with the name of the server you want, then recover the path from notepad. I tried it, and it did not work. Then I hit the Apply button. Now it works. Does that approximate what you went through?|||I can connect to any server using the alias name with the TCP/IP, but the same doesn't work with the Named Pipes.
Any help?I have just tried this. Pain in the neck, too. When you change the name of the alias, the client network utility is all helpful, and changes the actual path, and server name. So you have to get the right path, and save it of in notepad or something. Change the name of the alias, replace the name of the server with the name of the server you want, then recover the path from notepad. I tried it, and it did not work. Then I hit the Apply button. Now it works. Does that approximate what you went through?|||I can connect to any server using the alias name with the TCP/IP, but the same doesn't work with the Named Pipes.
Wednesday, March 28, 2012
named pipes and sql cluster
Good day,
There is a 2-node microsoft sql 2000 cluster in active/active mode. .
Default instance is on node A, another named instance is on node B.
Client uses BDE while connecting. When the node A fails over to the
node B, it's not possible to connect to the default instance while
using trusted logins. When sql login is used, users can connect..
I can connect via Query Analyzer, but via tcp/ip only(when named pipes
aren't used) at this very moment.
As far as I understand, BDE uses named pipes with trusted logins.
Are there any workarounds?
Thank in advance,
Andrew.
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
Windows NT 5.2 (Build 3790: Service Pack 1)
Andrew,
What is the service pack level for your SQL Server 2000 clustered instance?
As of SQL Server 2000 SP3 -- Named Pipes Support Cannot Be Removed on a Virtual Server That Is Running SQL Server 2000 SP3
Here is the link that explains this
http://support.microsoft.com/default.aspx?kbid=831127
Note: If you are already on SP3a --> On a virtual server that is running SQL 2000 SP3a, an administrator can disable Named Pipes support through SQL Server Enterprise
Manager in SQL Server 2000 SP2 or earlier.
Recommendation:
Although Named Pipes support is not required for a virtual server, Microsoft recommends that both network libraries must be present on the system because of the
following reasons:
Having both network libraries available permits an administrator or an alternative interprocess communication (IPC) mechanism to repair the system.
Clients can continue to work with the virtual server, even if only one server-side network library is available.
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
|||Hi Uttam,
sp3a was installed..
named pipes aren't disabled. I can see them enabled while viewing the
sql servers logs.
Moreover, i can't connect to the moved instance via named pipes using
Query Analyzer as well. Not only our application can't connect.
Andrew.
Uttam Parui[MS] =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> Andrew,
> What is the service pack level for your SQL Server 2000 clustered instanc=
e?
> As of SQL Server 2000 SP3 -- Named Pipes Support Cannot Be Removed on a V=
irtual Server That Is Running SQL Server 2000 SP3
> Here is the link that explains this
> http://support.microsoft.com/default.aspx?kbid=3D831127
> Note: If you are already on SP3a --> On a virtual server that is runnin=
g SQL 2000 SP3a, an administrator can disable Named Pipes support through S=
QL Server Enterprise
> Manager in SQL Server 2000 SP2 or earlier.
> Recommendation:
> Although Named Pipes support is not required for a virtual server, Micros=
oft recommends that both network libraries must be present on the system be=
cause of the
> following reasons:
> Having both network libraries available permits an administrator or an al=
ternative interprocess communication (IPC) mechanism to repair the system.
> Clients can continue to work with the virtual server, even if only one se=
rver-side network library is available.
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no right=
s=2E
> Are you secure? For information about the Strategic Technology Protectio=
n 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 vulnerabi=
lities. The easiest way
> to do this is to visit the following websites: http://www.microsoft.com/p=
rotect
> http://www.microsoft.com/security/guidance/default.mspx
There is a 2-node microsoft sql 2000 cluster in active/active mode. .
Default instance is on node A, another named instance is on node B.
Client uses BDE while connecting. When the node A fails over to the
node B, it's not possible to connect to the default instance while
using trusted logins. When sql login is used, users can connect..
I can connect via Query Analyzer, but via tcp/ip only(when named pipes
aren't used) at this very moment.
As far as I understand, BDE uses named pipes with trusted logins.
Are there any workarounds?
Thank in advance,
Andrew.
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
Windows NT 5.2 (Build 3790: Service Pack 1)
Andrew,
What is the service pack level for your SQL Server 2000 clustered instance?
As of SQL Server 2000 SP3 -- Named Pipes Support Cannot Be Removed on a Virtual Server That Is Running SQL Server 2000 SP3
Here is the link that explains this
http://support.microsoft.com/default.aspx?kbid=831127
Note: If you are already on SP3a --> On a virtual server that is running SQL 2000 SP3a, an administrator can disable Named Pipes support through SQL Server Enterprise
Manager in SQL Server 2000 SP2 or earlier.
Recommendation:
Although Named Pipes support is not required for a virtual server, Microsoft recommends that both network libraries must be present on the system because of the
following reasons:
Having both network libraries available permits an administrator or an alternative interprocess communication (IPC) mechanism to repair the system.
Clients can continue to work with the virtual server, even if only one server-side network library is available.
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
|||Hi Uttam,
sp3a was installed..
named pipes aren't disabled. I can see them enabled while viewing the
sql servers logs.
Moreover, i can't connect to the moved instance via named pipes using
Query Analyzer as well. Not only our application can't connect.
Andrew.
Uttam Parui[MS] =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> Andrew,
> What is the service pack level for your SQL Server 2000 clustered instanc=
e?
> As of SQL Server 2000 SP3 -- Named Pipes Support Cannot Be Removed on a V=
irtual Server That Is Running SQL Server 2000 SP3
> Here is the link that explains this
> http://support.microsoft.com/default.aspx?kbid=3D831127
> Note: If you are already on SP3a --> On a virtual server that is runnin=
g SQL 2000 SP3a, an administrator can disable Named Pipes support through S=
QL Server Enterprise
> Manager in SQL Server 2000 SP2 or earlier.
> Recommendation:
> Although Named Pipes support is not required for a virtual server, Micros=
oft recommends that both network libraries must be present on the system be=
cause of the
> following reasons:
> Having both network libraries available permits an administrator or an al=
ternative interprocess communication (IPC) mechanism to repair the system.
> Clients can continue to work with the virtual server, even if only one se=
rver-side network library is available.
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no right=
s=2E
> Are you secure? For information about the Strategic Technology Protectio=
n 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 vulnerabi=
lities. The easiest way
> to do this is to visit the following websites: http://www.microsoft.com/p=
rotect
> http://www.microsoft.com/security/guidance/default.mspx
named pipes
The cluster consists of two nodes and of two instances. One default sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
Have you run cliconfg.exe on both nodes, not just the "primary"?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
The cluster consists of two nodes and of two instances. One default sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
|||I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>=20
>=20
>=20
> Thanks in advance.
> Andrew
|||This sounds strange. Have you tried removing the aliases from the client
machines?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau писал(а):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
> Thanks in advance.
> Andrew
|||If i remove - i just can't connect..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
|||This sounds like either a DNS issue or that SQL Server is not listening on
TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
Server errorlog to see what protocols SQL Server will "hear". Also, ensure
that your clients are using TCP/IP. Check out their Client Network Utility
to confirm.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
If i remove - i just can't connect..
Andrew
Tom Moreau писал(а):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau писал(а):
|||with tcp/ip everything is ok. I've a problem with named pipes. Our
application isn't tcp/ip aware, just named pipes - thats all.
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> This sounds like either a DNS issue or that SQL Server is not listening on
> TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
> Server errorlog to see what protocols SQL Server will "hear". Also, ensu=
re
> that your clients are using TCP/IP. Check out their Client Network Utili=
ty[vbcol=seagreen]
> to confirm.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
> If i remove - i just can't connect..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
nt[vbcol=seagreen]
ql[vbcol=seagreen]
s?[vbcol=seagreen]
|||ok, for example
Active-Active cluster. One instance server1, another one -
server2\instance
Since my application isnt't cluster aware i create an alias to connect
via named pipes.
- server alias: server2
- server name: server2\instance
- pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
when server2 fails over to server1 i can't use my application. At this
moment I can ping server2 successfully.
If i change on the client the alias server2:
- server alias: server2 (it's the same)
- server name: server1
- pipe name: \\server1\pipe\\sql\query
I can connect and can't use my application
|||kreit wrote:
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
Maybe some of the registry is not replicated. In the cluster registry
there should be about 7 registry entries for each sql server resource
which are used to replicate some of the sql registry keys. Check if they
exist. Also check the contents of software\microsoft\microsoft sql
server\instance\mssqlserver\supersocketnetlib\np\p ipename on the problem
node when sql is running there.
The service account of the default instance should be able to read the
registry key's of the named instance and vice versa. Sqlservers log
mentions its listening on named pipes?
What I think is kind of strange is that you are able to use the client
network tools aliases but not tcp\ip. Your program should not even know
about named pipes or tcp/ip. It just needs to talk to the sqldriver.
Maybe its time to instal ethereal (http://www.ethereal.com/) on one of
the clients.
Hans
|||kreit wrote:
> ok, for example
> Active-Active cluster. One instance server1, another one -
> server2\instance
> Since my application isnt't cluster aware i create an alias to connect
> via named pipes.
> - server alias: server2
> - server name: server2\instance
> - pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
>
> when server2 fails over to server1 i can't use my application. At this
> moment I can ping server2 successfully.
> If i change on the client the alias server2:
> - server alias: server2 (it's the same)
> - server name: server1
> - pipe name: \\server1\pipe\\sql\query
> I can connect and can't use my application
>
Just to make very sure, you do know the difference between the virtual
server name and the node name?
'when server2 fails over to server1 i can't use my application'
should be:
'when virtual server2 fails over to node1 i can't use my application'
Clients should connect to the virtual server name and not to the not to
the name of the physical server.
Hans
sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
Have you run cliconfg.exe on both nodes, not just the "primary"?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
The cluster consists of two nodes and of two instances. One default sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
|||I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>=20
>=20
>=20
> Thanks in advance.
> Andrew
|||This sounds strange. Have you tried removing the aliases from the client
machines?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau писал(а):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
> Thanks in advance.
> Andrew
|||If i remove - i just can't connect..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
|||This sounds like either a DNS issue or that SQL Server is not listening on
TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
Server errorlog to see what protocols SQL Server will "hear". Also, ensure
that your clients are using TCP/IP. Check out their Client Network Utility
to confirm.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
If i remove - i just can't connect..
Andrew
Tom Moreau писал(а):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau писал(а):
|||with tcp/ip everything is ok. I've a problem with named pipes. Our
application isn't tcp/ip aware, just named pipes - thats all.
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> This sounds like either a DNS issue or that SQL Server is not listening on
> TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
> Server errorlog to see what protocols SQL Server will "hear". Also, ensu=
re
> that your clients are using TCP/IP. Check out their Client Network Utili=
ty[vbcol=seagreen]
> to confirm.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
> If i remove - i just can't connect..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
nt[vbcol=seagreen]
ql[vbcol=seagreen]
s?[vbcol=seagreen]
|||ok, for example
Active-Active cluster. One instance server1, another one -
server2\instance
Since my application isnt't cluster aware i create an alias to connect
via named pipes.
- server alias: server2
- server name: server2\instance
- pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
when server2 fails over to server1 i can't use my application. At this
moment I can ping server2 successfully.
If i change on the client the alias server2:
- server alias: server2 (it's the same)
- server name: server1
- pipe name: \\server1\pipe\\sql\query
I can connect and can't use my application
|||kreit wrote:
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
Maybe some of the registry is not replicated. In the cluster registry
there should be about 7 registry entries for each sql server resource
which are used to replicate some of the sql registry keys. Check if they
exist. Also check the contents of software\microsoft\microsoft sql
server\instance\mssqlserver\supersocketnetlib\np\p ipename on the problem
node when sql is running there.
The service account of the default instance should be able to read the
registry key's of the named instance and vice versa. Sqlservers log
mentions its listening on named pipes?
What I think is kind of strange is that you are able to use the client
network tools aliases but not tcp\ip. Your program should not even know
about named pipes or tcp/ip. It just needs to talk to the sqldriver.
Maybe its time to instal ethereal (http://www.ethereal.com/) on one of
the clients.
Hans
|||kreit wrote:
> ok, for example
> Active-Active cluster. One instance server1, another one -
> server2\instance
> Since my application isnt't cluster aware i create an alias to connect
> via named pipes.
> - server alias: server2
> - server name: server2\instance
> - pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
>
> when server2 fails over to server1 i can't use my application. At this
> moment I can ping server2 successfully.
> If i change on the client the alias server2:
> - server alias: server2 (it's the same)
> - server name: server1
> - pipe name: \\server1\pipe\\sql\query
> I can connect and can't use my application
>
Just to make very sure, you do know the difference between the virtual
server name and the node name?
'when server2 fails over to server1 i can't use my application'
should be:
'when virtual server2 fails over to node1 i can't use my application'
Clients should connect to the virtual server name and not to the not to
the name of the physical server.
Hans
sql
Monday, March 26, 2012
Named Instances
During the install SQL 2000 askes to use the default to name a instance. Is
it better to name the instance or use the default? What is the function of
instances in SQL?Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:
> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which it
> is running. Applications using client software from earlier versions of SQL
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
> ar_cs_9i5u.asp
> Working with Named and Multiple Instances of SQL Server 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_
> runsetup_2xmb.asp
> Multiple Instances
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/
> html/MultipleInstances.asp
>
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
it better to name the instance or use the default? What is the function of
instances in SQL?Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:
> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which it
> is running. Applications using client software from earlier versions of SQL
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
> ar_cs_9i5u.asp
> Working with Named and Multiple Instances of SQL Server 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_
> runsetup_2xmb.asp
> Multiple Instances
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/
> html/MultipleInstances.asp
>
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Named Instances
When applying patches if I have a default instance and
named instance on the same server, does the patch affect
both instances or can I patch them seperate?The executable code for each instance is deliberatly in a separate =directory so patches affect each instance seperately. This is so you can =test thingsin isolation. The exception to this is patches to tye clein =tools (Query Analyser, EM etc) as these are shared between instances.
Mike John
"Larry" <anonymous@.discussions.microsoft.com> wrote in message =news:04c901c39421$f2c73900$a101280a@.phx.gbl...
> When applying patches if I have a default instance and > named instance on the same server, does the patch affect > both instances or can I patch them seperate?|||Larry,
Your only choice is to apply them separately. Think of it as two machines
hiding in one box.
Russell Fields
"Larry" <anonymous@.discussions.microsoft.com> wrote in message
news:04c901c39421$f2c73900$a101280a@.phx.gbl...
> When applying patches if I have a default instance and
> named instance on the same server, does the patch affect
> both instances or can I patch them seperate?|||Larry,
A named instance is essentially a different server from
the default instance (and any other named instances).
You must patch all instances separately.
Tim
>--Original Message--
>When applying patches if I have a default instance and
>named instance on the same server, does the patch affect
>both instances or can I patch them seperate?
>.
>
named instance on the same server, does the patch affect
both instances or can I patch them seperate?The executable code for each instance is deliberatly in a separate =directory so patches affect each instance seperately. This is so you can =test thingsin isolation. The exception to this is patches to tye clein =tools (Query Analyser, EM etc) as these are shared between instances.
Mike John
"Larry" <anonymous@.discussions.microsoft.com> wrote in message =news:04c901c39421$f2c73900$a101280a@.phx.gbl...
> When applying patches if I have a default instance and > named instance on the same server, does the patch affect > both instances or can I patch them seperate?|||Larry,
Your only choice is to apply them separately. Think of it as two machines
hiding in one box.
Russell Fields
"Larry" <anonymous@.discussions.microsoft.com> wrote in message
news:04c901c39421$f2c73900$a101280a@.phx.gbl...
> When applying patches if I have a default instance and
> named instance on the same server, does the patch affect
> both instances or can I patch them seperate?|||Larry,
A named instance is essentially a different server from
the default instance (and any other named instances).
You must patch all instances separately.
Tim
>--Original Message--
>When applying patches if I have a default instance and
>named instance on the same server, does the patch affect
>both instances or can I patch them seperate?
>.
>
Named Instances
During the install SQL 2000 askes to use the default to name a instance. I
s
it better to name the instance or use the default? What is the function of
instances in SQL?Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/d...-us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:
> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which i
t
> is running. Applications using client software from earlier versions of SQ
L
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at
a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/d...ft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
s
it better to name the instance or use the default? What is the function of
instances in SQL?Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/d...-us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:
> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which i
t
> is running. Applications using client software from earlier versions of SQ
L
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at
a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/d...ft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Named Instances
In SQL 2000 Clustering, can I have only one default instance for the entire
cluster or can I have one default per virtual server. In other words, can
all my SQL installs in a cluster be default, each on a different virtual
server?
1 Default or no default. Then you can have up to 15 named or all 16 can be
named
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Arun" <aganesan@.esurance.com> wrote in message
news:OqFY8U5dFHA.3492@.TK2MSFTNGP14.phx.gbl...
> In SQL 2000 Clustering, can I have only one default instance for the
> entire
> cluster or can I have one default per virtual server. In other words, can
> all my SQL installs in a cluster be default, each on a different virtual
> server?
>
|||Each Instance gets its own virtual server. Due to SQL Instance naming
restrictions, you still only get one default instance per cluster.
Personally, I prefer to use only Named Instances on a cluster, just to keep
name appearances consistent.
Geoff N. Hiten
Microsoft SQL Server MVP
"Arun" <aganesan@.esurance.com> wrote in message
news:OqFY8U5dFHA.3492@.TK2MSFTNGP14.phx.gbl...
> In SQL 2000 Clustering, can I have only one default instance for the
> entire
> cluster or can I have one default per virtual server. In other words, can
> all my SQL installs in a cluster be default, each on a different virtual
> server?
>
cluster or can I have one default per virtual server. In other words, can
all my SQL installs in a cluster be default, each on a different virtual
server?
1 Default or no default. Then you can have up to 15 named or all 16 can be
named
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Arun" <aganesan@.esurance.com> wrote in message
news:OqFY8U5dFHA.3492@.TK2MSFTNGP14.phx.gbl...
> In SQL 2000 Clustering, can I have only one default instance for the
> entire
> cluster or can I have one default per virtual server. In other words, can
> all my SQL installs in a cluster be default, each on a different virtual
> server?
>
|||Each Instance gets its own virtual server. Due to SQL Instance naming
restrictions, you still only get one default instance per cluster.
Personally, I prefer to use only Named Instances on a cluster, just to keep
name appearances consistent.
Geoff N. Hiten
Microsoft SQL Server MVP
"Arun" <aganesan@.esurance.com> wrote in message
news:OqFY8U5dFHA.3492@.TK2MSFTNGP14.phx.gbl...
> In SQL 2000 Clustering, can I have only one default instance for the
> entire
> cluster or can I have one default per virtual server. In other words, can
> all my SQL installs in a cluster be default, each on a different virtual
> server?
>
Named Instances
During the install SQL 2000 askes to use the default to name a instance. Is
it better to name the instance or use the default? What is the function of
instances in SQL?
Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/de...us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/de...us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/de...us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:
> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which it
> is running. Applications using client software from earlier versions of SQL
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/de...us/architec/8_
> ar_cs_9i5u.asp
> Working with Named and Multiple Instances of SQL Server 2000
> http://msdn.microsoft.com/library/de...us/instsql/in_
> runsetup_2xmb.asp
> Multiple Instances
> http://msdn.microsoft.com/library/de...us/dnsqlmag2k/
> html/MultipleInstances.asp
>
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
it better to name the instance or use the default? What is the function of
instances in SQL?
Hello,
With Microsoft SQL Server 2000, you have the option of installing multiple
copies, or instances of SQL Server on one computer. When setting up a new
installation of SQL Server 2000 or maintaining an existing installation,
you can specify it as:
A default instance of SQL Server.
This instance is identified by the network name of the computer on which it
is running. Applications using client software from earlier versions of SQL
Server can connect to a default instance. SQL Server version 6.5 or SQL
Server version 7.0 servers can operate as default instances. However, a
computer can have only ONE version functioning as the default instance at a
time.
A named instance of SQL Server.
This instance is identified by the network name of the computer plus an
instance name, in the format <computername>\<instancename>. Applications
must use SQL Server 2000 client components to connect to a named instance.
A computer can run any number of named instances of SQL Server
concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The
instance name cannot exceed 16 characters.
The maximum number of instances supported in SQL Server 2000 is 16. For
more information, refer to the following articles:
Multiple Instances of SQL Server
http://msdn.microsoft.com/library/de...us/architec/8_
ar_cs_9i5u.asp
Working with Named and Multiple Instances of SQL Server 2000
http://msdn.microsoft.com/library/de...us/instsql/in_
runsetup_2xmb.asp
Multiple Instances
http://msdn.microsoft.com/library/de...us/dnsqlmag2k/
html/MultipleInstances.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||If the server later changes name or joins a domain will th instance name
change as well. What I'm doing is replacing are existing SQL server with a
new SQL Server. I've named the new server newsql and made it a member of a
workgroup. After I move the databses over I would then change change the
name on the old server and then make the new server the name of the old
server and join it to the domain. Will the instance name chnage when the
server's name changes?
"Sophie Guo [MSFT]" wrote:
> Hello,
> With Microsoft SQL Server 2000, you have the option of installing multiple
> copies, or instances of SQL Server on one computer. When setting up a new
> installation of SQL Server 2000 or maintaining an existing installation,
> you can specify it as:
> A default instance of SQL Server.
> This instance is identified by the network name of the computer on which it
> is running. Applications using client software from earlier versions of SQL
> Server can connect to a default instance. SQL Server version 6.5 or SQL
> Server version 7.0 servers can operate as default instances. However, a
> computer can have only ONE version functioning as the default instance at a
> time.
> A named instance of SQL Server.
> This instance is identified by the network name of the computer plus an
> instance name, in the format <computername>\<instancename>. Applications
> must use SQL Server 2000 client components to connect to a named instance.
> A computer can run any number of named instances of SQL Server
> concurrently. A named instance can run at the same time as an existing
> installation of SQL Server version 6.5 or SQL Server version 7.0. The
> instance name cannot exceed 16 characters.
> The maximum number of instances supported in SQL Server 2000 is 16. For
> more information, refer to the following articles:
> Multiple Instances of SQL Server
> http://msdn.microsoft.com/library/de...us/architec/8_
> ar_cs_9i5u.asp
> Working with Named and Multiple Instances of SQL Server 2000
> http://msdn.microsoft.com/library/de...us/instsql/in_
> runsetup_2xmb.asp
> Multiple Instances
> http://msdn.microsoft.com/library/de...us/dnsqlmag2k/
> html/MultipleInstances.asp
>
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hello,
After renaming a server, we can perform the following steps to rename SQL
server instance:
1. Restart the server and then start the SQL Server service. This should
automatically get the *new* Server name and we only need to run the
following procedures to
update syservers system table:
-- For a default instance
EXEC sp_dropserver ''old_name''
GO
EXEC sp_addserver ''new_name'', local
GO
-- For a named instance
EXEC sp_dropserver ''original_name\original_instance_name''
GO
EXEC sp_addserver ''new_server_name\instance_name'', local
GO
2. After running the sp_addserver stored procedure, we must restart the SQL
Server service for the change to take effect. The following article
describes this
scenario in more detail:
303774 BUG: "Renaming A Server" Topic in SQL Server Books Online is
Incomplete
http://support.microsoft.com/?id=303774
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Named instance, no default instance -> connection problems?
Hey,
I have the following problem with deployment of MSDE. Here's what I want
to do:
- I want to install MSDE in a named instance, even if it wasn't installed
before.
- I want to connect to the local server only, if possible with a
"generic" name, so I don't have to look up the system name
and stuff.
I can't really get this to work at all. I have connection strings that
work fine on development machines (where the default instance name is
used), using . for the server name. On the test machine, using
..\MYINSTANCE doesn't work at all. I read suggestions to use
(local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
a default instance running on the same machine. Plus, it seems cumbersome
to have to find out the system's name for such a purpose.
Maybe I'm just seriously wrong about something... I didn't think it would
be that hard to set up a local (!, no networking enabled) database server
using the standard (!, they do say I'm to use a vendor-specific instance,
don't they?) setup procedure and connect to that.
Any ideas, please?
Oliver Sturm
omnibus ex nihilo ducendis sufficit unum
MSN oliver@.sturmnet.org Jabber sturm@.amessage.de ICQ 27142619
hi Oliver,
"Oliver Sturm" <oliver@.sturmnet.org> ha scritto nel messaggio
news:pan.2004.06.18.10.39.55.285051@.sturmnet.org.. .
> Hey,
> I have the following problem with deployment of MSDE. Here's what I want
> to do:
> - I want to install MSDE in a named instance, even if it wasn't installed
> before.
> - I want to connect to the local server only, if possible with a
> "generic" name, so I don't have to look up the system name
> and stuff.
> I can't really get this to work at all. I have connection strings that
> work fine on development machines (where the default instance name is
> used), using . for the server name. On the test machine, using
> .\MYINSTANCE doesn't work at all. I read suggestions to use
> (local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
> The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
> a default instance running on the same machine. Plus, it seems cumbersome
> to have to find out the system's name for such a purpose.
> Maybe I'm just seriously wrong about something... I didn't think it would
> be that hard to set up a local (!, no networking enabled) database server
> using the standard (!, they do say I'm to use a vendor-specific instance,
> don't they?) setup procedure and connect to that.
> Any ideas, please?
that's weird, becouse (local)\InstanceName shoul'd be fine..... ok, I'm
running a pc with a default instance and a named instance...
as regard the ComputerName part, remember you are trying to connect to a
service specified on the target pc...
you can always set an Alias via Client Network Utility, but this is not the
case... but building the connection string using something similar to Public
Declare Function GetComputerName Lib "kernel32" Alias "GetComputerNameA"
(ByVal lpBuffer As String, nSize As Long) As Long, appending the
"\YourInstanceName", in your preferred language, coul'd solve the problem
too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql
I have the following problem with deployment of MSDE. Here's what I want
to do:
- I want to install MSDE in a named instance, even if it wasn't installed
before.
- I want to connect to the local server only, if possible with a
"generic" name, so I don't have to look up the system name
and stuff.
I can't really get this to work at all. I have connection strings that
work fine on development machines (where the default instance name is
used), using . for the server name. On the test machine, using
..\MYINSTANCE doesn't work at all. I read suggestions to use
(local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
a default instance running on the same machine. Plus, it seems cumbersome
to have to find out the system's name for such a purpose.
Maybe I'm just seriously wrong about something... I didn't think it would
be that hard to set up a local (!, no networking enabled) database server
using the standard (!, they do say I'm to use a vendor-specific instance,
don't they?) setup procedure and connect to that.
Any ideas, please?
Oliver Sturm
omnibus ex nihilo ducendis sufficit unum
MSN oliver@.sturmnet.org Jabber sturm@.amessage.de ICQ 27142619
hi Oliver,
"Oliver Sturm" <oliver@.sturmnet.org> ha scritto nel messaggio
news:pan.2004.06.18.10.39.55.285051@.sturmnet.org.. .
> Hey,
> I have the following problem with deployment of MSDE. Here's what I want
> to do:
> - I want to install MSDE in a named instance, even if it wasn't installed
> before.
> - I want to connect to the local server only, if possible with a
> "generic" name, so I don't have to look up the system name
> and stuff.
> I can't really get this to work at all. I have connection strings that
> work fine on development machines (where the default instance name is
> used), using . for the server name. On the test machine, using
> .\MYINSTANCE doesn't work at all. I read suggestions to use
> (local)\MYINSTANCE instead of .\MYINSTANCE, but to no avail.
> The funny thing is, even SYSTEMNAME\MYINSTANCE doesn't work unless there's
> a default instance running on the same machine. Plus, it seems cumbersome
> to have to find out the system's name for such a purpose.
> Maybe I'm just seriously wrong about something... I didn't think it would
> be that hard to set up a local (!, no networking enabled) database server
> using the standard (!, they do say I'm to use a vendor-specific instance,
> don't they?) setup procedure and connect to that.
> Any ideas, please?
that's weird, becouse (local)\InstanceName shoul'd be fine..... ok, I'm
running a pc with a default instance and a named instance...
as regard the ComputerName part, remember you are trying to connect to a
service specified on the target pc...
you can always set an Alias via Client Network Utility, but this is not the
case... but building the connection string using something similar to Public
Declare Function GetComputerName Lib "kernel32" Alias "GetComputerNameA"
(ByVal lpBuffer As String, nSize As Long) As Long, appending the
"\YourInstanceName", in your preferred language, coul'd solve the problem
too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql
Named Instance, Connectivity Question
I had XP Machine, with SQL Server 2000 Client
preinstalled.
This week, I installed MSDE 2000 under Named Instance.
After this, I restart my PC, I can see the Names Instance
is up running under Service window.
By My SQL server Enterprise Manager and SQL Analyzer wont
see the instance or any MSDE server.
Then I installed default Instance(no name), then
Enterprise Manager and SQL Analyzer can see MSDE sever
under LOCAL name, I assume this is the default instance.
My VB Data Enviroment can see a MSDE server under my
Computer name.
My Questiona are:
1. How do I login the named instance?
2. can I installed Named instance alone without a default
instance? if not, does the install sequence matters?
3. how to rollback my installation in case I want retry?
Greg Chang
hi Greg,
"Greg Chang" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:176dc01c418d4$3cb51410$a501280a@.phx.gbl...
> I had XP Machine, with SQL Server 2000 Client
> preinstalled.
> This week, I installed MSDE 2000 under Named Instance.
> After this, I restart my PC, I can see the Names Instance
> is up running under Service window.
> By My SQL server Enterprise Manager and SQL Analyzer wont
> see the instance or any MSDE server.
> Then I installed default Instance(no name), then
> Enterprise Manager and SQL Analyzer can see MSDE sever
> under LOCAL name, I assume this is the default instance.
> My VB Data Enviroment can see a MSDE server under my
> Computer name.
thi can be due to
http://support.microsoft.com/default...b;EN-US;814132 ...
there are other undocumented issues regarding instance names not showing up
in the service manager list thought...
> My Questiona are:
> 1. How do I login the named instance?
you must provide the full name as ComputerName\InstanceName
> 2. can I installed Named instance alone without a default
> instance? if not, does the install sequence matters?
yes, you can install only a named instance, only a default instance, or upt
to 15 named instances and 1 default instance...
> 3. how to rollback my installation in case I want retry?
you have to fully uninstall it... go in control panel and use the
install/uninstall applet...
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
preinstalled.
This week, I installed MSDE 2000 under Named Instance.
After this, I restart my PC, I can see the Names Instance
is up running under Service window.
By My SQL server Enterprise Manager and SQL Analyzer wont
see the instance or any MSDE server.
Then I installed default Instance(no name), then
Enterprise Manager and SQL Analyzer can see MSDE sever
under LOCAL name, I assume this is the default instance.
My VB Data Enviroment can see a MSDE server under my
Computer name.
My Questiona are:
1. How do I login the named instance?
2. can I installed Named instance alone without a default
instance? if not, does the install sequence matters?
3. how to rollback my installation in case I want retry?
Greg Chang
hi Greg,
"Greg Chang" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:176dc01c418d4$3cb51410$a501280a@.phx.gbl...
> I had XP Machine, with SQL Server 2000 Client
> preinstalled.
> This week, I installed MSDE 2000 under Named Instance.
> After this, I restart my PC, I can see the Names Instance
> is up running under Service window.
> By My SQL server Enterprise Manager and SQL Analyzer wont
> see the instance or any MSDE server.
> Then I installed default Instance(no name), then
> Enterprise Manager and SQL Analyzer can see MSDE sever
> under LOCAL name, I assume this is the default instance.
> My VB Data Enviroment can see a MSDE server under my
> Computer name.
thi can be due to
http://support.microsoft.com/default...b;EN-US;814132 ...
there are other undocumented issues regarding instance names not showing up
in the service manager list thought...
> My Questiona are:
> 1. How do I login the named instance?
you must provide the full name as ComputerName\InstanceName
> 2. can I installed Named instance alone without a default
> instance? if not, does the install sequence matters?
yes, you can install only a named instance, only a default instance, or upt
to 15 named instances and 1 default instance...
> 3. how to rollback my installation in case I want retry?
you have to fully uninstall it... go in control panel and use the
install/uninstall applet...
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Named Instance timeout problem
I am running two large applications on a 4 cpu SQL server with 2 named insta
nces.
There are times when I am running a query on one named instance that users o
n the other instance are getting time out errors. I am trying to justify gi
ving each instance limits on which cpu's they can use and also potentially m
emory. I tried giving the
more critical application 3 cpu's and the other one cpu. There was still a
similar problem on the critical app when running a intensive query on the ot
her which was just allocated one cpu. My boss insisted that I change both b
ack to sharing all cpu's.
My argument is that if both can hog all 4 cpu's, I can guarantee that there
will be a problem.
When the large queries are running, the HD lights are on constant and the CP
U's are all pegged at 100%. The databases for each application are stored o
n their own mirrored HD.
I was wondering if anyone out there has experienced a similar problem and wo
ndering where to go from here.
Thank You,
EverettWe went with defaults when the instance was installed. I think both are
dynamic.
"Vikram Jayaram [MS]" wrote:
> What about memory allocation? Are both instnaces alloted to have Dynamic
> Memory? In that case one instnace could be hogging system memory and not
> granting the other enough, on time.
> Vikram Jayaram
> Microsoft, SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
>|||Right then., Try alloting one of those to fixed memory of a lesser amount
and see if the behaviour still exists. Worth a try!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
nces.
There are times when I am running a query on one named instance that users o
n the other instance are getting time out errors. I am trying to justify gi
ving each instance limits on which cpu's they can use and also potentially m
emory. I tried giving the
more critical application 3 cpu's and the other one cpu. There was still a
similar problem on the critical app when running a intensive query on the ot
her which was just allocated one cpu. My boss insisted that I change both b
ack to sharing all cpu's.
My argument is that if both can hog all 4 cpu's, I can guarantee that there
will be a problem.
When the large queries are running, the HD lights are on constant and the CP
U's are all pegged at 100%. The databases for each application are stored o
n their own mirrored HD.
I was wondering if anyone out there has experienced a similar problem and wo
ndering where to go from here.
Thank You,
EverettWe went with defaults when the instance was installed. I think both are
dynamic.
"Vikram Jayaram [MS]" wrote:
> What about memory allocation? Are both instnaces alloted to have Dynamic
> Memory? In that case one instnace could be hogging system memory and not
> granting the other enough, on time.
> Vikram Jayaram
> Microsoft, SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
>|||Right then., Try alloting one of those to fixed memory of a lesser amount
and see if the behaviour still exists. Worth a try!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Named Instance timeout problem
I am running two large applications on a 4 cpu SQL server with 2 named instances.
There are times when I am running a query on one named instance that users on the other instance are getting time out errors. I am trying to justify giving each instance limits on which cpu's they can use and also potentially memory. I tried giving the
more critical application 3 cpu's and the other one cpu. There was still a similar problem on the critical app when running a intensive query on the other which was just allocated one cpu. My boss insisted that I change both back to sharing all cpu's.
My argument is that if both can hog all 4 cpu's, I can guarantee that there will be a problem.
When the large queries are running, the HD lights are on constant and the CPU's are all pegged at 100%. The databases for each application are stored on their own mirrored HD.
I was wondering if anyone out there has experienced a similar problem and wondering where to go from here.
Thank You,
Everett
We went with defaults when the instance was installed. I think both are
dynamic.
"Vikram Jayaram [MS]" wrote:
> What about memory allocation? Are both instnaces alloted to have Dynamic
> Memory? In that case one instnace could be hogging system memory and not
> granting the other enough, on time.
> Vikram Jayaram
> Microsoft, SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
>
|||Right then., Try alloting one of those to fixed memory of a lesser amount
and see if the behaviour still exists. Worth a try!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
There are times when I am running a query on one named instance that users on the other instance are getting time out errors. I am trying to justify giving each instance limits on which cpu's they can use and also potentially memory. I tried giving the
more critical application 3 cpu's and the other one cpu. There was still a similar problem on the critical app when running a intensive query on the other which was just allocated one cpu. My boss insisted that I change both back to sharing all cpu's.
My argument is that if both can hog all 4 cpu's, I can guarantee that there will be a problem.
When the large queries are running, the HD lights are on constant and the CPU's are all pegged at 100%. The databases for each application are stored on their own mirrored HD.
I was wondering if anyone out there has experienced a similar problem and wondering where to go from here.
Thank You,
Everett
We went with defaults when the instance was installed. I think both are
dynamic.
"Vikram Jayaram [MS]" wrote:
> What about memory allocation? Are both instnaces alloted to have Dynamic
> Memory? In that case one instnace could be hogging system memory and not
> granting the other enough, on time.
> Vikram Jayaram
> Microsoft, SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
>
|||Right then., Try alloting one of those to fixed memory of a lesser amount
and see if the behaviour still exists. Worth a try!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Named Instance stack dump upon startup
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
I have a SQL server for a document imaging application. SQL is installed
along with a named instance that is necessary for the application. I was not
involved in the installation or setup of this machine, but now the
responsibility has fallen to me to maintain it.
The named instance occasionally (once every other month) generates a stack
dump upon startup. Generally all I have to do to "clean" this up is to stop
and restart SQL and it's services, or a reboot. Yesterday I found myself in
this situation again, but the normal "fixes" did not resolve it. This morning
I was searching the net for clues, and still attempting to shutdown and
restart SQL, when SQL finally cooperated and started clean - the app works
fine now.
I have never found anything in the event viewer to give me a hint. The
information in the logs has not provided me with any answers, though I am
pretty inexperiened in that area. I have not been able to find any of the log
contents in MSKB or elsewhere.
I am confident enough to reinstall SQL, to see if any of this is fixed, but
the application's consultant is afraid that the app will break if I do that.
I need to take the time to FIX this rather than band-aiding it when it
breaks. I inherited this last summer, but the issue has been occurring for 2
years, and the server's previous caretaker did not deal with it. The other
hindrance is that our company will be closing this time next year, so the
attitude here is to just keep things running, without any new investment.
Any help with this is much appreciated! Thank-you!!!
Part of the log is listed below:
2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-03-22 08:37:42.80 server All rights reserved.
2005-03-22 08:37:42.80 server Server Process ID is 696.
2005-03-22 08:37:42.80 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
2005-03-22 08:37:42.82 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2005-03-22 08:37:42.92 server SQL Server configured for thread mode
processing.
2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'master'
(1).
2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (1)
2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977,
127.0.0.1:3977.
2005-03-22 08:37:44.88 server SQL Server is ready for client connections
2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
2005-03-22 08:37:45.50 spid2 Recovery complete.
2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL$LASERFICHE\log\SQL00640.dmp
2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
..
..
..
2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
c0000005 caught.
Karen
"There are two documents in your in-box: tragedy and comedy. Your Pick."
--Dale Dauten
Hi
Install sp3a for SQL Server 2000. You have no Service Pack on that instance.
Server Version: http://www.aspfaq.com/show.asp?id=2160
Regards
Mike
"Karen" wrote:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> I have a SQL server for a document imaging application. SQL is installed
> along with a named instance that is necessary for the application. I was not
> involved in the installation or setup of this machine, but now the
> responsibility has fallen to me to maintain it.
> The named instance occasionally (once every other month) generates a stack
> dump upon startup. Generally all I have to do to "clean" this up is to stop
> and restart SQL and it's services, or a reboot. Yesterday I found myself in
> this situation again, but the normal "fixes" did not resolve it. This morning
> I was searching the net for clues, and still attempting to shutdown and
> restart SQL, when SQL finally cooperated and started clean - the app works
> fine now.
> I have never found anything in the event viewer to give me a hint. The
> information in the logs has not provided me with any answers, though I am
> pretty inexperiened in that area. I have not been able to find any of the log
> contents in MSKB or elsewhere.
> I am confident enough to reinstall SQL, to see if any of this is fixed, but
> the application's consultant is afraid that the app will break if I do that.
> I need to take the time to FIX this rather than band-aiding it when it
> breaks. I inherited this last summer, but the issue has been occurring for 2
> years, and the server's previous caretaker did not deal with it. The other
> hindrance is that our company will be closing this time next year, so the
> attitude here is to just keep things running, without any new investment.
> Any help with this is much appreciated! Thank-you!!!
> Part of the log is listed below:
> --
> 2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
> X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporation.
> 2005-03-22 08:37:42.80 server All rights reserved.
> 2005-03-22 08:37:42.80 server Server Process ID is 696.
> 2005-03-22 08:37:42.80 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
> 2005-03-22 08:37:42.82 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2005-03-22 08:37:42.92 server SQL Server configured for thread mode
> processing.
> 2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
> 2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'master'
> (1).
> 2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (1)
> 2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
> 2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
> 2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
> 2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
> 2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
> 2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977,
> 127.0.0.1:3977.
> 2005-03-22 08:37:44.88 server SQL Server is ready for client connections
> 2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
> 2005-03-22 08:37:45.50 spid2 Recovery complete.
> 2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
> Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL$LASERFICHE\log\SQL00640.dmp
> 2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
> fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> .
> .
> .
> 2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
> c0000005 caught.
> Karen
> "There are two documents in your in-box: tragedy and comedy. Your Pick."
> --Dale Dauten
|||Thanks, Mike, but I have never been able to get sp3a applied to the instance.
It has been a few months since the last time I tried, so I do not have the
error available, and it will be a few days until I can try again.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Install sp3a for SQL Server 2000. You have no Service Pack on that instance.
> Server Version: http://www.aspfaq.com/show.asp?id=2160
> Regards
> Mike
|||Hi
The fact that sp3a will not install indicates that there is something wrong
with the machine or installation. So getting stack dumps is not unexpected.
Regards
Mike
"Karen" wrote:
> Thanks, Mike, but I have never been able to get sp3a applied to the instance.
> It has been a few months since the last time I tried, so I do not have the
> error available, and it will be a few days until I can try again.
> "Mike Epprecht (SQL MVP)" wrote:
>
|||Hi Mike,
It certainly does.
I have discovered that the named instance really isn't a named instance, it
is MSDE, so it is understandable that the sp's did not install. It would have
been nice if the SP install would have given a message to the fact that it
was the wrong version, but that would have been too easy!
I will install the correct sp this week & perhaps there will no longer be
any problems.
Thanks,
Karen
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The fact that sp3a will not install indicates that there is something wrong
> with the machine or installation. So getting stack dumps is not unexpected.
> Regards
> Mike
> "Karen" wrote:
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
I have a SQL server for a document imaging application. SQL is installed
along with a named instance that is necessary for the application. I was not
involved in the installation or setup of this machine, but now the
responsibility has fallen to me to maintain it.
The named instance occasionally (once every other month) generates a stack
dump upon startup. Generally all I have to do to "clean" this up is to stop
and restart SQL and it's services, or a reboot. Yesterday I found myself in
this situation again, but the normal "fixes" did not resolve it. This morning
I was searching the net for clues, and still attempting to shutdown and
restart SQL, when SQL finally cooperated and started clean - the app works
fine now.
I have never found anything in the event viewer to give me a hint. The
information in the logs has not provided me with any answers, though I am
pretty inexperiened in that area. I have not been able to find any of the log
contents in MSKB or elsewhere.
I am confident enough to reinstall SQL, to see if any of this is fixed, but
the application's consultant is afraid that the app will break if I do that.
I need to take the time to FIX this rather than band-aiding it when it
breaks. I inherited this last summer, but the issue has been occurring for 2
years, and the server's previous caretaker did not deal with it. The other
hindrance is that our company will be closing this time next year, so the
attitude here is to just keep things running, without any new investment.
Any help with this is much appreciated! Thank-you!!!
Part of the log is listed below:
2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-03-22 08:37:42.80 server All rights reserved.
2005-03-22 08:37:42.80 server Server Process ID is 696.
2005-03-22 08:37:42.80 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
2005-03-22 08:37:42.82 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2005-03-22 08:37:42.92 server SQL Server configured for thread mode
processing.
2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'master'
(1).
2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (1)
2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977,
127.0.0.1:3977.
2005-03-22 08:37:44.88 server SQL Server is ready for client connections
2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
2005-03-22 08:37:45.50 spid2 Recovery complete.
2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL$LASERFICHE\log\SQL00640.dmp
2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
..
..
..
2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
c0000005 caught.
Karen
"There are two documents in your in-box: tragedy and comedy. Your Pick."
--Dale Dauten
Hi
Install sp3a for SQL Server 2000. You have no Service Pack on that instance.
Server Version: http://www.aspfaq.com/show.asp?id=2160
Regards
Mike
"Karen" wrote:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> I have a SQL server for a document imaging application. SQL is installed
> along with a named instance that is necessary for the application. I was not
> involved in the installation or setup of this machine, but now the
> responsibility has fallen to me to maintain it.
> The named instance occasionally (once every other month) generates a stack
> dump upon startup. Generally all I have to do to "clean" this up is to stop
> and restart SQL and it's services, or a reboot. Yesterday I found myself in
> this situation again, but the normal "fixes" did not resolve it. This morning
> I was searching the net for clues, and still attempting to shutdown and
> restart SQL, when SQL finally cooperated and started clean - the app works
> fine now.
> I have never found anything in the event viewer to give me a hint. The
> information in the logs has not provided me with any answers, though I am
> pretty inexperiened in that area. I have not been able to find any of the log
> contents in MSKB or elsewhere.
> I am confident enough to reinstall SQL, to see if any of this is fixed, but
> the application's consultant is afraid that the app will break if I do that.
> I need to take the time to FIX this rather than band-aiding it when it
> breaks. I inherited this last summer, but the issue has been occurring for 2
> years, and the server's previous caretaker did not deal with it. The other
> hindrance is that our company will be closing this time next year, so the
> attitude here is to just keep things running, without any new investment.
> Any help with this is much appreciated! Thank-you!!!
> Part of the log is listed below:
> --
> 2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
> X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporation.
> 2005-03-22 08:37:42.80 server All rights reserved.
> 2005-03-22 08:37:42.80 server Server Process ID is 696.
> 2005-03-22 08:37:42.80 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
> 2005-03-22 08:37:42.82 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2005-03-22 08:37:42.92 server SQL Server configured for thread mode
> processing.
> 2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
> 2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'master'
> (1).
> 2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (1)
> 2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
> 2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
> 2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
> 2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
> 2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
> 2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977,
> 127.0.0.1:3977.
> 2005-03-22 08:37:44.88 server SQL Server is ready for client connections
> 2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
> 2005-03-22 08:37:45.50 spid2 Recovery complete.
> 2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
> Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL$LASERFICHE\log\SQL00640.dmp
> 2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
> fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> .
> .
> .
> 2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
> c0000005 caught.
> Karen
> "There are two documents in your in-box: tragedy and comedy. Your Pick."
> --Dale Dauten
|||Thanks, Mike, but I have never been able to get sp3a applied to the instance.
It has been a few months since the last time I tried, so I do not have the
error available, and it will be a few days until I can try again.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Install sp3a for SQL Server 2000. You have no Service Pack on that instance.
> Server Version: http://www.aspfaq.com/show.asp?id=2160
> Regards
> Mike
|||Hi
The fact that sp3a will not install indicates that there is something wrong
with the machine or installation. So getting stack dumps is not unexpected.
Regards
Mike
"Karen" wrote:
> Thanks, Mike, but I have never been able to get sp3a applied to the instance.
> It has been a few months since the last time I tried, so I do not have the
> error available, and it will be a few days until I can try again.
> "Mike Epprecht (SQL MVP)" wrote:
>
|||Hi Mike,
It certainly does.
I have discovered that the named instance really isn't a named instance, it
is MSDE, so it is understandable that the sp's did not install. It would have
been nice if the SP install would have given a message to the fact that it
was the wrong version, but that would have been too easy!
I will install the correct sp this week & perhaps there will no longer be
any problems.
Thanks,
Karen
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The fact that sp3a will not install indicates that there is something wrong
> with the machine or installation. So getting stack dumps is not unexpected.
> Regards
> Mike
> "Karen" wrote:
Named Instance stack dump upon startup
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
I have a SQL server for a document imaging application. SQL is installed
along with a named instance that is necessary for the application. I was not
involved in the installation or setup of this machine, but now the
responsibility has fallen to me to maintain it.
The named instance occasionally (once every other month) generates a stack
dump upon startup. Generally all I have to do to "clean" this up is to stop
and restart SQL and it's services, or a reboot. Yesterday I found myself in
this situation again, but the normal "fixes" did not resolve it. This mornin
g
I was searching the net for clues, and still attempting to shutdown and
restart SQL, when SQL finally cooperated and started clean - the app works
fine now.
I have never found anything in the event viewer to give me a hint. The
information in the logs has not provided me with any answers, though I am
pretty inexperiened in that area. I have not been able to find any of the lo
g
contents in MSKB or elsewhere.
I am confident enough to reinstall SQL, to see if any of this is fixed, but
the application's consultant is afraid that the app will break if I do that.
I need to take the time to FIX this rather than band-aiding it when it
breaks. I inherited this last summer, but the issue has been occurring for 2
years, and the server's previous caretaker did not deal with it. The other
hindrance is that our company will be closing this time next year, so the
attitude here is to just keep things running, without any new investment.
Any help with this is much appreciated! Thank-you!!!
Part of the log is listed below:
--
2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-03-22 08:37:42.80 server All rights reserved.
2005-03-22 08:37:42.80 server Server Process ID is 696.
2005-03-22 08:37:42.80 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
2005-03-22 08:37:42.82 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2005-03-22 08:37:42.92 server SQL Server configured for thread mode
processing.
2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'master'
(1).
2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (1)
2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977,
127.0.0.1:3977.
2005-03-22 08:37:44.88 server SQL Server is ready for client connections
2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
2005-03-22 08:37:45.50 spid2 Recovery complete.
2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL$LASERFICHE\log\SQL00640.dmp
2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
.
.
.
2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
c0000005 caught.
Karen
"There are two documents in your in-box: tragedy and comedy. Your Pick."
--Dale DautenHi
Install sp3a for SQL Server 2000. You have no Service Pack on that instance.
Server Version: http://www.aspfaq.com/show.asp?id=2160
Regards
Mike
"Karen" wrote:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> I have a SQL server for a document imaging application. SQL is installed
> along with a named instance that is necessary for the application. I was n
ot
> involved in the installation or setup of this machine, but now the
> responsibility has fallen to me to maintain it.
> The named instance occasionally (once every other month) generates a stack
> dump upon startup. Generally all I have to do to "clean" this up is to sto
p
> and restart SQL and it's services, or a reboot. Yesterday I found myself i
n
> this situation again, but the normal "fixes" did not resolve it. This morn
ing
> I was searching the net for clues, and still attempting to shutdown and
> restart SQL, when SQL finally cooperated and started clean - the app works
> fine now.
> I have never found anything in the event viewer to give me a hint. The
> information in the logs has not provided me with any answers, though I am
> pretty inexperiened in that area. I have not been able to find any of the
log
> contents in MSKB or elsewhere.
> I am confident enough to reinstall SQL, to see if any of this is fixed, bu
t
> the application's consultant is afraid that the app will break if I do tha
t.
> I need to take the time to FIX this rather than band-aiding it when it
> breaks. I inherited this last summer, but the issue has been occurring for
2
> years, and the server's previous caretaker did not deal with it. The other
> hindrance is that our company will be closing this time next year, so the
> attitude here is to just keep things running, without any new investment.
> Any help with this is much appreciated! Thank-you!!!
> Part of the log is listed below:
> --
> 2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
> X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporatio
n.
> 2005-03-22 08:37:42.80 server All rights reserved.
> 2005-03-22 08:37:42.80 server Server Process ID is 696.
> 2005-03-22 08:37:42.80 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
> 2005-03-22 08:37:42.82 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2005-03-22 08:37:42.92 server SQL Server configured for thread mode
> processing.
> 2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Loc
k
> Blocks, [1000] Lock Owner Blocks.
> 2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
> 2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'maste
r'
> (1).
> 2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (
1)
> 2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
> 2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
> 2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
> 2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
> 2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
> 2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977
,
> 127.0.0.1:3977.
> 2005-03-22 08:37:44.88 server SQL Server is ready for client connections
> 2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
> 2005-03-22 08:37:45.50 spid2 Recovery complete.
> 2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
> Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL$LASERFICHE\log\SQL00640.dmp
> 2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
> fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> .
> .
> .
> 2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
> c0000005 caught.
> Karen
> "There are two documents in your in-box: tragedy and comedy. Your Pick."
> --Dale Dauten|||Thanks, Mike, but I have never been able to get sp3a applied to the instance
.
It has been a few months since the last time I tried, so I do not have the
error available, and it will be a few days until I can try again.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Install sp3a for SQL Server 2000. You have no Service Pack on that instanc
e.
> Server Version: http://www.aspfaq.com/show.asp?id=2160
> Regards
> Mike|||Hi
The fact that sp3a will not install indicates that there is something wrong
with the machine or installation. So getting stack dumps is not unexpected.
Regards
Mike
"Karen" wrote:
> Thanks, Mike, but I have never been able to get sp3a applied to the instan
ce.
> It has been a few months since the last time I tried, so I do not have the
> error available, and it will be a few days until I can try again.
> "Mike Epprecht (SQL MVP)" wrote:
>
>|||Hi Mike,
It certainly does.
I have discovered that the named instance really isn't a named instance, it
is MSDE, so it is understandable that the sp's did not install. It would hav
e
been nice if the SP install would have given a message to the fact that it
was the wrong version, but that would have been too easy!
I will install the correct sp this week & perhaps there will no longer be
any problems.
Thanks,
Karen
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The fact that sp3a will not install indicates that there is something wron
g
> with the machine or installation. So getting stack dumps is not unexpected
.
> Regards
> Mike
> "Karen" wrote:
>sql
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
I have a SQL server for a document imaging application. SQL is installed
along with a named instance that is necessary for the application. I was not
involved in the installation or setup of this machine, but now the
responsibility has fallen to me to maintain it.
The named instance occasionally (once every other month) generates a stack
dump upon startup. Generally all I have to do to "clean" this up is to stop
and restart SQL and it's services, or a reboot. Yesterday I found myself in
this situation again, but the normal "fixes" did not resolve it. This mornin
g
I was searching the net for clues, and still attempting to shutdown and
restart SQL, when SQL finally cooperated and started clean - the app works
fine now.
I have never found anything in the event viewer to give me a hint. The
information in the logs has not provided me with any answers, though I am
pretty inexperiened in that area. I have not been able to find any of the lo
g
contents in MSKB or elsewhere.
I am confident enough to reinstall SQL, to see if any of this is fixed, but
the application's consultant is afraid that the app will break if I do that.
I need to take the time to FIX this rather than band-aiding it when it
breaks. I inherited this last summer, but the issue has been occurring for 2
years, and the server's previous caretaker did not deal with it. The other
hindrance is that our company will be closing this time next year, so the
attitude here is to just keep things running, without any new investment.
Any help with this is much appreciated! Thank-you!!!
Part of the log is listed below:
--
2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-03-22 08:37:42.80 server All rights reserved.
2005-03-22 08:37:42.80 server Server Process ID is 696.
2005-03-22 08:37:42.80 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
2005-03-22 08:37:42.82 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2005-03-22 08:37:42.92 server SQL Server configured for thread mode
processing.
2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'master'
(1).
2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (1)
2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977,
127.0.0.1:3977.
2005-03-22 08:37:44.88 server SQL Server is ready for client connections
2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
2005-03-22 08:37:45.50 spid2 Recovery complete.
2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL$LASERFICHE\log\SQL00640.dmp
2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
.
.
.
2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
c0000005 caught.
Karen
"There are two documents in your in-box: tragedy and comedy. Your Pick."
--Dale DautenHi
Install sp3a for SQL Server 2000. You have no Service Pack on that instance.
Server Version: http://www.aspfaq.com/show.asp?id=2160
Regards
Mike
"Karen" wrote:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> I have a SQL server for a document imaging application. SQL is installed
> along with a named instance that is necessary for the application. I was n
ot
> involved in the installation or setup of this machine, but now the
> responsibility has fallen to me to maintain it.
> The named instance occasionally (once every other month) generates a stack
> dump upon startup. Generally all I have to do to "clean" this up is to sto
p
> and restart SQL and it's services, or a reboot. Yesterday I found myself i
n
> this situation again, but the normal "fixes" did not resolve it. This morn
ing
> I was searching the net for clues, and still attempting to shutdown and
> restart SQL, when SQL finally cooperated and started clean - the app works
> fine now.
> I have never found anything in the event viewer to give me a hint. The
> information in the logs has not provided me with any answers, though I am
> pretty inexperiened in that area. I have not been able to find any of the
log
> contents in MSKB or elsewhere.
> I am confident enough to reinstall SQL, to see if any of this is fixed, bu
t
> the application's consultant is afraid that the app will break if I do tha
t.
> I need to take the time to FIX this rather than band-aiding it when it
> breaks. I inherited this last summer, but the issue has been occurring for
2
> years, and the server's previous caretaker did not deal with it. The other
> hindrance is that our company will be closing this time next year, so the
> attitude here is to just keep things running, without any new investment.
> Any help with this is much appreciated! Thank-you!!!
> Part of the log is listed below:
> --
> 2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
> X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporatio
n.
> 2005-03-22 08:37:42.80 server All rights reserved.
> 2005-03-22 08:37:42.80 server Server Process ID is 696.
> 2005-03-22 08:37:42.80 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
> 2005-03-22 08:37:42.82 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2005-03-22 08:37:42.92 server SQL Server configured for thread mode
> processing.
> 2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Loc
k
> Blocks, [1000] Lock Owner Blocks.
> 2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
> 2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'maste
r'
> (1).
> 2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (
1)
> 2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
> 2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
> 2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
> 2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
> 2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
> 2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977
,
> 127.0.0.1:3977.
> 2005-03-22 08:37:44.88 server SQL Server is ready for client connections
> 2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
> 2005-03-22 08:37:45.50 spid2 Recovery complete.
> 2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
> Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL$LASERFICHE\log\SQL00640.dmp
> 2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
> fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> .
> .
> .
> 2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
> c0000005 caught.
> Karen
> "There are two documents in your in-box: tragedy and comedy. Your Pick."
> --Dale Dauten|||Thanks, Mike, but I have never been able to get sp3a applied to the instance
.
It has been a few months since the last time I tried, so I do not have the
error available, and it will be a few days until I can try again.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Install sp3a for SQL Server 2000. You have no Service Pack on that instanc
e.
> Server Version: http://www.aspfaq.com/show.asp?id=2160
> Regards
> Mike|||Hi
The fact that sp3a will not install indicates that there is something wrong
with the machine or installation. So getting stack dumps is not unexpected.
Regards
Mike
"Karen" wrote:
> Thanks, Mike, but I have never been able to get sp3a applied to the instan
ce.
> It has been a few months since the last time I tried, so I do not have the
> error available, and it will be a few days until I can try again.
> "Mike Epprecht (SQL MVP)" wrote:
>
>|||Hi Mike,
It certainly does.
I have discovered that the named instance really isn't a named instance, it
is MSDE, so it is understandable that the sp's did not install. It would hav
e
been nice if the SP install would have given a message to the fact that it
was the wrong version, but that would have been too easy!
I will install the correct sp this week & perhaps there will no longer be
any problems.
Thanks,
Karen
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The fact that sp3a will not install indicates that there is something wron
g
> with the machine or installation. So getting stack dumps is not unexpected
.
> Regards
> Mike
> "Karen" wrote:
>sql
Named Instance SQL 7 / SQL 2K
We have a server by name TEST and SQL 7 installed and exists a login 'xx'
and password 'xx'
Recently we installed a named instance SQL 2K on TEST by name TEST\TEST2K
and with a login 'xx' and password 'abc'
I created an alias for TEST\TEST2K as TEST2K
From TEST, Executed sp_addlinkedserver TEST2K
When I try executing from TEST , logged in as 'xx' and password 'xx'
SELECT * FROM TEST2K.MYDB.DBO.MYTABLE
error message
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'xx'.
Is this because of the password difference for 'xx' in TEST and TEST2K '
How to handle this '
Thanks
ShamimSee if this helps...
exec sp_addlinkedserver 'TEST2K','','SQLOLEDB','TEST\TEST2K'
exec sp_addlinkedsrvlogin 'TEST2K','false',null,'xx','abc'
--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
"Shamim" <shamim.abdul@.railamerica.com> wrote in message
news:OV0C$P%23eDHA.1828@.TK2MSFTNGP10.phx.gbl...
> We have a server by name TEST and SQL 7 installed and exists a login 'xx'
> and password 'xx'
> Recently we installed a named instance SQL 2K on TEST by name TEST\TEST2K
> and with a login 'xx' and password 'abc'
> I created an alias for TEST\TEST2K as TEST2K
> From TEST, Executed sp_addlinkedserver TEST2K
> When I try executing from TEST , logged in as 'xx' and password 'xx'
> SELECT * FROM TEST2K.MYDB.DBO.MYTABLE
> error message
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'xx'.
> Is this because of the password difference for 'xx' in TEST and TEST2K '
> How to handle this '
> Thanks
> Shamim
>|||Thanks oj..It worked !!!! much appreciated.
Shamim
"oj" <nospam_ojngo@.home.com> wrote in message
news:e$v$do$eDHA.2748@.TK2MSFTNGP11.phx.gbl...
> See if this helps...
> exec sp_addlinkedserver 'TEST2K','','SQLOLEDB','TEST\TEST2K'
> exec sp_addlinkedsrvlogin 'TEST2K','false',null,'xx','abc'
> --
> -oj
> RAC v2.2 & QALite!
> http://www.rac4sql.net
>
> "Shamim" <shamim.abdul@.railamerica.com> wrote in message
> news:OV0C$P%23eDHA.1828@.TK2MSFTNGP10.phx.gbl...
> > We have a server by name TEST and SQL 7 installed and exists a login
'xx'
> > and password 'xx'
> > Recently we installed a named instance SQL 2K on TEST by name
TEST\TEST2K
> > and with a login 'xx' and password 'abc'
> >
> > I created an alias for TEST\TEST2K as TEST2K
> > From TEST, Executed sp_addlinkedserver TEST2K
> >
> > When I try executing from TEST , logged in as 'xx' and password 'xx'
> >
> > SELECT * FROM TEST2K.MYDB.DBO.MYTABLE
> >
> > error message
> > Server: Msg 18456, Level 14, State 1, Line 1
> > Login failed for user 'xx'.
> >
> > Is this because of the password difference for 'xx' in TEST and TEST2K
'
> >
> > How to handle this '
> >
> > Thanks
> > Shamim
> >
> >
>
and password 'xx'
Recently we installed a named instance SQL 2K on TEST by name TEST\TEST2K
and with a login 'xx' and password 'abc'
I created an alias for TEST\TEST2K as TEST2K
From TEST, Executed sp_addlinkedserver TEST2K
When I try executing from TEST , logged in as 'xx' and password 'xx'
SELECT * FROM TEST2K.MYDB.DBO.MYTABLE
error message
Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'xx'.
Is this because of the password difference for 'xx' in TEST and TEST2K '
How to handle this '
Thanks
ShamimSee if this helps...
exec sp_addlinkedserver 'TEST2K','','SQLOLEDB','TEST\TEST2K'
exec sp_addlinkedsrvlogin 'TEST2K','false',null,'xx','abc'
--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
"Shamim" <shamim.abdul@.railamerica.com> wrote in message
news:OV0C$P%23eDHA.1828@.TK2MSFTNGP10.phx.gbl...
> We have a server by name TEST and SQL 7 installed and exists a login 'xx'
> and password 'xx'
> Recently we installed a named instance SQL 2K on TEST by name TEST\TEST2K
> and with a login 'xx' and password 'abc'
> I created an alias for TEST\TEST2K as TEST2K
> From TEST, Executed sp_addlinkedserver TEST2K
> When I try executing from TEST , logged in as 'xx' and password 'xx'
> SELECT * FROM TEST2K.MYDB.DBO.MYTABLE
> error message
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'xx'.
> Is this because of the password difference for 'xx' in TEST and TEST2K '
> How to handle this '
> Thanks
> Shamim
>|||Thanks oj..It worked !!!! much appreciated.
Shamim
"oj" <nospam_ojngo@.home.com> wrote in message
news:e$v$do$eDHA.2748@.TK2MSFTNGP11.phx.gbl...
> See if this helps...
> exec sp_addlinkedserver 'TEST2K','','SQLOLEDB','TEST\TEST2K'
> exec sp_addlinkedsrvlogin 'TEST2K','false',null,'xx','abc'
> --
> -oj
> RAC v2.2 & QALite!
> http://www.rac4sql.net
>
> "Shamim" <shamim.abdul@.railamerica.com> wrote in message
> news:OV0C$P%23eDHA.1828@.TK2MSFTNGP10.phx.gbl...
> > We have a server by name TEST and SQL 7 installed and exists a login
'xx'
> > and password 'xx'
> > Recently we installed a named instance SQL 2K on TEST by name
TEST\TEST2K
> > and with a login 'xx' and password 'abc'
> >
> > I created an alias for TEST\TEST2K as TEST2K
> > From TEST, Executed sp_addlinkedserver TEST2K
> >
> > When I try executing from TEST , logged in as 'xx' and password 'xx'
> >
> > SELECT * FROM TEST2K.MYDB.DBO.MYTABLE
> >
> > error message
> > Server: Msg 18456, Level 14, State 1, Line 1
> > Login failed for user 'xx'.
> >
> > Is this because of the password difference for 'xx' in TEST and TEST2K
'
> >
> > How to handle this '
> >
> > Thanks
> > Shamim
> >
> >
>
named instance rename
is there a way to rename a named instance?
Jason,
For SQL Server 2000, read:
http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
For SQL Server 2005, the server can be renamed, but not the instance. See:
http://msdn2.microsoft.com/en-us/library/ms143799.aspx
RLF
"jason" <jason@.discussions.microsoft.com> wrote in message
news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
> is there a way to rename a named instance?
|||Jason,
I got to the first link through http://support.microsoft.com/kb/260414 which
is "meant to address frequently asked questions encountered during the setup
or after the installation of multiple instances of SQL Server on the same
computer."
However, after a closer reading of the SQL Server 2000 document I don't
believe it is actually telling how to rename the instance name, only the
server name.
RLF
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
> Jason,
> For SQL Server 2000, read:
> http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
> For SQL Server 2005, the server can be renamed, but not the instance. See:
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx
> RLF
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
>
|||thanks for the feedback, i find it odd that MS doesn't let you change the
name of an instance. any thoughts on why that is?
"Russell Fields" wrote:
> Jason,
> I got to the first link through http://support.microsoft.com/kb/260414 which
> is "meant to address frequently asked questions encountered during the setup
> or after the installation of multiple instances of SQL Server on the same
> computer."
> However, after a closer reading of the SQL Server 2000 document I don't
> believe it is actually telling how to rename the instance name, only the
> server name.
> RLF
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
>
>
|||Hello,
Since the named instance will create folders and registry keys based on the
instance name provide during installation, it will
not be easy to change those constant names.
Thanks
Hari
"jason" <jason@.discussions.microsoft.com> wrote in message
news:A198F0BE-0026-4071-ABA6-FD68D5DB5396@.microsoft.com...[vbcol=seagreen]
> thanks for the feedback, i find it odd that MS doesn't let you change the
> name of an instance. any thoughts on why that is?
> "Russell Fields" wrote:
|||Hi, Jason,
I understand that you would like to know how to rename the named instance
of your SQL Server.
If I have misunderstood, please let me know.
For a named instance, SQL Server does not provide a way to rename the
instance name unless you uninstall the instance and then install a new SQL
Server instance; however you can rename the server name.
Please refer to:
Renaming a Server
http://msdn2.microsoft.com/en-us/library/aa197071%28SQL.80%29.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||It is a simple matter to un-install another instance for many reasons and for
the same reason, you cannot easily rename an instance, but you can create a
new instance with the name you want. You are allowed to install 16, if I am
not mistaken.
As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I am
not sure how the SQL Express works), there is a key in the registry
HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds a
great deal of information about your instance and which references many other
registry keys. In the process of uninstalling you run across two barriers,
the first being these registry keys and the second being that the databases,
by default, are read - only and remain that way while they are attached.
Assuming you have attached databases when you uninstall, you cannot remove
the directory they are in because they are read only.
Imagine how you would react if you uninstalled a named instance and it
removed your database(s).
Again, best way to rename is to create a named instance with the name you
desire and then move the databases from the one named instance to the other
(detach and attach).
Regards,
Jamie
"jason" wrote:
> is there a way to rename a named instance?
|||thanks!
"thejamie" wrote:
[vbcol=seagreen]
> It is a simple matter to un-install another instance for many reasons and for
> the same reason, you cannot easily rename an instance, but you can create a
> new instance with the name you want. You are allowed to install 16, if I am
> not mistaken.
> As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I am
> not sure how the SQL Express works), there is a key in the registry
> HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds a
> great deal of information about your instance and which references many other
> registry keys. In the process of uninstalling you run across two barriers,
> the first being these registry keys and the second being that the databases,
> by default, are read - only and remain that way while they are attached.
> Assuming you have attached databases when you uninstall, you cannot remove
> the directory they are in because they are read only.
> Imagine how you would react if you uninstalled a named instance and it
> removed your database(s).
> Again, best way to rename is to create a named instance with the name you
> desire and then move the databases from the one named instance to the other
> (detach and attach).
> --
> Regards,
> Jamie
>
> "jason" wrote:
|||Actually I meant the first line to say it is NOT a simple matter to
uninstall... nevertheless, if you do, then make sure you delete the regkey
for MSSQL$MyInstance (ask which one it is if you are not sure - messing with
the registry is always dangerour) and after you uninstall, then copy the
databases from the old instance folder to your new instance and attach them
to the new instance... probably a good idea to delete the old folder after
you copy the databases just in case you decide to reinstall the old instance
for some reason.
One more thing to remember. The sixteen msi's that are run from the MSDE
installation use different GUID keys and access the instance name and
reference it accordingly. This procedure is followed during an uninstall
also. SP4 improved the uninstall process considerably over the sp3a. It
may be smart enough to do all this without monitoring the registry, but I
check anyway as I had tons of trouble with the sp3a installation. Each GUID
is related back to a particular numbered instance of the msi.
Glad it helped.
Regards,
Jamie
"jason" wrote:
[vbcol=seagreen]
> thanks!
> "thejamie" wrote:
Jason,
For SQL Server 2000, read:
http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
For SQL Server 2005, the server can be renamed, but not the instance. See:
http://msdn2.microsoft.com/en-us/library/ms143799.aspx
RLF
"jason" <jason@.discussions.microsoft.com> wrote in message
news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
> is there a way to rename a named instance?
|||Jason,
I got to the first link through http://support.microsoft.com/kb/260414 which
is "meant to address frequently asked questions encountered during the setup
or after the installation of multiple instances of SQL Server on the same
computer."
However, after a closer reading of the SQL Server 2000 document I don't
believe it is actually telling how to rename the instance name, only the
server name.
RLF
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
> Jason,
> For SQL Server 2000, read:
> http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
> For SQL Server 2005, the server can be renamed, but not the instance. See:
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx
> RLF
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
>
|||thanks for the feedback, i find it odd that MS doesn't let you change the
name of an instance. any thoughts on why that is?
"Russell Fields" wrote:
> Jason,
> I got to the first link through http://support.microsoft.com/kb/260414 which
> is "meant to address frequently asked questions encountered during the setup
> or after the installation of multiple instances of SQL Server on the same
> computer."
> However, after a closer reading of the SQL Server 2000 document I don't
> believe it is actually telling how to rename the instance name, only the
> server name.
> RLF
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
>
>
|||Hello,
Since the named instance will create folders and registry keys based on the
instance name provide during installation, it will
not be easy to change those constant names.
Thanks
Hari
"jason" <jason@.discussions.microsoft.com> wrote in message
news:A198F0BE-0026-4071-ABA6-FD68D5DB5396@.microsoft.com...[vbcol=seagreen]
> thanks for the feedback, i find it odd that MS doesn't let you change the
> name of an instance. any thoughts on why that is?
> "Russell Fields" wrote:
|||Hi, Jason,
I understand that you would like to know how to rename the named instance
of your SQL Server.
If I have misunderstood, please let me know.
For a named instance, SQL Server does not provide a way to rename the
instance name unless you uninstall the instance and then install a new SQL
Server instance; however you can rename the server name.
Please refer to:
Renaming a Server
http://msdn2.microsoft.com/en-us/library/aa197071%28SQL.80%29.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||It is a simple matter to un-install another instance for many reasons and for
the same reason, you cannot easily rename an instance, but you can create a
new instance with the name you want. You are allowed to install 16, if I am
not mistaken.
As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I am
not sure how the SQL Express works), there is a key in the registry
HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds a
great deal of information about your instance and which references many other
registry keys. In the process of uninstalling you run across two barriers,
the first being these registry keys and the second being that the databases,
by default, are read - only and remain that way while they are attached.
Assuming you have attached databases when you uninstall, you cannot remove
the directory they are in because they are read only.
Imagine how you would react if you uninstalled a named instance and it
removed your database(s).
Again, best way to rename is to create a named instance with the name you
desire and then move the databases from the one named instance to the other
(detach and attach).
Regards,
Jamie
"jason" wrote:
> is there a way to rename a named instance?
|||thanks!
"thejamie" wrote:
[vbcol=seagreen]
> It is a simple matter to un-install another instance for many reasons and for
> the same reason, you cannot easily rename an instance, but you can create a
> new instance with the name you want. You are allowed to install 16, if I am
> not mistaken.
> As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I am
> not sure how the SQL Express works), there is a key in the registry
> HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds a
> great deal of information about your instance and which references many other
> registry keys. In the process of uninstalling you run across two barriers,
> the first being these registry keys and the second being that the databases,
> by default, are read - only and remain that way while they are attached.
> Assuming you have attached databases when you uninstall, you cannot remove
> the directory they are in because they are read only.
> Imagine how you would react if you uninstalled a named instance and it
> removed your database(s).
> Again, best way to rename is to create a named instance with the name you
> desire and then move the databases from the one named instance to the other
> (detach and attach).
> --
> Regards,
> Jamie
>
> "jason" wrote:
|||Actually I meant the first line to say it is NOT a simple matter to
uninstall... nevertheless, if you do, then make sure you delete the regkey
for MSSQL$MyInstance (ask which one it is if you are not sure - messing with
the registry is always dangerour) and after you uninstall, then copy the
databases from the old instance folder to your new instance and attach them
to the new instance... probably a good idea to delete the old folder after
you copy the databases just in case you decide to reinstall the old instance
for some reason.
One more thing to remember. The sixteen msi's that are run from the MSDE
installation use different GUID keys and access the instance name and
reference it accordingly. This procedure is followed during an uninstall
also. SP4 improved the uninstall process considerably over the sp3a. It
may be smart enough to do all this without monitoring the registry, but I
check anyway as I had tons of trouble with the sp3a installation. Each GUID
is related back to a particular numbered instance of the msi.
Glad it helped.
Regards,
Jamie
"jason" wrote:
[vbcol=seagreen]
> thanks!
> "thejamie" wrote:
named instance rename
is there a way to rename a named instance?Jason,
For SQL Server 2000, read:
http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
For SQL Server 2005, the server can be renamed, but not the instance. See:
http://msdn2.microsoft.com/en-us/library/ms143799.aspx
RLF
"jason" <jason@.discussions.microsoft.com> wrote in message
news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
> is there a way to rename a named instance?|||Jason,
I got to the first link through http://support.microsoft.com/kb/260414 which
is "meant to address frequently asked questions encountered during the setup
or after the installation of multiple instances of SQL Server on the same
computer."
However, after a closer reading of the SQL Server 2000 document I don't
believe it is actually telling how to rename the instance name, only the
server name.
RLF
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
> Jason,
> For SQL Server 2000, read:
> http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
> For SQL Server 2005, the server can be renamed, but not the instance. See:
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx
> RLF
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
>|||thanks for the feedback, i find it odd that MS doesn't let you change the
name of an instance. any thoughts on why that is?
"Russell Fields" wrote:
> Jason,
> I got to the first link through http://support.microsoft.com/kb/260414 whi
ch
> is "meant to address frequently asked questions encountered during the set
up
> or after the installation of multiple instances of SQL Server on the same
> computer."
> However, after a closer reading of the SQL Server 2000 document I don't
> believe it is actually telling how to rename the instance name, only the
> server name.
> RLF
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
>
>|||Hello,
Since the named instance will create folders and registry keys based on the
instance name provide during installation, it will
not be easy to change those constant names.
Thanks
Hari
"jason" <jason@.discussions.microsoft.com> wrote in message
news:A198F0BE-0026-4071-ABA6-FD68D5DB5396@.microsoft.com...[vbcol=seagreen]
> thanks for the feedback, i find it odd that MS doesn't let you change the
> name of an instance. any thoughts on why that is?
> "Russell Fields" wrote:
>|||Hi, Jason,
I understand that you would like to know how to rename the named instance
of your SQL Server.
If I have misunderstood, please let me know.
For a named instance, SQL Server does not provide a way to rename the
instance name unless you uninstall the instance and then install a new SQL
Server instance; however you can rename the server name.
Please refer to:
Renaming a Server
http://msdn2.microsoft.com/en-us/li...8SQL.80%29.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||It is a simple matter to un-install another instance for many reasons and fo
r
the same reason, you cannot easily rename an instance, but you can create a
new instance with the name you want. You are allowed to install 16, if I am
not mistaken.
As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I am
not sure how the SQL Express works), there is a key in the registry
HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds a
great deal of information about your instance and which references many othe
r
registry keys. In the process of uninstalling you run across two barriers,
the first being these registry keys and the second being that the databases,
by default, are read - only and remain that way while they are attached.
Assuming you have attached databases when you uninstall, you cannot remove
the directory they are in because they are read only.
Imagine how you would react if you uninstalled a named instance and it
removed your database(s).
Again, best way to rename is to create a named instance with the name you
desire and then move the databases from the one named instance to the other
(detach and attach).
--
Regards,
Jamie
"jason" wrote:
> is there a way to rename a named instance?|||thanks!
"thejamie" wrote:
[vbcol=seagreen]
> It is a simple matter to un-install another instance for many reasons and
for
> the same reason, you cannot easily rename an instance, but you can create
a
> new instance with the name you want. You are allowed to install 16, if I
am
> not mistaken.
> As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I a
m
> not sure how the SQL Express works), there is a key in the registry
> HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds
a
> great deal of information about your instance and which references many ot
her
> registry keys. In the process of uninstalling you run across two barrier
s,
> the first being these registry keys and the second being that the database
s,
> by default, are read - only and remain that way while they are attached.
> Assuming you have attached databases when you uninstall, you cannot remove
> the directory they are in because they are read only.
> Imagine how you would react if you uninstalled a named instance and it
> removed your database(s).
> Again, best way to rename is to create a named instance with the name you
> desire and then move the databases from the one named instance to the othe
r
> (detach and attach).
> --
> Regards,
> Jamie
>
> "jason" wrote:
>|||Actually I meant the first line to say it is NOT a simple matter to
uninstall... nevertheless, if you do, then make sure you delete the regkey
for MSSQL$MyInstance (ask which one it is if you are not sure - messing with
the registry is always dangerour) and after you uninstall, then copy the
databases from the old instance folder to your new instance and attach them
to the new instance... probably a good idea to delete the old folder after
you copy the databases just in case you decide to reinstall the old instance
for some reason.
One more thing to remember. The sixteen msi's that are run from the MSDE
installation use different GUID keys and access the instance name and
reference it accordingly. This procedure is followed during an uninstall
also. SP4 improved the uninstall process considerably over the sp3a. It
may be smart enough to do all this without monitoring the registry, but I
check anyway as I had tons of trouble with the sp3a installation. Each GUID
is related back to a particular numbered instance of the msi.
Glad it helped.
--
Regards,
Jamie
"jason" wrote:
[vbcol=seagreen]
> thanks!
> "thejamie" wrote:
>
For SQL Server 2000, read:
http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
For SQL Server 2005, the server can be renamed, but not the instance. See:
http://msdn2.microsoft.com/en-us/library/ms143799.aspx
RLF
"jason" <jason@.discussions.microsoft.com> wrote in message
news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
> is there a way to rename a named instance?|||Jason,
I got to the first link through http://support.microsoft.com/kb/260414 which
is "meant to address frequently asked questions encountered during the setup
or after the installation of multiple instances of SQL Server on the same
computer."
However, after a closer reading of the SQL Server 2000 document I don't
believe it is actually telling how to rename the instance name, only the
server name.
RLF
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
> Jason,
> For SQL Server 2000, read:
> http://msdn2.microsoft.com/en-us/library/aa197071(SQL.80).aspx
> For SQL Server 2005, the server can be renamed, but not the instance. See:
> http://msdn2.microsoft.com/en-us/library/ms143799.aspx
> RLF
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:9E08D712-1072-4209-B83C-8076623FCD07@.microsoft.com...
>|||thanks for the feedback, i find it odd that MS doesn't let you change the
name of an instance. any thoughts on why that is?
"Russell Fields" wrote:
> Jason,
> I got to the first link through http://support.microsoft.com/kb/260414 whi
ch
> is "meant to address frequently asked questions encountered during the set
up
> or after the installation of multiple instances of SQL Server on the same
> computer."
> However, after a closer reading of the SQL Server 2000 document I don't
> believe it is actually telling how to rename the instance name, only the
> server name.
> RLF
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:OGUopdOZHHA.3628@.TK2MSFTNGP02.phx.gbl...
>
>|||Hello,
Since the named instance will create folders and registry keys based on the
instance name provide during installation, it will
not be easy to change those constant names.
Thanks
Hari
"jason" <jason@.discussions.microsoft.com> wrote in message
news:A198F0BE-0026-4071-ABA6-FD68D5DB5396@.microsoft.com...[vbcol=seagreen]
> thanks for the feedback, i find it odd that MS doesn't let you change the
> name of an instance. any thoughts on why that is?
> "Russell Fields" wrote:
>|||Hi, Jason,
I understand that you would like to know how to rename the named instance
of your SQL Server.
If I have misunderstood, please let me know.
For a named instance, SQL Server does not provide a way to rename the
instance name unless you uninstall the instance and then install a new SQL
Server instance; however you can rename the server name.
Please refer to:
Renaming a Server
http://msdn2.microsoft.com/en-us/li...8SQL.80%29.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||It is a simple matter to un-install another instance for many reasons and fo
r
the same reason, you cannot easily rename an instance, but you can create a
new instance with the name you want. You are allowed to install 16, if I am
not mistaken.
As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I am
not sure how the SQL Express works), there is a key in the registry
HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds a
great deal of information about your instance and which references many othe
r
registry keys. In the process of uninstalling you run across two barriers,
the first being these registry keys and the second being that the databases,
by default, are read - only and remain that way while they are attached.
Assuming you have attached databases when you uninstall, you cannot remove
the directory they are in because they are read only.
Imagine how you would react if you uninstalled a named instance and it
removed your database(s).
Again, best way to rename is to create a named instance with the name you
desire and then move the databases from the one named instance to the other
(detach and attach).
--
Regards,
Jamie
"jason" wrote:
> is there a way to rename a named instance?|||thanks!
"thejamie" wrote:
[vbcol=seagreen]
> It is a simple matter to un-install another instance for many reasons and
for
> the same reason, you cannot easily rename an instance, but you can create
a
> new instance with the name you want. You are allowed to install 16, if I
am
> not mistaken.
> As far as renaming goes, keep in mind that if you uninstall MSDE 2000 (I a
m
> not sure how the SQL Express works), there is a key in the registry
> HKLM/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL$MyInstance which holds
a
> great deal of information about your instance and which references many ot
her
> registry keys. In the process of uninstalling you run across two barrier
s,
> the first being these registry keys and the second being that the database
s,
> by default, are read - only and remain that way while they are attached.
> Assuming you have attached databases when you uninstall, you cannot remove
> the directory they are in because they are read only.
> Imagine how you would react if you uninstalled a named instance and it
> removed your database(s).
> Again, best way to rename is to create a named instance with the name you
> desire and then move the databases from the one named instance to the othe
r
> (detach and attach).
> --
> Regards,
> Jamie
>
> "jason" wrote:
>|||Actually I meant the first line to say it is NOT a simple matter to
uninstall... nevertheless, if you do, then make sure you delete the regkey
for MSSQL$MyInstance (ask which one it is if you are not sure - messing with
the registry is always dangerour) and after you uninstall, then copy the
databases from the old instance folder to your new instance and attach them
to the new instance... probably a good idea to delete the old folder after
you copy the databases just in case you decide to reinstall the old instance
for some reason.
One more thing to remember. The sixteen msi's that are run from the MSDE
installation use different GUID keys and access the instance name and
reference it accordingly. This procedure is followed during an uninstall
also. SP4 improved the uninstall process considerably over the sp3a. It
may be smart enough to do all this without monitoring the registry, but I
check anyway as I had tons of trouble with the sp3a installation. Each GUID
is related back to a particular numbered instance of the msi.
Glad it helped.
--
Regards,
Jamie
"jason" wrote:
[vbcol=seagreen]
> thanks!
> "thejamie" wrote:
>
Subscribe to:
Posts (Atom)