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 default. Show all posts
Showing posts with label default. 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 vs TCP
How would one go about adjusting the default connection to the SQL Server on the client side, using either Named Pipes or TCP as the default?Look for the Client Network Utility tool in the SQL Server program group. Or start->run CliConfig.exe.|||any way to pull of the defaulting programmatically??|||Yes, but the mechanics vary a lot depending on how you are programming. The easiest/surest way is to use the NETWORK parameter within DSN-Less connection strings (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnodbc/html/odbcsql.asp).
-PatP|||Looks like the ticket, thanks for your assistance...
-PatP|||Looks like the ticket, thanks for your assistance...
Wednesday, March 28, 2012
Named Pipes Disabled in SQL 2005
I see Named Pipes disabled by default in SQL 2005. Is this for any specific reasons?Depends on the SKU of your SQL Server package, NP may or may not disabled. In general, we disable NP to reduce attack surface area. You can turn it on by your own judgement based on your cofiguration and requirement.
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..anything different than default ?
We have always used default instances of SQL Server and wanted to start
considering multiple named instances on one physical host. Anything to watch
out for other than just the name change which goes as
Hostname\NamedInstance1 ?
Thanks
Hassam
Each instance on the server consumes memory , just be aware.
"Hassan" <hassan@.hotmail.com> wrote in message
news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
> We have always used default instances of SQL Server and wanted to start
> considering multiple named instances on one physical host. Anything to
> watch out for other than just the name change which goes as
> Hostname\NamedInstance1 ?
> Thanks
>
|||Hello,
As well as each installed named instance require seperate SQL Server
licenses.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Hassam
> Each instance on the server consumes memory , just be aware.
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>
|||> As well as each installed named instance require seperate SQL Server
> licenses.
I believe licensing varies by both SQL Server version and edition. Separate
licenses are needed in some cases but not others.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uS1F4hjtHHA.4572@.TK2MSFTNGP02.phx.gbl...
> Hello,
> As well as each installed named instance require seperate SQL Server
> licenses.
> Thanks
> Hari
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
>
|||For SQL 2005 you don't need licenses for separate instances. You do
need one license for the machine though.
Dan Guzman wrote:
> I believe licensing varies by both SQL Server version and edition.
> Separate licenses are needed in some cases but not others.
>
|||Is that true ? That would be cool.
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> For SQL 2005 you don't need licenses for separate instances. You do need
> one license for the machine though.
>
> Dan Guzman wrote:
|||Check the readme and licensing info that comes with SQL 2005. I also
checked with our MS rep about it.
Hassan wrote:
> Is that true ? That would be cool.
> "Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
> news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
>
considering multiple named instances on one physical host. Anything to watch
out for other than just the name change which goes as
Hostname\NamedInstance1 ?
Thanks
Hassam
Each instance on the server consumes memory , just be aware.
"Hassan" <hassan@.hotmail.com> wrote in message
news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
> We have always used default instances of SQL Server and wanted to start
> considering multiple named instances on one physical host. Anything to
> watch out for other than just the name change which goes as
> Hostname\NamedInstance1 ?
> Thanks
>
|||Hello,
As well as each installed named instance require seperate SQL Server
licenses.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Hassam
> Each instance on the server consumes memory , just be aware.
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>
|||> As well as each installed named instance require seperate SQL Server
> licenses.
I believe licensing varies by both SQL Server version and edition. Separate
licenses are needed in some cases but not others.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uS1F4hjtHHA.4572@.TK2MSFTNGP02.phx.gbl...
> Hello,
> As well as each installed named instance require seperate SQL Server
> licenses.
> Thanks
> Hari
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
>
|||For SQL 2005 you don't need licenses for separate instances. You do
need one license for the machine though.
Dan Guzman wrote:
> I believe licensing varies by both SQL Server version and edition.
> Separate licenses are needed in some cases but not others.
>
|||Is that true ? That would be cool.
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> For SQL 2005 you don't need licenses for separate instances. You do need
> one license for the machine though.
>
> Dan Guzman wrote:
|||Check the readme and licensing info that comes with SQL 2005. I also
checked with our MS rep about it.
Hassan wrote:
> Is that true ? That would be cool.
> "Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
> news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
>
Named instances..anything different than default ?
We have always used default instances of SQL Server and wanted to start
considering multiple named instances on one physical host. Anything to watch
out for other than just the name change which goes as
Hostname\NamedInstance1 ?
ThanksHassam
Each instance on the server consumes memory , just be aware.
"Hassan" <hassan@.hotmail.com> wrote in message
news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
> We have always used default instances of SQL Server and wanted to start
> considering multiple named instances on one physical host. Anything to
> watch out for other than just the name change which goes as
> Hostname\NamedInstance1 ?
> Thanks
>|||Hello,
As well as each installed named instance require seperate SQL Server
licenses.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Hassam
> Each instance on the server consumes memory , just be aware.
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>> We have always used default instances of SQL Server and wanted to start
>> considering multiple named instances on one physical host. Anything to
>> watch out for other than just the name change which goes as
>> Hostname\NamedInstance1 ?
>> Thanks
>|||> As well as each installed named instance require seperate SQL Server
> licenses.
I believe licensing varies by both SQL Server version and edition. Separate
licenses are needed in some cases but not others.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uS1F4hjtHHA.4572@.TK2MSFTNGP02.phx.gbl...
> Hello,
> As well as each installed named instance require seperate SQL Server
> licenses.
> Thanks
> Hari
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
>> Hassam
>> Each instance on the server consumes memory , just be aware.
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>> We have always used default instances of SQL Server and wanted to start
>> considering multiple named instances on one physical host. Anything to
>> watch out for other than just the name change which goes as
>> Hostname\NamedInstance1 ?
>> Thanks
>>
>|||For SQL 2005 you don't need licenses for separate instances. You do
need one license for the machine though.
Dan Guzman wrote:
>> As well as each installed named instance require seperate SQL Server
>> licenses.
> I believe licensing varies by both SQL Server version and edition.
> Separate licenses are needed in some cases but not others.
>|||Is that true ? That would be cool.
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
> For SQL 2005 you don't need licenses for separate instances. You do need
> one license for the machine though.
>
> Dan Guzman wrote:
>> As well as each installed named instance require seperate SQL Server
>> licenses.
>> I believe licensing varies by both SQL Server version and edition.
>> Separate licenses are needed in some cases but not others.|||Check the readme and licensing info that comes with SQL 2005. I also
checked with our MS rep about it.
Hassan wrote:
> Is that true ? That would be cool.
> "Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
> news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> For SQL 2005 you don't need licenses for separate instances. You do need
>> one license for the machine though.
>>
>> Dan Guzman wrote:
>> As well as each installed named instance require seperate SQL Server
>> licenses.
>> I believe licensing varies by both SQL Server version and edition.
>> Separate licenses are needed in some cases but not others.
>
considering multiple named instances on one physical host. Anything to watch
out for other than just the name change which goes as
Hostname\NamedInstance1 ?
ThanksHassam
Each instance on the server consumes memory , just be aware.
"Hassan" <hassan@.hotmail.com> wrote in message
news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
> We have always used default instances of SQL Server and wanted to start
> considering multiple named instances on one physical host. Anything to
> watch out for other than just the name change which goes as
> Hostname\NamedInstance1 ?
> Thanks
>|||Hello,
As well as each installed named instance require seperate SQL Server
licenses.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Hassam
> Each instance on the server consumes memory , just be aware.
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>> We have always used default instances of SQL Server and wanted to start
>> considering multiple named instances on one physical host. Anything to
>> watch out for other than just the name change which goes as
>> Hostname\NamedInstance1 ?
>> Thanks
>|||> As well as each installed named instance require seperate SQL Server
> licenses.
I believe licensing varies by both SQL Server version and edition. Separate
licenses are needed in some cases but not others.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uS1F4hjtHHA.4572@.TK2MSFTNGP02.phx.gbl...
> Hello,
> As well as each installed named instance require seperate SQL Server
> licenses.
> Thanks
> Hari
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
>> Hassam
>> Each instance on the server consumes memory , just be aware.
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>> We have always used default instances of SQL Server and wanted to start
>> considering multiple named instances on one physical host. Anything to
>> watch out for other than just the name change which goes as
>> Hostname\NamedInstance1 ?
>> Thanks
>>
>|||For SQL 2005 you don't need licenses for separate instances. You do
need one license for the machine though.
Dan Guzman wrote:
>> As well as each installed named instance require seperate SQL Server
>> licenses.
> I believe licensing varies by both SQL Server version and edition.
> Separate licenses are needed in some cases but not others.
>|||Is that true ? That would be cool.
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
> For SQL 2005 you don't need licenses for separate instances. You do need
> one license for the machine though.
>
> Dan Guzman wrote:
>> As well as each installed named instance require seperate SQL Server
>> licenses.
>> I believe licensing varies by both SQL Server version and edition.
>> Separate licenses are needed in some cases but not others.|||Check the readme and licensing info that comes with SQL 2005. I also
checked with our MS rep about it.
Hassan wrote:
> Is that true ? That would be cool.
> "Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
> news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
>> For SQL 2005 you don't need licenses for separate instances. You do need
>> one license for the machine though.
>>
>> Dan Guzman wrote:
>> As well as each installed named instance require seperate SQL Server
>> licenses.
>> I believe licensing varies by both SQL Server version and edition.
>> Separate licenses are needed in some cases but not others.
>
Named instances..anything different than default ?
We have always used default instances of SQL Server and wanted to start
considering multiple named instances on one physical host. Anything to watch
out for other than just the name change which goes as
Hostname\NamedInstance1 ?
ThanksHassam
Each instance on the server consumes memory , just be aware.
"Hassan" <hassan@.hotmail.com> wrote in message
news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
> We have always used default instances of SQL Server and wanted to start
> considering multiple named instances on one physical host. Anything to
> watch out for other than just the name change which goes as
> Hostname\NamedInstance1 ?
> Thanks
>|||Hello,
As well as each installed named instance require seperate SQL Server
licenses.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Hassam
> Each instance on the server consumes memory , just be aware.
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>|||> As well as each installed named instance require seperate SQL Server
> licenses.
I believe licensing varies by both SQL Server version and edition. Separate
licenses are needed in some cases but not others.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uS1F4hjtHHA.4572@.TK2MSFTNGP02.phx.gbl...
> Hello,
> As well as each installed named instance require seperate SQL Server
> licenses.
> Thanks
> Hari
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
>|||For SQL 2005 you don't need licenses for separate instances. You do
need one license for the machine though.
Dan Guzman wrote:
> I believe licensing varies by both SQL Server version and edition.
> Separate licenses are needed in some cases but not others.
>|||Is that true ? That would be cool.
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> For SQL 2005 you don't need licenses for separate instances. You do need
> one license for the machine though.
>
> Dan Guzman wrote:|||Check the readme and licensing info that comes with SQL 2005. I also
checked with our MS rep about it.
Hassan wrote:
> Is that true ? That would be cool.
> "Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
> news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
>sql
considering multiple named instances on one physical host. Anything to watch
out for other than just the name change which goes as
Hostname\NamedInstance1 ?
ThanksHassam
Each instance on the server consumes memory , just be aware.
"Hassan" <hassan@.hotmail.com> wrote in message
news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
> We have always used default instances of SQL Server and wanted to start
> considering multiple named instances on one physical host. Anything to
> watch out for other than just the name change which goes as
> Hostname\NamedInstance1 ?
> Thanks
>|||Hello,
As well as each installed named instance require seperate SQL Server
licenses.
Thanks
Hari
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Hassam
> Each instance on the server consumes memory , just be aware.
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:u1rPioitHHA.4688@.TK2MSFTNGP05.phx.gbl...
>|||> As well as each installed named instance require seperate SQL Server
> licenses.
I believe licensing varies by both SQL Server version and edition. Separate
licenses are needed in some cases but not others.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uS1F4hjtHHA.4572@.TK2MSFTNGP02.phx.gbl...
> Hello,
> As well as each installed named instance require seperate SQL Server
> licenses.
> Thanks
> Hari
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u2sfZ8itHHA.1212@.TK2MSFTNGP05.phx.gbl...
>|||For SQL 2005 you don't need licenses for separate instances. You do
need one license for the machine though.
Dan Guzman wrote:
> I believe licensing varies by both SQL Server version and edition.
> Separate licenses are needed in some cases but not others.
>|||Is that true ? That would be cool.
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> For SQL 2005 you don't need licenses for separate instances. You do need
> one license for the machine though.
>
> Dan Guzman wrote:|||Check the readme and licensing info that comes with SQL 2005. I also
checked with our MS rep about it.
Hassan wrote:
> Is that true ? That would be cool.
> "Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
> news:O7EZ59ntHHA.1728@.TK2MSFTNGP06.phx.gbl...
>sql
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 question
Can instance names be aliased back to the the default instance? ie can
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>
Named instance question
Can instance names be aliased back to the the default instance? ie can
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>
Named instance question
Can instance names be aliased back to the the default instance? ie can
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?
Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>
server/instancename resolve back to servername/? We are looking to migrate
over from using a named instance, to a default instance, but don't want to
have to go change all of the connection strings in many applications, to
that have named instances attached.
If so, can someone point me in the direction to do so?
Only from the clients connecting to it. You can install MDAC 2.6 or later
and use the alias.
"Gary" <clgary@.yahoo.com> wrote in message
news:#j9tS57uEHA.1404@.TK2MSFTNGP11.phx.gbl...
> Can instance names be aliased back to the the default instance? ie can
> server/instancename resolve back to servername/? We are looking to migrate
> over from using a named instance, to a default instance, but don't want to
> have to go change all of the connection strings in many applications, to
> that have named instances attached.
> If so, can someone point me in the direction to do so?
>
Named Instance On Cluster.
I am running a default instance on my Active\Passive cluster and want to
install a named instance on the same cluster. How is that done?
Hi
Search for "How to create a new failover cluster " in SQL Server 2000 BOL.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Shawn" <sscamner@.bellsouth.net> wrote in message
news:uBx4fGUbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>I am running a default instance on my Active\Passive cluster and want to
>install a named instance on the same cluster. How is that done?
>
|||The problem is, I have a default instance running and when I run SQL
install, The Named Instance option is not available.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:etyZXKUbFHA.2736@.TK2MSFTNGP12.phx.gbl...
> Hi
> Search for "How to create a new failover cluster " in SQL Server 2000 BOL.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Shawn" <sscamner@.bellsouth.net> wrote in message
> news:uBx4fGUbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>
|||You'll have to specify a new virtual server name and then specify an
instance for it.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Shawn" <sscamner@.bellsouth.net> wrote in message
news:eqVHDWUbFHA.3184@.TK2MSFTNGP15.phx.gbl...
The problem is, I have a default instance running and when I run SQL
install, The Named Instance option is not available.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:etyZXKUbFHA.2736@.TK2MSFTNGP12.phx.gbl...
> Hi
> Search for "How to create a new failover cluster " in SQL Server 2000 BOL.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Shawn" <sscamner@.bellsouth.net> wrote in message
> news:uBx4fGUbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>
|||And a new ip as well?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23WsMY$UbFHA.3864@.TK2MSFTNGP10.phx.gbl...
> You'll have to specify a new virtual server name and then specify an
> instance for it.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "Shawn" <sscamner@.bellsouth.net> wrote in message
> news:eqVHDWUbFHA.3184@.TK2MSFTNGP15.phx.gbl...
> The problem is, I have a default instance running and when I run SQL
> install, The Named Instance option is not available.
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:etyZXKUbFHA.2736@.TK2MSFTNGP12.phx.gbl...
>
|||New IP, New Virtual Server\Instance Name, and all new disks for each SQL
Instance.
Geoff N. Hiten
Microsoft SQL Server MVP
"Shawn" <sscamner@.bellsouth.net> wrote in message
news:ulFCVLVbFHA.2520@.TK2MSFTNGP09.phx.gbl...
> And a new ip as well?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23WsMY$UbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>
install a named instance on the same cluster. How is that done?
Hi
Search for "How to create a new failover cluster " in SQL Server 2000 BOL.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Shawn" <sscamner@.bellsouth.net> wrote in message
news:uBx4fGUbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>I am running a default instance on my Active\Passive cluster and want to
>install a named instance on the same cluster. How is that done?
>
|||The problem is, I have a default instance running and when I run SQL
install, The Named Instance option is not available.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:etyZXKUbFHA.2736@.TK2MSFTNGP12.phx.gbl...
> Hi
> Search for "How to create a new failover cluster " in SQL Server 2000 BOL.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Shawn" <sscamner@.bellsouth.net> wrote in message
> news:uBx4fGUbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>
|||You'll have to specify a new virtual server name and then specify an
instance for it.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Shawn" <sscamner@.bellsouth.net> wrote in message
news:eqVHDWUbFHA.3184@.TK2MSFTNGP15.phx.gbl...
The problem is, I have a default instance running and when I run SQL
install, The Named Instance option is not available.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:etyZXKUbFHA.2736@.TK2MSFTNGP12.phx.gbl...
> Hi
> Search for "How to create a new failover cluster " in SQL Server 2000 BOL.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Shawn" <sscamner@.bellsouth.net> wrote in message
> news:uBx4fGUbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>
|||And a new ip as well?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23WsMY$UbFHA.3864@.TK2MSFTNGP10.phx.gbl...
> You'll have to specify a new virtual server name and then specify an
> instance for it.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "Shawn" <sscamner@.bellsouth.net> wrote in message
> news:eqVHDWUbFHA.3184@.TK2MSFTNGP15.phx.gbl...
> The problem is, I have a default instance running and when I run SQL
> install, The Named Instance option is not available.
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:etyZXKUbFHA.2736@.TK2MSFTNGP12.phx.gbl...
>
|||New IP, New Virtual Server\Instance Name, and all new disks for each SQL
Instance.
Geoff N. Hiten
Microsoft SQL Server MVP
"Shawn" <sscamner@.bellsouth.net> wrote in message
news:ulFCVLVbFHA.2520@.TK2MSFTNGP09.phx.gbl...
> And a new ip as well?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23WsMY$UbFHA.3864@.TK2MSFTNGP10.phx.gbl...
>
Subscribe to:
Posts (Atom)