On a stand alone server, our naming convention for multiple instances is:
server (default instance)
server\IN1 (first named instance)
server\IN2 (second named instance)
etc, etc
Now, on a cluster, I understand the SQL name is made up of
virtualservername\instancename
So say the default instance is installed on the cluster as virtual name =
"server". We would refer to this server as "server"
Say the first named instance is IN1. Am I right in thinking I cannot use the
same virtual server name as the default instance because this name is used in
the cluster group, therefore I cannot have "server\IN1", "server\IN2", etc on
a cluster?
I would have to use something like
server1\IN1
server2\IN2
etc?
"Stu" <Stu@.discussions.microsoft.com> wrote in message
news:B9D979DD-7F4F-4B65-A719-6425881C2121@.microsoft.com...
> On a stand alone server, our naming convention for multiple instances is:
> server (default instance)
> server\IN1 (first named instance)
> server\IN2 (second named instance)
> etc, etc
> Now, on a cluster, I understand the SQL name is made up of
> virtualservername\instancename
> So say the default instance is installed on the cluster as virtual name =
> "server". We would refer to this server as "server"
> Say the first named instance is IN1. Am I right in thinking I cannot use
the
> same virtual server name as the default instance because this name is used
in
> the cluster group, therefore I cannot have "server\IN1", "server\IN2", etc
on
> a cluster?
> I would have to use something like
> server1\IN1
> server2\IN2
correct
Rgds,
Edwin.
Showing posts with label default. Show all posts
Showing posts with label default. Show all posts
Friday, March 30, 2012
Multiple Instances on a cluster
I currently have a 2-node, active/passive cluster running SQL Server
2000 w/SP4, running just the default instance. I am looking to add a
2nd instance, but I have a couple of questions on how to start:
1) I understand that you have to re-run the install and create the 2nd
instance. I've already created a separate resource group and have
available a 2nd dedicated IP, physical disk, virtual server name, etc.
When I do the install, which node should I perform the install on?
2) Once I have the 2nd instance installed, and I create the SQL Server
resource, how do I define which instance this resource controls? I.e.
I thought when I selected SQL Server from the resource list, it would
lise SQL Server and SQL Server\Instance2, but it did not.
If anyone has or knows of any step-by-step documentation on how to
setup a 2nd instance it would be appreciated
Thanks in advance for your help!
Start the install from the node that currently owns the new resource group.
That group should have only the new disk resource in it. SQL will add the
IP address and the network name during the install from information you
supply. The SQL Installer will create a resource group with all the correct
dependencies. I usually rename the resource groups to match the Virtual
Server names so I don't get confused later on.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<sean.frenette@.umassmed.edu> wrote in message
news:1141072994.001225.149140@.p10g2000cwp.googlegr oups.com...
>I currently have a 2-node, active/passive cluster running SQL Server
> 2000 w/SP4, running just the default instance. I am looking to add a
> 2nd instance, but I have a couple of questions on how to start:
> 1) I understand that you have to re-run the install and create the 2nd
> instance. I've already created a separate resource group and have
> available a 2nd dedicated IP, physical disk, virtual server name, etc.
> When I do the install, which node should I perform the install on?
> 2) Once I have the 2nd instance installed, and I create the SQL Server
> resource, how do I define which instance this resource controls? I.e.
> I thought when I selected SQL Server from the resource list, it would
> lise SQL Server and SQL Server\Instance2, but it did not.
> If anyone has or knows of any step-by-step documentation on how to
> setup a 2nd instance it would be appreciated
> Thanks in advance for your help!
>
|||I'm confused.....
what is your goal ?
You want to run multiple server instances on a clustered server in a
production environment ?
If so, why?
(Btw...I dont know the answer to your question, but Hopefully we can get to
a solution one way or another)
Greg Jackson
Pdx, Oregon
|||Yep, we are running 2 instances of SQL on the same cluster. We are
getting ready to implement Tumbleweed secure mail product which
requires it's own instance
sql
2000 w/SP4, running just the default instance. I am looking to add a
2nd instance, but I have a couple of questions on how to start:
1) I understand that you have to re-run the install and create the 2nd
instance. I've already created a separate resource group and have
available a 2nd dedicated IP, physical disk, virtual server name, etc.
When I do the install, which node should I perform the install on?
2) Once I have the 2nd instance installed, and I create the SQL Server
resource, how do I define which instance this resource controls? I.e.
I thought when I selected SQL Server from the resource list, it would
lise SQL Server and SQL Server\Instance2, but it did not.
If anyone has or knows of any step-by-step documentation on how to
setup a 2nd instance it would be appreciated
Thanks in advance for your help!
Start the install from the node that currently owns the new resource group.
That group should have only the new disk resource in it. SQL will add the
IP address and the network name during the install from information you
supply. The SQL Installer will create a resource group with all the correct
dependencies. I usually rename the resource groups to match the Virtual
Server names so I don't get confused later on.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<sean.frenette@.umassmed.edu> wrote in message
news:1141072994.001225.149140@.p10g2000cwp.googlegr oups.com...
>I currently have a 2-node, active/passive cluster running SQL Server
> 2000 w/SP4, running just the default instance. I am looking to add a
> 2nd instance, but I have a couple of questions on how to start:
> 1) I understand that you have to re-run the install and create the 2nd
> instance. I've already created a separate resource group and have
> available a 2nd dedicated IP, physical disk, virtual server name, etc.
> When I do the install, which node should I perform the install on?
> 2) Once I have the 2nd instance installed, and I create the SQL Server
> resource, how do I define which instance this resource controls? I.e.
> I thought when I selected SQL Server from the resource list, it would
> lise SQL Server and SQL Server\Instance2, but it did not.
> If anyone has or knows of any step-by-step documentation on how to
> setup a 2nd instance it would be appreciated
> Thanks in advance for your help!
>
|||I'm confused.....
what is your goal ?
You want to run multiple server instances on a clustered server in a
production environment ?
If so, why?
(Btw...I dont know the answer to your question, but Hopefully we can get to
a solution one way or another)
Greg Jackson
Pdx, Oregon
|||Yep, we are running 2 instances of SQL on the same cluster. We are
getting ready to implement Tumbleweed secure mail product which
requires it's own instance
sql
Wednesday, March 28, 2012
Multiple Instances on a cluster
I currently have a 2-node, active/passive cluster running SQL Server
2000 w/SP4, running just the default instance. I am looking to add a
2nd instance, but I have a couple of questions on how to start:
1) I understand that you have to re-run the install and create the 2nd
instance. I've already created a separate resource group and have
available a 2nd dedicated IP, physical disk, virtual server name, etc.
When I do the install, which node should I perform the install on?
2) Once I have the 2nd instance installed, and I create the SQL Server
resource, how do I define which instance this resource controls? I.e.
I thought when I selected SQL Server from the resource list, it would
lise SQL Server and SQL Server\Instance2, but it did not.
If anyone has or knows of any step-by-step documentation on how to
setup a 2nd instance it would be appreciated
Thanks in advance for your help!Start the install from the node that currently owns the new resource group.
That group should have only the new disk resource in it. SQL will add the
IP address and the network name during the install from information you
supply. The SQL Installer will create a resource group with all the correct
dependencies. I usually rename the resource groups to match the Virtual
Server names so I don't get confused later on.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<sean.frenette@.umassmed.edu> wrote in message
news:1141072994.001225.149140@.p10g2000cwp.googlegroups.com...
>I currently have a 2-node, active/passive cluster running SQL Server
> 2000 w/SP4, running just the default instance. I am looking to add a
> 2nd instance, but I have a couple of questions on how to start:
> 1) I understand that you have to re-run the install and create the 2nd
> instance. I've already created a separate resource group and have
> available a 2nd dedicated IP, physical disk, virtual server name, etc.
> When I do the install, which node should I perform the install on?
> 2) Once I have the 2nd instance installed, and I create the SQL Server
> resource, how do I define which instance this resource controls? I.e.
> I thought when I selected SQL Server from the resource list, it would
> lise SQL Server and SQL Server\Instance2, but it did not.
> If anyone has or knows of any step-by-step documentation on how to
> setup a 2nd instance it would be appreciated
> Thanks in advance for your help!
>|||I'm confused.....
what is your goal ?
You want to run multiple server instances on a clustered server in a
production environment ?
If so, why?
(Btw...I dont know the answer to your question, but Hopefully we can get to
a solution one way or another)
Greg Jackson
Pdx, Oregon|||Yep, we are running 2 instances of SQL on the same cluster. We are
getting ready to implement Tumbleweed secure mail product which
requires it's own instance
2000 w/SP4, running just the default instance. I am looking to add a
2nd instance, but I have a couple of questions on how to start:
1) I understand that you have to re-run the install and create the 2nd
instance. I've already created a separate resource group and have
available a 2nd dedicated IP, physical disk, virtual server name, etc.
When I do the install, which node should I perform the install on?
2) Once I have the 2nd instance installed, and I create the SQL Server
resource, how do I define which instance this resource controls? I.e.
I thought when I selected SQL Server from the resource list, it would
lise SQL Server and SQL Server\Instance2, but it did not.
If anyone has or knows of any step-by-step documentation on how to
setup a 2nd instance it would be appreciated
Thanks in advance for your help!Start the install from the node that currently owns the new resource group.
That group should have only the new disk resource in it. SQL will add the
IP address and the network name during the install from information you
supply. The SQL Installer will create a resource group with all the correct
dependencies. I usually rename the resource groups to match the Virtual
Server names so I don't get confused later on.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<sean.frenette@.umassmed.edu> wrote in message
news:1141072994.001225.149140@.p10g2000cwp.googlegroups.com...
>I currently have a 2-node, active/passive cluster running SQL Server
> 2000 w/SP4, running just the default instance. I am looking to add a
> 2nd instance, but I have a couple of questions on how to start:
> 1) I understand that you have to re-run the install and create the 2nd
> instance. I've already created a separate resource group and have
> available a 2nd dedicated IP, physical disk, virtual server name, etc.
> When I do the install, which node should I perform the install on?
> 2) Once I have the 2nd instance installed, and I create the SQL Server
> resource, how do I define which instance this resource controls? I.e.
> I thought when I selected SQL Server from the resource list, it would
> lise SQL Server and SQL Server\Instance2, but it did not.
> If anyone has or knows of any step-by-step documentation on how to
> setup a 2nd instance it would be appreciated
> Thanks in advance for your help!
>|||I'm confused.....
what is your goal ?
You want to run multiple server instances on a clustered server in a
production environment ?
If so, why?
(Btw...I dont know the answer to your question, but Hopefully we can get to
a solution one way or another)
Greg Jackson
Pdx, Oregon|||Yep, we are running 2 instances of SQL on the same cluster. We are
getting ready to implement Tumbleweed secure mail product which
requires it's own instance
Multiple Instances on a cluster
I currently have a 2-node, active/passive cluster running SQL Server
2000 w/SP4, running just the default instance. I am looking to add a
2nd instance, but I have a couple of questions on how to start:
1) I understand that you have to re-run the install and create the 2nd
instance. I've already created a separate resource group and have
available a 2nd dedicated IP, physical disk, virtual server name, etc.
When I do the install, which node should I perform the install on?
2) Once I have the 2nd instance installed, and I create the SQL Server
resource, how do I define which instance this resource controls? I.e.
I thought when I selected SQL Server from the resource list, it would
lise SQL Server and SQL Server\Instance2, but it did not.
If anyone has or knows of any step-by-step documentation on how to
setup a 2nd instance it would be appreciated
Thanks in advance for your help!Start the install from the node that currently owns the new resource group.
That group should have only the new disk resource in it. SQL will add the
IP address and the network name during the install from information you
supply. The SQL Installer will create a resource group with all the correct
dependencies. I usually rename the resource groups to match the Virtual
Server names so I don't get confused later on.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<sean.frenette@.umassmed.edu> wrote in message
news:1141072994.001225.149140@.p10g2000cwp.googlegroups.com...
>I currently have a 2-node, active/passive cluster running SQL Server
> 2000 w/SP4, running just the default instance. I am looking to add a
> 2nd instance, but I have a couple of questions on how to start:
> 1) I understand that you have to re-run the install and create the 2nd
> instance. I've already created a separate resource group and have
> available a 2nd dedicated IP, physical disk, virtual server name, etc.
> When I do the install, which node should I perform the install on?
> 2) Once I have the 2nd instance installed, and I create the SQL Server
> resource, how do I define which instance this resource controls? I.e.
> I thought when I selected SQL Server from the resource list, it would
> lise SQL Server and SQL Server\Instance2, but it did not.
> If anyone has or knows of any step-by-step documentation on how to
> setup a 2nd instance it would be appreciated
> Thanks in advance for your help!
>|||I'm confused.....
what is your goal ?
You want to run multiple server instances on a clustered server in a
production environment ?
If so, why?
(Btw...I dont know the answer to your question, but Hopefully we can get to
a solution one way or another)
Greg Jackson
Pdx, Oregon|||Yep, we are running 2 instances of SQL on the same cluster. We are
getting ready to implement Tumbleweed secure mail product which
requires it's own instance
2000 w/SP4, running just the default instance. I am looking to add a
2nd instance, but I have a couple of questions on how to start:
1) I understand that you have to re-run the install and create the 2nd
instance. I've already created a separate resource group and have
available a 2nd dedicated IP, physical disk, virtual server name, etc.
When I do the install, which node should I perform the install on?
2) Once I have the 2nd instance installed, and I create the SQL Server
resource, how do I define which instance this resource controls? I.e.
I thought when I selected SQL Server from the resource list, it would
lise SQL Server and SQL Server\Instance2, but it did not.
If anyone has or knows of any step-by-step documentation on how to
setup a 2nd instance it would be appreciated
Thanks in advance for your help!Start the install from the node that currently owns the new resource group.
That group should have only the new disk resource in it. SQL will add the
IP address and the network name during the install from information you
supply. The SQL Installer will create a resource group with all the correct
dependencies. I usually rename the resource groups to match the Virtual
Server names so I don't get confused later on.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<sean.frenette@.umassmed.edu> wrote in message
news:1141072994.001225.149140@.p10g2000cwp.googlegroups.com...
>I currently have a 2-node, active/passive cluster running SQL Server
> 2000 w/SP4, running just the default instance. I am looking to add a
> 2nd instance, but I have a couple of questions on how to start:
> 1) I understand that you have to re-run the install and create the 2nd
> instance. I've already created a separate resource group and have
> available a 2nd dedicated IP, physical disk, virtual server name, etc.
> When I do the install, which node should I perform the install on?
> 2) Once I have the 2nd instance installed, and I create the SQL Server
> resource, how do I define which instance this resource controls? I.e.
> I thought when I selected SQL Server from the resource list, it would
> lise SQL Server and SQL Server\Instance2, but it did not.
> If anyone has or knows of any step-by-step documentation on how to
> setup a 2nd instance it would be appreciated
> Thanks in advance for your help!
>|||I'm confused.....
what is your goal ?
You want to run multiple server instances on a clustered server in a
production environment ?
If so, why?
(Btw...I dont know the answer to your question, but Hopefully we can get to
a solution one way or another)
Greg Jackson
Pdx, Oregon|||Yep, we are running 2 instances of SQL on the same cluster. We are
getting ready to implement Tumbleweed secure mail product which
requires it's own instance
Multiple Instances and Processor
Does anyone know how sql handles processor delegation when you install
multiple instances of sql?
For example:
Default installation will use up to 100% of the processor.
Default installation with 1 named instance will each take 50%.
Default installation with 2 named instances will each take 33.333%
Thanks,
Markeach instance will potentially schedule spids on each processor unless you
use affinity mask within each instance...
once a spid is released to a processor SQL doesn't have any control over
it's excution...
actually... SQL assigns spids to something called a user mode scheduler
which is affinitized to a processor and the UMS hands the spids off...
books like Inside SQL Server 2000 or Ken Henderson's new internals books
have great content on topics like that...
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Mark Newton" <mark.newton@.bdsmarketing.com> wrote in message
news:v11svv82d84m8rvn1vaic6fskbn0jabfo8@.4ax.com...
> Does anyone know how sql handles processor delegation when you install
> multiple instances of sql?
> For example:
> Default installation will use up to 100% of the processor.
> Default installation with 1 named instance will each take 50%.
> Default installation with 2 named instances will each take 33.333%
> Thanks,
> Marksql
multiple instances of sql?
For example:
Default installation will use up to 100% of the processor.
Default installation with 1 named instance will each take 50%.
Default installation with 2 named instances will each take 33.333%
Thanks,
Markeach instance will potentially schedule spids on each processor unless you
use affinity mask within each instance...
once a spid is released to a processor SQL doesn't have any control over
it's excution...
actually... SQL assigns spids to something called a user mode scheduler
which is affinitized to a processor and the UMS hands the spids off...
books like Inside SQL Server 2000 or Ken Henderson's new internals books
have great content on topics like that...
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Mark Newton" <mark.newton@.bdsmarketing.com> wrote in message
news:v11svv82d84m8rvn1vaic6fskbn0jabfo8@.4ax.com...
> Does anyone know how sql handles processor delegation when you install
> multiple instances of sql?
> For example:
> Default installation will use up to 100% of the processor.
> Default installation with 1 named instance will each take 50%.
> Default installation with 2 named instances will each take 33.333%
> Thanks,
> Marksql
Monday, March 26, 2012
Multiple instance name
Hi,
Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance" work
with two or more names?
My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
Thanks,
Max
Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias
for the desired server\instance with whatever server\instance name you like.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance"
> ou make a "named instance" work with two or more names?
> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress"
> named instance and I just have a default instance o SQL Server Developer 2005 (and I would not
> install another instance just for that).
> Thanks,
> Max
>
|||I try it but when I try a connect with the alias name the server I receive: "this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections".
My alias is like that:
Name: mycomputer\SQLExpress
Port: <blank>
Protocol: TCP/IPa
Server: mycomputer
The default SQL Server is running under Network Service account.
Thanks,
Max
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu na mensagem
news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
> Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias for the desired
> server\instance with whatever server\instance name you like.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>
|||As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name resolution. You need to
enable remote connections using the Surface Area Configuration tool. Unlike
SQL 2000, SQL 2005 (all editions) does not allow remote connections
immediately following the installation. This is so you can patch a SQL
Server before exposing it to network connections, should such future
patching be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>I try it but when I try a connect with the alias name the server I receive:
>"this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections".
> My alias is like that:
> Name: mycomputer\SQLExpress
> Port: <blank>
> Protocol: TCP/IPa
> Server: mycomputer
> The default SQL Server is running under Network Service account.
> Thanks,
> Max
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> escreveu na mensagem news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>
|||Yes, I see. Thanks for the tips!
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> escreveu na mensagem news:O5bday9MGHA.1180@.TK2MSFTNGP09.phx.gbl...
> As the message says, the default settings for SQL 2005 do not allow remote connections. This has nothing to do with name
> resolution. You need to enable remote connections using the Surface Area Configuration tool. Unlike SQL 2000, SQL 2005 (all
> editions) does not allow remote connections immediately following the installation. This is so you can patch a SQL Server before
> exposing it to network connections, should such future patching be necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>
sql
Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance" work
with two or more names?
My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
Thanks,
Max
Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias
for the desired server\instance with whatever server\instance name you like.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance"
> ou make a "named instance" work with two or more names?
> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress"
> named instance and I just have a default instance o SQL Server Developer 2005 (and I would not
> install another instance just for that).
> Thanks,
> Max
>
|||I try it but when I try a connect with the alias name the server I receive: "this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections".
My alias is like that:
Name: mycomputer\SQLExpress
Port: <blank>
Protocol: TCP/IPa
Server: mycomputer
The default SQL Server is running under Network Service account.
Thanks,
Max
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu na mensagem
news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
> Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias for the desired
> server\instance with whatever server\instance name you like.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>
|||As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name resolution. You need to
enable remote connections using the Surface Area Configuration tool. Unlike
SQL 2000, SQL 2005 (all editions) does not allow remote connections
immediately following the installation. This is so you can patch a SQL
Server before exposing it to network connections, should such future
patching be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>I try it but when I try a connect with the alias name the server I receive:
>"this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections".
> My alias is like that:
> Name: mycomputer\SQLExpress
> Port: <blank>
> Protocol: TCP/IPa
> Server: mycomputer
> The default SQL Server is running under Network Service account.
> Thanks,
> Max
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> escreveu na mensagem news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>
|||Yes, I see. Thanks for the tips!
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> escreveu na mensagem news:O5bday9MGHA.1180@.TK2MSFTNGP09.phx.gbl...
> As the message says, the default settings for SQL 2005 do not allow remote connections. This has nothing to do with name
> resolution. You need to enable remote connections using the Surface Area Configuration tool. Unlike SQL 2000, SQL 2005 (all
> editions) does not allow remote connections immediately following the installation. This is so you can patch a SQL Server before
> exposing it to network connections, should such future patching be necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>
sql
Multiple instance name
Hi,
Is there a way to make the default instance (SQL 2005) work at the same time
as a "named instance" ou make a "named instance" work
with two or more names?
My problem is that I'm using the QuickStart for VS 2005 and all code work wi
th a "SQLExpress" named instance and I just have a
default instance o SQL Server Developer 2005 (and I would not install anothe
r instance just for that).
Thanks,
MaxYes, but you have to do this on the client. Use the SQL Server Configuration
Manager to add an alias
for the desired server\instance with whatever server\instance name you like.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Is there a way to make the default instance (SQL 2005) work at the same ti
me as a "named instance"
> ou make a "named instance" work with two or more names?
> My problem is that I'm using the QuickStart for VS 2005 and all code work
with a "SQLExpress"
> named instance and I just have a default instance o SQL Server Developer 2
005 (and I would not
> install another instance just for that).
> Thanks,
> Max
>|||I try it but when I try a connect with the alias name the server I receive:
"this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections".
My alias is like that:
Name: mycomputer\SQLExpress
Port: <blank>
Protocol: TCP/IPa
Server: mycomputer
The default SQL Server is running under Network Service account.
Thanks,
Max
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu
na mensagem
news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
> Yes, but you have to do this on the client. Use the SQL Server Configurati
on Manager to add an alias for the desired
> server\instance with whatever server\instance name you like.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:%238KccV
9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>|||As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name resolution. You need to
enable remote connections using the Surface Area Configuration tool. Unlike
SQL 2000, SQL 2005 (all editions) does not allow remote connections
immediately following the installation. This is so you can patch a SQL
Server before exposing it to network connections, should such future
patching be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>I try it but when I try a connect with the alias name the server I receive:
>"this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections".
> My alias is like that:
> Name: mycomputer\SQLExpress
> Port: <blank>
> Protocol: TCP/IPa
> Server: mycomputer
> The default SQL Server is running under Network Service account.
> Thanks,
> Max
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> escreveu na mensagem news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>|||Yes, I see. Thanks for the tips!
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> escreveu na mensagem news:O5bday9MGHA.1180@.TK2MSFT
NGP09.phx.gbl...
> As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name
> resolution. You need to enable remote connections using the Surface Area
Configuration tool. Unlike SQL 2000, SQL 2005 (all
> editions) does not allow remote connections immediately following the inst
allation. This is so you can patch a SQL Server before
> exposing it to network connections, should such future patching be necessa
ry.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:uib%23tp
9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>
Is there a way to make the default instance (SQL 2005) work at the same time
as a "named instance" ou make a "named instance" work
with two or more names?
My problem is that I'm using the QuickStart for VS 2005 and all code work wi
th a "SQLExpress" named instance and I just have a
default instance o SQL Server Developer 2005 (and I would not install anothe
r instance just for that).
Thanks,
MaxYes, but you have to do this on the client. Use the SQL Server Configuration
Manager to add an alias
for the desired server\instance with whatever server\instance name you like.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Is there a way to make the default instance (SQL 2005) work at the same ti
me as a "named instance"
> ou make a "named instance" work with two or more names?
> My problem is that I'm using the QuickStart for VS 2005 and all code work
with a "SQLExpress"
> named instance and I just have a default instance o SQL Server Developer 2
005 (and I would not
> install another instance just for that).
> Thanks,
> Max
>|||I try it but when I try a connect with the alias name the server I receive:
"this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections".
My alias is like that:
Name: mycomputer\SQLExpress
Port: <blank>
Protocol: TCP/IPa
Server: mycomputer
The default SQL Server is running under Network Service account.
Thanks,
Max
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu
na mensagem
news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
> Yes, but you have to do this on the client. Use the SQL Server Configurati
on Manager to add an alias for the desired
> server\instance with whatever server\instance name you like.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:%238KccV
9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>|||As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name resolution. You need to
enable remote connections using the Surface Area Configuration tool. Unlike
SQL 2000, SQL 2005 (all editions) does not allow remote connections
immediately following the installation. This is so you can patch a SQL
Server before exposing it to network connections, should such future
patching be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max Andr Bndchen" <nospam@.microsoft.com> wrote in message
news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>I try it but when I try a connect with the alias name the server I receive:
>"this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections".
> My alias is like that:
> Name: mycomputer\SQLExpress
> Port: <blank>
> Protocol: TCP/IPa
> Server: mycomputer
> The default SQL Server is running under Network Service account.
> Thanks,
> Max
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> escreveu na mensagem news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>|||Yes, I see. Thanks for the tips!
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> escreveu na mensagem news:O5bday9MGHA.1180@.TK2MSFT
NGP09.phx.gbl...
> As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name
> resolution. You need to enable remote connections using the Surface Area
Configuration tool. Unlike SQL 2000, SQL 2005 (all
> editions) does not allow remote connections immediately following the inst
allation. This is so you can patch a SQL Server before
> exposing it to network connections, should such future patching be necessa
ry.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Max Andr Bndchen" <nospam@.microsoft.com> wrote in message news:uib%23tp
9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>
Multiple instance name
Hi,
Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance" work
with two or more names?
My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
Thanks,
MaxYes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias
for the desired server\instance with whatever server\instance name you like.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Max André Bündchen" <nospam@.microsoft.com> wrote in message
news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance"
> ou make a "named instance" work with two or more names?
> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress"
> named instance and I just have a default instance o SQL Server Developer 2005 (and I would not
> install another instance just for that).
> Thanks,
> Max
>|||I try it but when I try a connect with the alias name the server I receive: "this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections".
My alias is like that:
Name: mycomputer\SQLExpress
Port: <blank>
Protocol: TCP/IPa
Server: mycomputer
The default SQL Server is running under Network Service account.
Thanks,
Max
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu na mensagem
news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
> Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias for the desired
> server\instance with whatever server\instance name you like.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Max André Bündchen" <nospam@.microsoft.com> wrote in message news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance"
>> work with two or more names?
>> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
>> default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
>> Thanks,
>> Max
>|||As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name resolution. You need to
enable remote connections using the Surface Area Configuration tool. Unlike
SQL 2000, SQL 2005 (all editions) does not allow remote connections
immediately following the installation. This is so you can patch a SQL
Server before exposing it to network connections, should such future
patching be necessary.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max André Bündchen" <nospam@.microsoft.com> wrote in message
news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>I try it but when I try a connect with the alias name the server I receive:
>"this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections".
> My alias is like that:
> Name: mycomputer\SQLExpress
> Port: <blank>
> Protocol: TCP/IPa
> Server: mycomputer
> The default SQL Server is running under Network Service account.
> Thanks,
> Max
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> escreveu na mensagem news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>> Yes, but you have to do this on the client. Use the SQL Server
>> Configuration Manager to add an alias for the desired server\instance
>> with whatever server\instance name you like.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Max André Bündchen" <nospam@.microsoft.com> wrote in message
>> news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> Is there a way to make the default instance (SQL 2005) work at the same
>> time as a "named instance" ou make a "named instance" work with two or
>> more names?
>> My problem is that I'm using the QuickStart for VS 2005 and all code
>> work with a "SQLExpress" named instance and I just have a default
>> instance o SQL Server Developer 2005 (and I would not install another
>> instance just for that).
>> Thanks,
>> Max
>>
>|||Yes, I see. Thanks for the tips!
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> escreveu na mensagem news:O5bday9MGHA.1180@.TK2MSFTNGP09.phx.gbl...
> As the message says, the default settings for SQL 2005 do not allow remote connections. This has nothing to do with name
> resolution. You need to enable remote connections using the Surface Area Configuration tool. Unlike SQL 2000, SQL 2005 (all
> editions) does not allow remote connections immediately following the installation. This is so you can patch a SQL Server before
> exposing it to network connections, should such future patching be necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Max André Bündchen" <nospam@.microsoft.com> wrote in message news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>>I try it but when I try a connect with the alias name the server I receive: "this failure may be caused by the fact that under the
>>default settings SQL Server does not allow remote connections".
>> My alias is like that:
>> Name: mycomputer\SQLExpress
>> Port: <blank>
>> Protocol: TCP/IPa
>> Server: mycomputer
>> The default SQL Server is running under Network Service account.
>> Thanks,
>> Max
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu na mensagem
>> news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>> Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias for the desired
>> server\instance with whatever server\instance name you like.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Max André Bündchen" <nospam@.microsoft.com> wrote in message news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance"
>> work with two or more names?
>> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
>> default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
>> Thanks,
>> Max
>>
>>
>
Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance" work
with two or more names?
My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
Thanks,
MaxYes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias
for the desired server\instance with whatever server\instance name you like.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Max André Bündchen" <nospam@.microsoft.com> wrote in message
news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance"
> ou make a "named instance" work with two or more names?
> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress"
> named instance and I just have a default instance o SQL Server Developer 2005 (and I would not
> install another instance just for that).
> Thanks,
> Max
>|||I try it but when I try a connect with the alias name the server I receive: "this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections".
My alias is like that:
Name: mycomputer\SQLExpress
Port: <blank>
Protocol: TCP/IPa
Server: mycomputer
The default SQL Server is running under Network Service account.
Thanks,
Max
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu na mensagem
news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
> Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias for the desired
> server\instance with whatever server\instance name you like.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Max André Bündchen" <nospam@.microsoft.com> wrote in message news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance"
>> work with two or more names?
>> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
>> default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
>> Thanks,
>> Max
>|||As the message says, the default settings for SQL 2005 do not allow remote
connections. This has nothing to do with name resolution. You need to
enable remote connections using the Surface Area Configuration tool. Unlike
SQL 2000, SQL 2005 (all editions) does not allow remote connections
immediately following the installation. This is so you can patch a SQL
Server before exposing it to network connections, should such future
patching be necessary.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max André Bündchen" <nospam@.microsoft.com> wrote in message
news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>I try it but when I try a connect with the alias name the server I receive:
>"this failure may be caused by the fact that under the default settings SQL
>Server does not allow remote connections".
> My alias is like that:
> Name: mycomputer\SQLExpress
> Port: <blank>
> Protocol: TCP/IPa
> Server: mycomputer
> The default SQL Server is running under Network Service account.
> Thanks,
> Max
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> escreveu na mensagem news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>> Yes, but you have to do this on the client. Use the SQL Server
>> Configuration Manager to add an alias for the desired server\instance
>> with whatever server\instance name you like.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Max André Bündchen" <nospam@.microsoft.com> wrote in message
>> news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> Is there a way to make the default instance (SQL 2005) work at the same
>> time as a "named instance" ou make a "named instance" work with two or
>> more names?
>> My problem is that I'm using the QuickStart for VS 2005 and all code
>> work with a "SQLExpress" named instance and I just have a default
>> instance o SQL Server Developer 2005 (and I would not install another
>> instance just for that).
>> Thanks,
>> Max
>>
>|||Yes, I see. Thanks for the tips!
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> escreveu na mensagem news:O5bday9MGHA.1180@.TK2MSFTNGP09.phx.gbl...
> As the message says, the default settings for SQL 2005 do not allow remote connections. This has nothing to do with name
> resolution. You need to enable remote connections using the Surface Area Configuration tool. Unlike SQL 2000, SQL 2005 (all
> editions) does not allow remote connections immediately following the installation. This is so you can patch a SQL Server before
> exposing it to network connections, should such future patching be necessary.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Max André Bündchen" <nospam@.microsoft.com> wrote in message news:uib%23tp9MGHA.3064@.TK2MSFTNGP10.phx.gbl...
>>I try it but when I try a connect with the alias name the server I receive: "this failure may be caused by the fact that under the
>>default settings SQL Server does not allow remote connections".
>> My alias is like that:
>> Name: mycomputer\SQLExpress
>> Port: <blank>
>> Protocol: TCP/IPa
>> Server: mycomputer
>> The default SQL Server is running under Network Service account.
>> Thanks,
>> Max
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> escreveu na mensagem
>> news:uHHdea9MGHA.2764@.TK2MSFTNGP10.phx.gbl...
>> Yes, but you have to do this on the client. Use the SQL Server Configuration Manager to add an alias for the desired
>> server\instance with whatever server\instance name you like.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Max André Bündchen" <nospam@.microsoft.com> wrote in message news:%238KccV9MGHA.3164@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> Is there a way to make the default instance (SQL 2005) work at the same time as a "named instance" ou make a "named instance"
>> work with two or more names?
>> My problem is that I'm using the QuickStart for VS 2005 and all code work with a "SQLExpress" named instance and I just have a
>> default instance o SQL Server Developer 2005 (and I would not install another instance just for that).
>> Thanks,
>> Max
>>
>>
>
Friday, March 23, 2012
Multiple group default database
SQL Server 2000. Windows Auth. If a Windows login is a member of multiple
local groups on the SQL Server box, and each local group maps to a SQL Serve
r
login, and the logins have different default databases, how do you determine
what default database is used for a given Windows login?
Thanks
VernVern,
There is an order. When I tested it seemed like alphabetical order, but I
did not absolutely verify it. Try assigning the first alphabetical group
for a user to default to a database where he has no rights and see if this
causes a login failure.
RLF
"Vern Rabe" <VernRabe@.discussions.microsoft.com> wrote in message
news:7C825239-6888-4DEC-BE0B-59CFB3D2764A@.microsoft.com...
> SQL Server 2000. Windows Auth. If a Windows login is a member of multiple
> local groups on the SQL Server box, and each local group maps to a SQL
> Server
> login, and the logins have different default databases, how do you
> determine
> what default database is used for a given Windows login?
> Thanks
> Vernsql
local groups on the SQL Server box, and each local group maps to a SQL Serve
r
login, and the logins have different default databases, how do you determine
what default database is used for a given Windows login?
Thanks
VernVern,
There is an order. When I tested it seemed like alphabetical order, but I
did not absolutely verify it. Try assigning the first alphabetical group
for a user to default to a database where he has no rights and see if this
causes a login failure.
RLF
"Vern Rabe" <VernRabe@.discussions.microsoft.com> wrote in message
news:7C825239-6888-4DEC-BE0B-59CFB3D2764A@.microsoft.com...
> SQL Server 2000. Windows Auth. If a Windows login is a member of multiple
> local groups on the SQL Server box, and each local group maps to a SQL
> Server
> login, and the logins have different default databases, how do you
> determine
> what default database is used for a given Windows login?
> Thanks
> Vernsql
Monday, March 19, 2012
Multiple Default Values of Parameter
I have a report parameter that will either have 1 value to pick from, or multiple values to pick from depending on who is logged in. I want to be able to set the default value to the first result that is returned in the dataset. Is there a simple way to do this without making a new dataset?Hi,
you either need a new dataset or a static value for the default property. You can′t use the dataset as a expression to get the first value of the dataset.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Subscribe to:
Posts (Atom)