Multiple instances SQL server 2000 - destination folders

Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?
Yes, specify a different installation folder. There will be some shared
components though.
You have to install service packs/security patches/hot fixes for each
instance separately.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.4ax.com...
Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?
|||just specify the \Program files\Microsoft SQL Server will be enough , it
will create a directory below there called MSSQL$<INSTANCEName> (default
will go in MSSQL).
re Service Packs , yes you need to apply seperately for each instance,
although certain components asre common across instances - ie MDAC and Full
Text Search
cheers
Andy
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.4ax.com...
> Can someone clarify for me, if I were to install 2 named instances of
> SQL server 2000, whether I must define 2 different destination folders
> for the program files ?
> Or can I leave the Program Files destination folder the same for both
> instances [c:\program files\Microsoft SQL Server] ?
> I am separating the data files in their own data file destination
> directory [d:\...\microsoft sql server\data\name_of_instance1 and
> d:\...\microsoft sql server\data\name_of_instance2
> And also, will I need to run service packs for each named instance
> separately ?
|||Okay, Andy's response is precise, for your first question :-)
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:OGyegcnYEHA.2456@.TK2MSFTNGP10.phx.gbl...
Yes, specify a different installation folder. There will be some shared
components though.
You have to install service packs/security patches/hot fixes for each
instance separately.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.4ax.com...
Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?
|||On Mon, 5 Jul 2004 11:03:05 +0100, "Andy Ball"
<andy.ball@.remove4spam_greenfell.com> wrote:

>just specify the \Program files\Microsoft SQL Server will be enough , it
>will create a directory below there called MSSQL$<INSTANCEName> (default
>will go in MSSQL).
>re Service Packs , yes you need to apply seperately for each instance,
>although certain components asre common across instances - ie MDAC and Full
>Text Search
>cheers
>Andy
>
That's correct! Thanks for such a fast reply. I just finished checking
it on a test server! SQL server handles this just fine.

Multiple instances SQL server 2000 - destination folders

Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?Yes, specify a different installation folder. There will be some shared
components though.
You have to install service packs/security patches/hot fixes for each
instance separately.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.
4ax.com...
Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?|||just specify the \Program files\Microsoft SQL Server will be enough , it
will create a directory below there called MSSQL$<INSTANCEName> (default
will go in MSSQL).
re Service Packs , yes you need to apply seperately for each instance,
although certain components asre common across instances - ie MDAC and Full
Text Search
cheers
Andy
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.
4ax.com...
> Can someone clarify for me, if I were to install 2 named instances of
> SQL server 2000, whether I must define 2 different destination folders
> for the program files ?
> Or can I leave the Program Files destination folder the same for both
> instances [c:\program files\Microsoft SQL Server] ?
> I am separating the data files in their own data file destination
> directory [d:\...\microsoft sql server\data\name_of_instance1 and
> d:\...\microsoft sql server\data\name_of_instance2
> And also, will I need to run service packs for each named instance
> separately ?|||Okay, Andy's response is precise, for your first question :-)
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:OGyegcnYEHA.2456@.TK2MSFTNGP10.phx.gbl...
Yes, specify a different installation folder. There will be some shared
components though.
You have to install service packs/security patches/hot fixes for each
instance separately.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.
4ax.com...
Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?|||On Mon, 5 Jul 2004 11:03:05 +0100, "Andy Ball"
<andy.ball@.remove4spam_greenfell.com> wrote:

>just specify the \Program files\Microsoft SQL Server will be enough , it
>will create a directory below there called MSSQL$<INSTANCEName> (default
>will go in MSSQL).
>re Service Packs , yes you need to apply seperately for each instance,
>although certain components asre common across instances - ie MDAC and Full
>Text Search
>cheers
>Andy
>
That's correct! Thanks for such a fast reply. I just finished checking
it on a test server! SQL server handles this just fine.

Multiple instances SQL server 2000 - destination folders

Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?Yes, specify a different installation folder. There will be some shared
components though.
You have to install service packs/security patches/hot fixes for each
instance separately.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.4ax.com...
Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?|||just specify the \Program files\Microsoft SQL Server will be enough , it
will create a directory below there called MSSQL$<INSTANCEName> (default
will go in MSSQL).
re Service Packs , yes you need to apply seperately for each instance,
although certain components asre common across instances - ie MDAC and Full
Text Search
cheers
Andy
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.4ax.com...
> Can someone clarify for me, if I were to install 2 named instances of
> SQL server 2000, whether I must define 2 different destination folders
> for the program files ?
> Or can I leave the Program Files destination folder the same for both
> instances [c:\program files\Microsoft SQL Server] ?
> I am separating the data files in their own data file destination
> directory [d:\...\microsoft sql server\data\name_of_instance1 and
> d:\...\microsoft sql server\data\name_of_instance2
> And also, will I need to run service packs for each named instance
> separately ?|||Okay, Andy's response is precise, for your first question :-)
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:OGyegcnYEHA.2456@.TK2MSFTNGP10.phx.gbl...
Yes, specify a different installation folder. There will be some shared
components though.
You have to install service packs/security patches/hot fixes for each
instance separately.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:hu8ie014lns9k5lrcgldb8erth0i2c0rn7@.4ax.com...
Can someone clarify for me, if I were to install 2 named instances of
SQL server 2000, whether I must define 2 different destination folders
for the program files ?
Or can I leave the Program Files destination folder the same for both
instances [c:\program files\Microsoft SQL Server] ?
I am separating the data files in their own data file destination
directory [d:\...\microsoft sql server\data\name_of_instance1 and
d:\...\microsoft sql server\data\name_of_instance2
And also, will I need to run service packs for each named instance
separately ?|||On Mon, 5 Jul 2004 11:03:05 +0100, "Andy Ball"
<andy.ball@.remove4spam_greenfell.com> wrote:
>just specify the \Program files\Microsoft SQL Server will be enough , it
>will create a directory below there called MSSQL$<INSTANCEName> (default
>will go in MSSQL).
>re Service Packs , yes you need to apply seperately for each instance,
>although certain components asre common across instances - ie MDAC and Full
>Text Search
>cheers
>Andy
>
That's correct! Thanks for such a fast reply. I just finished checking
it on a test server! SQL server handles this just fine.sql

multiple instances on one virtual server

In a failover cluster is there any way at all that more than one named SQL
Server instance can exist on a virtual server?
Thanks!
No. Each virtual server can host exactly one instance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Robert Kinesta" <RobertKinesta@.discussions.microsoft.com> wrote in message
news:D02ECF04-7BC1-41B5-B35D-88D938E28FCC@.microsoft.com...
> In a failover cluster is there any way at all that more than one named SQL
> Server instance can exist on a virtual server?
> Thanks!
|||Hi,
Yes you can do that.
It is called a Multiple-Instance cluster. A Multile-Instance cluster
supports upto four nodes and supports 16 instances (1 default and 15 named or
16 named). This implementation requires extensive planning as each virtual
server requires its own disk resources that can not be shared by other
instances.
Hth
DeeJay Puar
MCDBA
"Robert Kinesta" wrote:

> In a failover cluster is there any way at all that more than one named SQL
> Server instance can exist on a virtual server?
> Thanks!

multiple instances on one virtual server

In a failover cluster is there any way at all that more than one named SQL
Server instance can exist on a virtual server?
Thanks!No. Each virtual server can host exactly one instance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Robert Kinesta" <RobertKinesta@.discussions.microsoft.com> wrote in message
news:D02ECF04-7BC1-41B5-B35D-88D938E28FCC@.microsoft.com...
> In a failover cluster is there any way at all that more than one named SQL
> Server instance can exist on a virtual server?
> Thanks!|||Hi,
Yes you can do that.
It is called a Multiple-Instance cluster. A Multile-Instance cluster
supports upto four nodes and supports 16 instances (1 default and 15 named o
r
16 named). This implementation requires extensive planning as each virtual
server requires its own disk resources that can not be shared by other
instances.
Hth
DeeJay Puar
MCDBA
"Robert Kinesta" wrote:

> In a failover cluster is there any way at all that more than one named SQL
> Server instance can exist on a virtual server?
> Thanks!

multiple instances on one virtual server

In a failover cluster is there any way at all that more than one named SQL
Server instance can exist on a virtual server?
Thanks!No. Each virtual server can host exactly one instance.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Robert Kinesta" <RobertKinesta@.discussions.microsoft.com> wrote in message
news:D02ECF04-7BC1-41B5-B35D-88D938E28FCC@.microsoft.com...
> In a failover cluster is there any way at all that more than one named SQL
> Server instance can exist on a virtual server?
> Thanks!|||Hi,
Yes you can do that.
It is called a Multiple-Instance cluster. A Multile-Instance cluster
supports upto four nodes and supports 16 instances (1 default and 15 named or
16 named). This implementation requires extensive planning as each virtual
server requires its own disk resources that can not be shared by other
instances.
Hth
DeeJay Puar
MCDBA
"Robert Kinesta" wrote:
> In a failover cluster is there any way at all that more than one named SQL
> Server instance can exist on a virtual server?
> Thanks!

Multiple instances on cluster

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.

Multiple instances in a virtual server

We want to create another named instance of SQL Server 2000 (sp 3a) in a SQL
2000 active/active cluster virtual server. We are finding evidence in
several forums (including this one) that we cannot do that : we would need a
new virtual server with its own instance instead. (The problem is our
bespoke software supplier doesn't support that!) Does anybody have any
DEFINITE proof (eg. from Microsoft themselves) that this is the case?
Cheers,
Colin
From BOL. Topic header "Creating a Failover Cluster"
Last bulleted item. 'One Instance...
--SNIP
Elements of a Virtual Server
A virtual server contains:
a.. A combination of one or more disks in a Microsoft Cluster Service
(MSCS) cluster group.
Each MSCS cluster group can contain at most one virtual SQL Server.
b.. A network name for each virtual server. This network name is the
virtual server name.
c.. One or more IP addresses that are used to connect to each virtual
server.
d.. One instance of SQL Server 2000, including a SQL Server resource, a
SQL Server Agent resource, and a full-text resource.
If an administrator uninstalls the instance of SQL Server 2000 within a
virtual server, the virtual server, including all IP addresses and the
network name, is also removed from the MSCS cluster group
--SNIP
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Colin Bunting" <ColinBunting@.discussions.microsoft.com> wrote in message
news:4F3951C7-E521-4FDB-95F0-4C07E2B380E0@.microsoft.com...
> We want to create another named instance of SQL Server 2000 (sp 3a) in a
SQL
> 2000 active/active cluster virtual server. We are finding evidence in
> several forums (including this one) that we cannot do that : we would
need a
> new virtual server with its own instance instead. (The problem is our
> bespoke software supplier doesn't support that!) Does anybody have any
> DEFINITE proof (eg. from Microsoft themselves) that this is the case?
> --
> Cheers,
> Colin
>

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

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...
>

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
>>
>>
>

Multiple Instance & Licensing

Can multiple instances of SQL Server be installed on the same machine under the same license?For example, a named instanced called WAREHOUSE and another called CHGMGMTSYS.

Yes, you can run multiple instances under the same license. For more detailed license info, check out this link:

http://www.microsoft.com/sql/howtobuy/default.mspx

Thanks,
Sam Lester (MSFT)

Multiple data insertion with For clause

Suppose I have a table named test with two fields(sl int,age int).
I want to insert 10 records all at a time.The records are in an incremental manner.I like to insert 1,2,3,4,5,6,7,8,9,10 for sl column and
22,23,24,25,26,27,28,29,30,31 for age column.But the procedure should follow C protype using for (j=1;j<10,j++) clause.
Is it possible to insert in SQL SERVER following c protype?
What is the fastest way for inserting multiple sequevcial data?
SubhasishFor relatively small sequential sets, do something like this...

INSERT INTO TEST(sl, age)
SELECT a.i, a.i+21
FROM (
SELECT i = 1 UNION
SELECT i = 2 UNION
SELECT i = 3 UNION
SELECT i = 4 UNION
SELECT i = 5 UNION
SELECT i = 6 UNION
SELECT i = 7 UNION
SELECT i = 8 UNION
SELECT i = 9 UNION
SELECT i = 10 ) as a

You can build up the derived table query quickly with cut-and-paste, then go back and fix the values

For bigger sequential sets, build yourself a temporary table of sequential integers like this:

CREATE TABLE #i
(x INT IDENTITY(1,1),
y INT)

INSERT INTO #i
VALUES(NULL)

INSERT INTO #i
SELECT y FROM #i

Running the last statement over and over will populate table #i with sequential integers in the x column. 11 executions gets you 1K rows, 21 gets you 1M rows, ... Then use the temporary table to drive your insert.

INSERT INTO test(sl, age)
SELECT #i.x, #i.x+21
FROM #i
WHERE #i.x < 100 -- for 100 rows|||I think s/he's looking for a loop as well...

USE Northwind
GO

CREATE TABLE myTable99 (sl int,age int)
GO

DECLARE @.x int, @.y int

SELECT @.x = 1, @.y = 1

WHILE @.x < 100
BEGIN
INSERT INTO myTable99 (sl, age)
SELECT @.X, 1*@.y UNION ALL
SELECT @.X, 2*@.y UNION ALL
SELECT @.X, 3*@.y UNION ALL
SELECT @.X, 4*@.y UNION ALL
SELECT @.X, 5*@.y UNION ALL
SELECT @.X, 6*@.y UNION ALL
SELECT @.X, 7*@.y UNION ALL
SELECT @.X, 8*@.y UNION ALL
SELECT @.X, 9*@.y UNION ALL
SELECT @.X, 10*@.y

SELECT @.x = @.x + 1, @.y = @.y + 1
END

SELECT COUNT(*) FROM myTable99
GO

DROP TABLE myTable99
GO