Cluster testing

I need to setup a 2 node cluster for testing.
I have 2 identical servers running Win2k3, but I have a question about the
shared disk device.
For the shared disk can I use a NAS device, one that connects thru a cat5,
or do I need a device that uses scsi?
Remember this is for a short term test.
Thanks
SQL Clustering won't support NAS. SCSI would work, but why not try Virtual
Server 2005? That works great!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"dutch" <dutch@.discussions.microsoft.com> wrote in message
news:2CCAEA46-6F5F-44D6-86A1-5BBAD07F8B18@.microsoft.com...
>I need to setup a 2 node cluster for testing.
> I have 2 identical servers running Win2k3, but I have a question about the
> shared disk device.
> For the shared disk can I use a NAS device, one that connects thru a cat5,
> or do I need a device that uses scsi?
> Remember this is for a short term test.
> Thanks
sqlsql

Cluster setup question

Im viewing the Cluster setup instructions at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
_clustering_51rm.asp
But it doesnt say where to install SQL. It seems to me that if I wanted to
have an Active/ Passive Cluster I would need to intsall it on both boxes? Is
this correct? Are there better links I should be using?
--
SQL2K SP3
TIA, ChrisRYou begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||Well, that is close, but not quite accurate.
Even on a stand-alone installation, when you run the setup dialogue in
interactive mode, all that really happens is that a custom .iss file is
generated from your responses to the questions. Once all of the information
is gathered, setup then executes the setupsql with the newly created
setup.iss file as a parameter.
A cluster install is similar, except the setup.iss is deployed to both
nodes. During the installation, the cluster fails the disk over to each
node so that the individual setup.iss files can be ran against two
independently executed setupsql commands. This creates registry keys.
However, since the first install already created the directory structure,
deployed the binaries, installed the .sql scripts to master, model, and
msdb, this part of the process does not run again a second time. Just the
registry keys, performance counters, and client side tools. And, of course,
the MDAC, which is client side and IS NOT cluster aware.
Also, there is such a thing as the "Primary Node." This is nothing more
than the node from which you started the installation. It does not matter
which node you begin the installation on, as long as it is the node that
currently owns the disk resource you plan on installing SQL Server to.
However, it is important that you keep in mind which node this was.
This node will be the only one that maintains a record of the setup logs.
There is also special CLSIDs that only this node will contain that will not
propagate to the other. The nodes are close to the same configuration, BUT
NOT EXACT. This will be important in the future when you try to add
additional disk resources or swap out old disks for new, if you ever need to
modify or add an additional IP resource, or change the domain the cluster
belongs to. Keeping in mind which node was PRIMARY will only be to your
benefit.
Sincerely,
Anthony Thomas
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
You begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||I have had to change accounts and add/remove disk resources. As long as I
use the current owner node, everything works fine.
Yes, there are some subtle differences such as log files between nodes but
that is only relevant during installation failure troubleshooting. Once
everythign is running, there is no practical difference between nodes,
unlike SQL 7.0 clustering.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:OfrkU8e$EHA.1084@.tk2msftngp13.phx.gbl...
> Well, that is close, but not quite accurate.
> Even on a stand-alone installation, when you run the setup dialogue in
> interactive mode, all that really happens is that a custom .iss file is
> generated from your responses to the questions. Once all of the
information
> is gathered, setup then executes the setupsql with the newly created
> setup.iss file as a parameter.
> A cluster install is similar, except the setup.iss is deployed to both
> nodes. During the installation, the cluster fails the disk over to each
> node so that the individual setup.iss files can be ran against two
> independently executed setupsql commands. This creates registry keys.
> However, since the first install already created the directory structure,
> deployed the binaries, installed the .sql scripts to master, model, and
> msdb, this part of the process does not run again a second time. Just the
> registry keys, performance counters, and client side tools. And, of
course,
> the MDAC, which is client side and IS NOT cluster aware.
> Also, there is such a thing as the "Primary Node." This is nothing more
> than the node from which you started the installation. It does not matter
> which node you begin the installation on, as long as it is the node that
> currently owns the disk resource you plan on installing SQL Server to.
> However, it is important that you keep in mind which node this was.
> This node will be the only one that maintains a record of the setup logs.
> There is also special CLSIDs that only this node will contain that will
not
> propagate to the other. The nodes are close to the same configuration,
BUT
> NOT EXACT. This will be important in the future when you try to add
> additional disk resources or swap out old disks for new, if you ever need
to
> modify or add an additional IP resource, or change the domain the cluster
> belongs to. Keeping in mind which node was PRIMARY will only be to your
> benefit.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> You begin the installation from the node that currently owns the disk
> resource you want SQL data files installed to. You can add additional
disk
> resources after the installation. The SQL installer adds code
automagically
> to the nodes you specify, provided they actually exist and are running at
> install time. You can add or remove nodes from the SQL installation later
> if you need to. Once SQL is installed, there is no difference between
> installed nodes except for which one is actually running SQL at a given
> moment.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "ChrisR" <bla@.noemail.com> wrote in message
> news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> > Im viewing the Cluster setup instructions at:
> >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> > _clustering_51rm.asp
> >
> > But it doesnt say where to install SQL. It seems to me that if I wanted
to
> > have an Active/ Passive Cluster I would need to intsall it on both
boxes?
> Is
> > this correct? Are there better links I should be using?
> >
> > --
> > SQL2K SP3
> >
> > TIA, ChrisR
> >
> >
>sqlsql

Cluster setup question

Im viewing the Cluster setup instructions at:
http://msdn.microsoft.com/library/de...us/howtosql/ht
_clustering_51rm.asp
But it doesnt say where to install SQL. It seems to me that if I wanted to
have an Active/ Passive Cluster I would need to intsall it on both boxes? Is
this correct? Are there better links I should be using?
SQL2K SP3
TIA, ChrisR
You begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/de...us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>
|||Well, that is close, but not quite accurate.
Even on a stand-alone installation, when you run the setup dialogue in
interactive mode, all that really happens is that a custom .iss file is
generated from your responses to the questions. Once all of the information
is gathered, setup then executes the setupsql with the newly created
setup.iss file as a parameter.
A cluster install is similar, except the setup.iss is deployed to both
nodes. During the installation, the cluster fails the disk over to each
node so that the individual setup.iss files can be ran against two
independently executed setupsql commands. This creates registry keys.
However, since the first install already created the directory structure,
deployed the binaries, installed the .sql scripts to master, model, and
msdb, this part of the process does not run again a second time. Just the
registry keys, performance counters, and client side tools. And, of course,
the MDAC, which is client side and IS NOT cluster aware.
Also, there is such a thing as the "Primary Node." This is nothing more
than the node from which you started the installation. It does not matter
which node you begin the installation on, as long as it is the node that
currently owns the disk resource you plan on installing SQL Server to.
However, it is important that you keep in mind which node this was.
This node will be the only one that maintains a record of the setup logs.
There is also special CLSIDs that only this node will contain that will not
propagate to the other. The nodes are close to the same configuration, BUT
NOT EXACT. This will be important in the future when you try to add
additional disk resources or swap out old disks for new, if you ever need to
modify or add an additional IP resource, or change the domain the cluster
belongs to. Keeping in mind which node was PRIMARY will only be to your
benefit.
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
You begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/de...us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>
|||I have had to change accounts and add/remove disk resources. As long as I
use the current owner node, everything works fine.
Yes, there are some subtle differences such as log files between nodes but
that is only relevant during installation failure troubleshooting. Once
everythign is running, there is no practical difference between nodes,
unlike SQL 7.0 clustering.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:OfrkU8e$EHA.1084@.tk2msftngp13.phx.gbl...
> Well, that is close, but not quite accurate.
> Even on a stand-alone installation, when you run the setup dialogue in
> interactive mode, all that really happens is that a custom .iss file is
> generated from your responses to the questions. Once all of the
information
> is gathered, setup then executes the setupsql with the newly created
> setup.iss file as a parameter.
> A cluster install is similar, except the setup.iss is deployed to both
> nodes. During the installation, the cluster fails the disk over to each
> node so that the individual setup.iss files can be ran against two
> independently executed setupsql commands. This creates registry keys.
> However, since the first install already created the directory structure,
> deployed the binaries, installed the .sql scripts to master, model, and
> msdb, this part of the process does not run again a second time. Just the
> registry keys, performance counters, and client side tools. And, of
course,
> the MDAC, which is client side and IS NOT cluster aware.
> Also, there is such a thing as the "Primary Node." This is nothing more
> than the node from which you started the installation. It does not matter
> which node you begin the installation on, as long as it is the node that
> currently owns the disk resource you plan on installing SQL Server to.
> However, it is important that you keep in mind which node this was.
> This node will be the only one that maintains a record of the setup logs.
> There is also special CLSIDs that only this node will contain that will
not
> propagate to the other. The nodes are close to the same configuration,
BUT
> NOT EXACT. This will be important in the future when you try to add
> additional disk resources or swap out old disks for new, if you ever need
to
> modify or add an additional IP resource, or change the domain the cluster
> belongs to. Keeping in mind which node was PRIMARY will only be to your
> benefit.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> You begin the installation from the node that currently owns the disk
> resource you want SQL data files installed to. You can add additional
disk
> resources after the installation. The SQL installer adds code
automagically
> to the nodes you specify, provided they actually exist and are running at
> install time. You can add or remove nodes from the SQL installation later
> if you need to. Once SQL is installed, there is no difference between
> installed nodes except for which one is actually running SQL at a given
> moment.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "ChrisR" <bla@.noemail.com> wrote in message
> news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
>
http://msdn.microsoft.com/library/de...us/howtosql/ht[vbcol=seagreen]
to[vbcol=seagreen]
boxes?
> Is
>

Cluster setup question

Im viewing the Cluster setup instructions at:
http://msdn.microsoft.com/library/d...-us/howtosql/ht
_clustering_51rm.asp
But it doesnt say where to install SQL. It seems to me that if I wanted to
have an Active/ Passive Cluster I would need to intsall it on both boxes? Is
this correct? Are there better links I should be using?
SQL2K SP3
TIA, ChrisRYou begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/d...-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||Well, that is close, but not quite accurate.
Even on a stand-alone installation, when you run the setup dialogue in
interactive mode, all that really happens is that a custom .iss file is
generated from your responses to the questions. Once all of the information
is gathered, setup then executes the setupsql with the newly created
setup.iss file as a parameter.
A cluster install is similar, except the setup.iss is deployed to both
nodes. During the installation, the cluster fails the disk over to each
node so that the individual setup.iss files can be ran against two
independently executed setupsql commands. This creates registry keys.
However, since the first install already created the directory structure,
deployed the binaries, installed the .sql scripts to master, model, and
msdb, this part of the process does not run again a second time. Just the
registry keys, performance counters, and client side tools. And, of course,
the MDAC, which is client side and IS NOT cluster aware.
Also, there is such a thing as the "Primary Node." This is nothing more
than the node from which you started the installation. It does not matter
which node you begin the installation on, as long as it is the node that
currently owns the disk resource you plan on installing SQL Server to.
However, it is important that you keep in mind which node this was.
This node will be the only one that maintains a record of the setup logs.
There is also special CLSIDs that only this node will contain that will not
propagate to the other. The nodes are close to the same configuration, BUT
NOT EXACT. This will be important in the future when you try to add
additional disk resources or swap out old disks for new, if you ever need to
modify or add an additional IP resource, or change the domain the cluster
belongs to. Keeping in mind which node was PRIMARY will only be to your
benefit.
Sincerely,
Anthony Thomas
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
You begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/d...-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||I have had to change accounts and add/remove disk resources. As long as I
use the current owner node, everything works fine.
Yes, there are some subtle differences such as log files between nodes but
that is only relevant during installation failure troubleshooting. Once
everythign is running, there is no practical difference between nodes,
unlike SQL 7.0 clustering.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:OfrkU8e$EHA.1084@.tk2msftngp13.phx.gbl...
> Well, that is close, but not quite accurate.
> Even on a stand-alone installation, when you run the setup dialogue in
> interactive mode, all that really happens is that a custom .iss file is
> generated from your responses to the questions. Once all of the
information
> is gathered, setup then executes the setupsql with the newly created
> setup.iss file as a parameter.
> A cluster install is similar, except the setup.iss is deployed to both
> nodes. During the installation, the cluster fails the disk over to each
> node so that the individual setup.iss files can be ran against two
> independently executed setupsql commands. This creates registry keys.
> However, since the first install already created the directory structure,
> deployed the binaries, installed the .sql scripts to master, model, and
> msdb, this part of the process does not run again a second time. Just the
> registry keys, performance counters, and client side tools. And, of
course,
> the MDAC, which is client side and IS NOT cluster aware.
> Also, there is such a thing as the "Primary Node." This is nothing more
> than the node from which you started the installation. It does not matter
> which node you begin the installation on, as long as it is the node that
> currently owns the disk resource you plan on installing SQL Server to.
> However, it is important that you keep in mind which node this was.
> This node will be the only one that maintains a record of the setup logs.
> There is also special CLSIDs that only this node will contain that will
not
> propagate to the other. The nodes are close to the same configuration,
BUT
> NOT EXACT. This will be important in the future when you try to add
> additional disk resources or swap out old disks for new, if you ever need
to
> modify or add an additional IP resource, or change the domain the cluster
> belongs to. Keeping in mind which node was PRIMARY will only be to your
> benefit.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> You begin the installation from the node that currently owns the disk
> resource you want SQL data files installed to. You can add additional
disk
> resources after the installation. The SQL installer adds code
automagically
> to the nodes you specify, provided they actually exist and are running at
> install time. You can add or remove nodes from the SQL installation later
> if you need to. Once SQL is installed, there is no difference between
> installed nodes except for which one is actually running SQL at a given
> moment.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "ChrisR" <bla@.noemail.com> wrote in message
> news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
>
http://msdn.microsoft.com/library/d...-us/howtosql/ht
to[vbcol=seagreen]
boxes?[vbcol=seagreen]
> Is
>

Cluster setup

We are on SQL Server 2000 A/A cluster and are moving to SQL Server 2005 cluster.

Following are the list of things before proceeding, please let me know if it needs any corrections and add-ons:

(side-by-side) Planning for new installation of SQL Server 2005 ( SQL2005INST1 and SQL2005INST2) on node1 and node2 and restoring the databases on SQL2005INST1 and SQL2005INST2 from respective 2000 instances.

1) SQL2005INST1

SQL Network Name

SQL IP address

2) SQL2005INST2

SQL Network Name

SQL IP address

As 2000 is already existing on the cluster.Want some clarity on following questions.

Can I keep the data files on the same disk as 2000 was using ?

Do I need to have new disk for the Quoram drive?

Under "Virtual Server Configuration" wizard during the setup under "Network to use" for "private cluster network" and "public cluster network" do that IP Address and network address and network subnet will be different from what we gave for SQL 2000.

Thanks

ITTECH

1. For eachc cluster instance, you need separate physically shared disk and IP address.

2. If you have enough physical disks and IP addresses, then you can install SQL Server 2005 on the cluster side by side with SQL Server 2000 without affecting SQL Server 2000.

3. IP address may not be in the same subnet, but it should not be already used by any other application. Otherwise, setup will complain that the IP address is already in use.

|||

Thanks for your reply!

Do I need to have separate shared disk for 2005 instances or is this something recommended ?

|||Yes. Each 2005 instance requires separate physically shared disk and IP address.

Cluster on Same Box (for educational/training purposes)

Is it possible to setup a second instance of SQL Server Enterprise on a box
and setup clustering? I have someone asking me that has only one Server to
do this with and they want to learn about Clustering.
Win2003 <-> Win2003 (SameBox)
OR
Can you run SQL Server on an XP machine and still setup clustering on a
Win2K03 Server and cluster the 2?
XP <--> Win2003 (Two Boxes)
Thanks
Erik
Cluster on XP <--> Win2003 (Two Boxes) -- No, the hardware needs to be
identical.
A better solution would be to run PC emulation software like VMWARE and
create a 2-node virtual cluster on one Windows 2003 computer.
Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.
This posting is provided "as is" with no warranties and confers no rights.

Cluster Environment SQL Server setup and configure

What is the best way to setup and configure a clusterd
environment of SQL Server in terms of RAID, data file
location, log file location, backup etc. I guess in
separate drives for data and logfile.Great question. The bad answer is always "it depends."
You must be doing something like a SAN or DAS right? In very general terms,
split the data, logs, and temp db all out on different raid configs, i.e.,
LUNs. I like RAID 1+0 (or said RAID 10) because of the speed and high
tolerance of multiple disk failures at once, not to mention when you need
more disk space, adding new spindles is easy. If performance is more
important than money, then spread out over as many spindles as feasable.
You achieve more I/Os this way. This means, go for more disks of lower size
than few disks of higher size.
I believe on the SQL disk there is a VB6 application called database hammer
which you can use to test your config.
hth, Eric
"Aboki" <waco361@.hotmail.com> wrote in message
news:0afe01c36b38$2ab80730$a001280a@.phx.gbl...
> What is the best way to setup and configure a clusterd
> environment of SQL Server in terms of RAID, data file
> location, log file location, backup etc. I guess in
> separate drives for data and logfile.sqlsql

Cluster confusion, and instances?

Hey,
I am trying to setup a clustered SQL 2000 environement (active-active) with
3 instances UAT, DEV and PROD.
Should i be using 3 named instances ? Or do I install 3 virtual servers each
being a default instance? I know this is a newbie question but please some
help would be appreciated.
At the moment I would expect 3 virtual servers of SQL 2000 each with their
own IP and NETBIOS name? ie.
10.10.10.1
10.10.10.2
10.10.10.3
Or do i just create 3 named insstances?ie.
10.10.10.1\UAT
10.10.10.1\DEV
10.10.10.1\PROD
Any help is appreciated.
> I am trying to setup a clustered SQL 2000 environement (active-active) with
> 3 instances UAT, DEV and PROD.
Having PROD share a cluster with QA and DEV defeats the whole purpose of
having a cluster which is to provide high availability.

> Should i be using 3 named instances ? Or do I install 3 virtual servers each
> being a default instance?
You can use three named instances. You can't have three default instances in
the same cluster; you can have only one default instance in a cluster.
Linchi
"Daniel" wrote:

> Hey,
> I am trying to setup a clustered SQL 2000 environement (active-active) with
> 3 instances UAT, DEV and PROD.
> Should i be using 3 named instances ? Or do I install 3 virtual servers each
> being a default instance? I know this is a newbie question but please some
> help would be appreciated.
> At the moment I would expect 3 virtual servers of SQL 2000 each with their
> own IP and NETBIOS name? ie.
> 10.10.10.1
> 10.10.10.2
> 10.10.10.3
> Or do i just create 3 named insstances?ie.
> 10.10.10.1\UAT
> 10.10.10.1\DEV
> 10.10.10.1\PROD
> Any help is appreciated.

Cluster confusion, and instances?

Hey,
I am trying to setup a clustered SQL 2000 environement (active-active) with
3 instances UAT, DEV and PROD.
Should i be using 3 named instances ? Or do I install 3 virtual servers each
being a default instance? I know this is a newbie question but please some
help would be appreciated.
At the moment I would expect 3 virtual servers of SQL 2000 each with their
own IP and NETBIOS name? ie.
10.10.10.1
10.10.10.2
10.10.10.3
Or do i just create 3 named insstances?ie.
10.10.10.1\UAT
10.10.10.1\DEV
10.10.10.1\PROD
Any help is appreciated.> I am trying to setup a clustered SQL 2000 environement (active-active) with
> 3 instances UAT, DEV and PROD.
Having PROD share a cluster with QA and DEV defeats the whole purpose of
having a cluster which is to provide high availability.
> Should i be using 3 named instances ? Or do I install 3 virtual servers each
> being a default instance?
You can use three named instances. You can't have three default instances in
the same cluster; you can have only one default instance in a cluster.
Linchi
"Daniel" wrote:
> Hey,
> I am trying to setup a clustered SQL 2000 environement (active-active) with
> 3 instances UAT, DEV and PROD.
> Should i be using 3 named instances ? Or do I install 3 virtual servers each
> being a default instance? I know this is a newbie question but please some
> help would be appreciated.
> At the moment I would expect 3 virtual servers of SQL 2000 each with their
> own IP and NETBIOS name? ie.
> 10.10.10.1
> 10.10.10.2
> 10.10.10.3
> Or do i just create 3 named insstances?ie.
> 10.10.10.1\UAT
> 10.10.10.1\DEV
> 10.10.10.1\PROD
> Any help is appreciated.sqlsql

Cluster confusion, and instances?

Hey,
I am trying to setup a clustered SQL 2000 environement (active-active) with
3 instances UAT, DEV and PROD.
Should i be using 3 named instances ? Or do I install 3 virtual servers each
being a default instance? I know this is a newbie question but please some
help would be appreciated.
At the moment I would expect 3 virtual servers of SQL 2000 each with their
own IP and NETBIOS name? ie.
10.10.10.1
10.10.10.2
10.10.10.3
Or do i just create 3 named insstances?ie.
10.10.10.1\UAT
10.10.10.1\DEV
10.10.10.1\PROD
Any help is appreciated.> I am trying to setup a clustered SQL 2000 environement (active-active) with">
> 3 instances UAT, DEV and PROD.
Having PROD share a cluster with QA and DEV defeats the whole purpose of
having a cluster which is to provide high availability.

> Should i be using 3 named instances ? Or do I install 3 virtual servers ea
ch
> being a default instance?
You can use three named instances. You can't have three default instances in
the same cluster; you can have only one default instance in a cluster.
Linchi
"Daniel" wrote:

> Hey,
> I am trying to setup a clustered SQL 2000 environement (active-active) wit
h
> 3 instances UAT, DEV and PROD.
> Should i be using 3 named instances ? Or do I install 3 virtual servers ea
ch
> being a default instance? I know this is a newbie question but please some
> help would be appreciated.
> At the moment I would expect 3 virtual servers of SQL 2000 each with their
> own IP and NETBIOS name? ie.
> 10.10.10.1
> 10.10.10.2
> 10.10.10.3
> Or do i just create 3 named insstances?ie.
> 10.10.10.1\UAT
> 10.10.10.1\DEV
> 10.10.10.1\PROD
> Any help is appreciated.

cluster admin - rights needed ?

I have read that the cluster admin needs to be a domain admin to setup a
cluster. I am using Win2003 and SQL 2000. Is that true ? If not, what are
the minimum rights required as our n/w admins are hesitant about creating it
as a member of domain admins
Don't be - The answer you got below is correct.
HTH
Bjorn
>--Original Message--
>A microsoft person responded to me (see RE: Services
login policies and
>rights question - "Yuan Shao") that the cluster admin
needs to be a Domain
>Admin...
>Now I'm confused.
>
>
>"Loay Shbeilat [MS]" <loays@.microsoft.com> wrote in
message
>news:eBLL%23G1GEHA.2876@.TK2MSFTNGP09.phx.gbl...
documents? Plz
>point
and confers no
domain admin to setup a
true ? If not, what
>are
hesitant about
>creating
>
>.
>
|||hmm... I guess that Yuan Shao is mistaken !!!
I think he meant that the domain user should be a local administrator on the
nodes.
You can trust me on this one :-) Also check this article on microsoft
website:
http://www.microsoft.com/technet/pro...on124121120120
Under checklist for Server Cluster Configuration-
"A domain-level account that is a member of the local administrators group
on each node. A dedicated account is recommended."
Ya, it is a bit confusing, but it means: "A domain user with admin
previliges on each of the cluster nodes"
Thanks,
Loay Shbeilat
MSCS Admin Tools STE
"This posting is provided "AS IS" with no warranties, and confers no
rights."
"frankm" <frank@.nxspxm.mallardcentral.com> wrote in message
news:%23Jdk7e1GEHA.2224@.TK2MSFTNGP12.phx.gbl...
> A microsoft person responded to me (see RE: Services login policies and
> rights question - "Yuan Shao") that the cluster admin needs to be a Domain
> Admin...
> Now I'm confused.
>
>
> "Loay Shbeilat [MS]" <loays@.microsoft.com> wrote in message
> news:eBLL%23G1GEHA.2876@.TK2MSFTNGP09.phx.gbl...
> point
a
> are
> creating
>
|||That's the way I understood it...
unfortunately things do change - so I don't take chances
"Loay Shbeilat [MS]" <loays@.microsoft.com> wrote in message
news:O%23wpOh$GEHA.1528@.TK2MSFTNGP09.phx.gbl...
> hmm... I guess that Yuan Shao is mistaken !!!
> I think he meant that the domain user should be a local administrator on
the
> nodes.
> You can trust me on this one :-) Also check this article on microsoft
> website:
>
http://www.microsoft.com/technet/pro...on124121120120
> Under checklist for Server Cluster Configuration-
> "A domain-level account that is a member of the local administrators group
> on each node. A dedicated account is recommended."
> Ya, it is a bit confusing, but it means: "A domain user with admin
> previliges on each of the cluster nodes"
> --
> Thanks,
> Loay Shbeilat
> MSCS Admin Tools STE
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
> "frankm" <frank@.nxspxm.mallardcentral.com> wrote in message
> news:%23Jdk7e1GEHA.2224@.TK2MSFTNGP12.phx.gbl...
Domain
setup
> a
what
>
|||Actually it doesn't take much these days...
"Bjorn Mobak" <anonymous@.discussions.microsoft.com> wrote in message
news:1936301c41bed$744a4500$a101280a@.phx.gbl...
> Don't be - The answer you got below is correct.
> HTH
> Bjorn
> login policies and
> needs to be a Domain
> message
> documents? Plz
> and confers no
> domain admin to setup a
> true ? If not, what
> hesitant about

Cluster 2005 need help please

quick overview

2 nodes-cluster setup from node 1

I setup a cluster, created 4 groups

1.cluster 2.msdtc 3.sqlinstance1 4.sqlinstance2

I want to create an active\passive on both nodes. (onenode will be the active node for on sql install while the other is passive.

I want to repeat this fo rthe second node, the second node being active and node 1 passive.

I logged into node 1 and I installed sql 2005 in failover cluster into sqlinstance 1., everyhting was fine, failover etc.

Now I logged into node 2 and ran sql 2005 setup to create a failover cluster.

I chose to install into sql instance 2.

Database unable to install with error "failed to set registry settings for server network libraries. acition is setdefaults.error 11001, no such host is known.

If I am not setting this up correclty please let me know

thanks

everything was fine. I logged onto node 2, was going to

Which node owns the disk resources that you are trying to install to? You can very simply run the setup routine twice from the same node. Then when you are done with both installs, all you have to do is move the group for one of the instances to the other node and you are done with your configuration. The node that you install from is irrelevant to where you want the instances to run.|||

Hi,

I don't know specifically the answer to your question, but here is a white paper that you might find useful:

SQL Server 2005 Failover Clustering
http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en

|||

the architect wants sql installed on both nodes. All groups and reasources are owned by node 2, just not the first install of sql which is still owned by node 1.

thanks

|||

Hi,

This issue happens due to a orphan registry key.

Delete the followinh key from both nodes:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Cluster

Be carefull while deleting the key, as quorum checkpointnig could cause issues.

HTH

Cluster 2005 need help please

quick overview

2 nodes-cluster setup from node 1

I setup a cluster, created 4 groups

1.cluster 2.msdtc 3.sqlinstance1 4.sqlinstance2

I want to create an active\passive on both nodes. (onenode will be the active node for on sql install while the other is passive.

I want to repeat this fo rthe second node, the second node being active and node 1 passive.

I logged into node 1 and I installed sql 2005 in failover cluster into sqlinstance 1., everyhting was fine, failover etc.

Now I logged into node 2 and ran sql 2005 setup to create a failover cluster.

I chose to install into sql instance 2.

Database unable to install with error "failed to set registry settings for server network libraries. acition is setdefaults.error 11001, no such host is known.

If I am not setting this up correclty please let me know

thanks

everything was fine. I logged onto node 2, was going to

Which node owns the disk resources that you are trying to install to? You can very simply run the setup routine twice from the same node. Then when you are done with both installs, all you have to do is move the group for one of the instances to the other node and you are done with your configuration. The node that you install from is irrelevant to where you want the instances to run.|||

Hi,

I don't know specifically the answer to your question, but here is a white paper that you might find useful:

SQL Server 2005 Failover Clustering
http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en

|||

the architect wants sql installed on both nodes. All groups and reasources are owned by node 2, just not the first install of sql which is still owned by node 1.

thanks

|||

Hi,

This issue happens due to a orphan registry key.

Delete the followinh key from both nodes:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Cluster

Be carefull while deleting the key, as quorum checkpointnig could cause issues.

HTH

cluster ? on muliple data disks

Hi,
I have setup a 2 node a/p cluster. During install i picked the s drive as
the data drive, and the L drive as the log drive.
i was able to create a db on the S drive
now i want to create a database and use the z drive. but it won't show me
the Z drive as a option when i try to browse to a different drive as part of
the create new db steps.
both disks are disk resources managed by the cluster
in the past, i have been able to do it on a non clustered server
what is the trick with a cluster?
The "trick" is twofold. First, you have to make the disks Cluster Resources
and put them in the resource group for the SQL virtual server. I am
guessing this is where you are at. Second, you have to make the SQL Service
dependent on the disk resource. You will have to take the service offline
to make the change. Look at the dependency relationship between the SQL
service and the existing disk resources.
Geoff N. Hiten
Microsoft SQL Server MVP
"jason" <jason@.discussions.microsoft.com> wrote in message
news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> Hi,
> I have setup a 2 node a/p cluster. During install i picked the s drive as
> the data drive, and the L drive as the log drive.
> i was able to create a db on the S drive
> now i want to create a database and use the z drive. but it won't show me
> the Z drive as a option when i try to browse to a different drive as part
> of
> the create new db steps.
> both disks are disk resources managed by the cluster
> in the past, i have been able to do it on a non clustered server
> what is the trick with a cluster?
|||Geoff, that did it thanks!
"Geoff N. Hiten" wrote:

> The "trick" is twofold. First, you have to make the disks Cluster Resources
> and put them in the resource group for the SQL virtual server. I am
> guessing this is where you are at. Second, you have to make the SQL Service
> dependent on the disk resource. You will have to take the service offline
> to make the change. Look at the dependency relationship between the SQL
> service and the existing disk resources.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
>
>

cluster ? on muliple data disks

Hi,
I have setup a 2 node a/p cluster. During install i picked the s drive as
the data drive, and the L drive as the log drive.
i was able to create a db on the S drive
now i want to create a database and use the z drive. but it won't show me
the Z drive as a option when i try to browse to a different drive as part of
the create new db steps.
both disks are disk resources managed by the cluster
in the past, i have been able to do it on a non clustered server
what is the trick with a cluster?The "trick" is twofold. First, you have to make the disks Cluster Resources
and put them in the resource group for the SQL virtual server. I am
guessing this is where you are at. Second, you have to make the SQL Service
dependent on the disk resource. You will have to take the service offline
to make the change. Look at the dependency relationship between the SQL
service and the existing disk resources.
Geoff N. Hiten
Microsoft SQL Server MVP
"jason" <jason@.discussions.microsoft.com> wrote in message
news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> Hi,
> I have setup a 2 node a/p cluster. During install i picked the s drive as
> the data drive, and the L drive as the log drive.
> i was able to create a db on the S drive
> now i want to create a database and use the z drive. but it won't show me
> the Z drive as a option when i try to browse to a different drive as part
> of
> the create new db steps.
> both disks are disk resources managed by the cluster
> in the past, i have been able to do it on a non clustered server
> what is the trick with a cluster?|||Geoff, that did it thanks!
"Geoff N. Hiten" wrote:
> The "trick" is twofold. First, you have to make the disks Cluster Resources
> and put them in the resource group for the SQL virtual server. I am
> guessing this is where you are at. Second, you have to make the SQL Service
> dependent on the disk resource. You will have to take the service offline
> to make the change. Look at the dependency relationship between the SQL
> service and the existing disk resources.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> > Hi,
> > I have setup a 2 node a/p cluster. During install i picked the s drive as
> > the data drive, and the L drive as the log drive.
> > i was able to create a db on the S drive
> > now i want to create a database and use the z drive. but it won't show me
> > the Z drive as a option when i try to browse to a different drive as part
> > of
> > the create new db steps.
> >
> > both disks are disk resources managed by the cluster
> >
> > in the past, i have been able to do it on a non clustered server
> >
> > what is the trick with a cluster?
>
>

cluster ? on muliple data disks

Hi,
I have setup a 2 node a/p cluster. During install i picked the s drive as
the data drive, and the L drive as the log drive.
i was able to create a db on the S drive
now i want to create a database and use the z drive. but it won't show me
the Z drive as a option when i try to browse to a different drive as part of
the create new db steps.
both disks are disk resources managed by the cluster
in the past, i have been able to do it on a non clustered server
what is the trick with a cluster?The "trick" is twofold. First, you have to make the disks Cluster Resources
and put them in the resource group for the SQL virtual server. I am
guessing this is where you are at. Second, you have to make the SQL Service
dependent on the disk resource. You will have to take the service offline
to make the change. Look at the dependency relationship between the SQL
service and the existing disk resources.
Geoff N. Hiten
Microsoft SQL Server MVP
"jason" <jason@.discussions.microsoft.com> wrote in message
news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> Hi,
> I have setup a 2 node a/p cluster. During install i picked the s drive as
> the data drive, and the L drive as the log drive.
> i was able to create a db on the S drive
> now i want to create a database and use the z drive. but it won't show me
> the Z drive as a option when i try to browse to a different drive as part
> of
> the create new db steps.
> both disks are disk resources managed by the cluster
> in the past, i have been able to do it on a non clustered server
> what is the trick with a cluster?|||Geoff, that did it thanks!
"Geoff N. Hiten" wrote:

> The "trick" is twofold. First, you have to make the disks Cluster Resourc
es
> and put them in the resource group for the SQL virtual server. I am
> guessing this is where you are at. Second, you have to make the SQL Servi
ce
> dependent on the disk resource. You will have to take the service offline
> to make the change. Look at the dependency relationship between the SQL
> service and the existing disk resources.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
>
>

Cluster / SQL 2005 / SAN storage

Hi...I got some basic questions in regards to setup a lab environment
with two nodes cluster over Windows ent 2003, ent SQL 2005 and SAN
storage.
1) Would the following hardware be enough: SAN storage, fiber channel
switch, two intel servers, 4 HBA (2 for each servers) ?
2) what is the difference betwen fiber channel switch and fiber
channel routing?
3) what is different between fiber channel and iSCSI?
4) what is the zoning?
5) what is the steps to install the cluster windows server?
6) what is the steps to configure the SQL2005? do I need to install
SQL twice in each node, or I just need to install once in the vitual
server?
7) what is the draft diagram?
8) what is the private network, public network for SAN?
Thanks,
Yve

> 1) Would the following hardware be enough: SAN storage, fiber channel
> switch, two intel servers, 4 HBA (2 for each servers) ?
Best practice would be to have two FC switches to create two fabrics for
redundancy. Also as you mention 2 HBA's per node, you probably want "Multi
path software", contact your storage vendor to get more information.

> 2) what is the difference betwen fiber channel switch and fiber
> channel routing?
Switching is done within a fabric. In VERY large installations, routing
might be needed to "route" between various fabrics, most installations, even
with multiple fabrics, you would find switches only. If you only build a
cluster in a lab, you would not need routing.

> 3) what is different between fiber channel and iSCSI?
iSCSI runs over IP protocol, iSCSI is deemed to be more cost efficient,
however when building a SAN there are many questions on cost, speed,
performance, interoperability and reliability (.. .and so on).

> 4) what is the zoning?
In a Fibre Channel Fabric, Zoning determines which HBA can talk to which
port on the Storage.
(e.g. HBA-1 from Server-2 can communicate to Port-X on Storage-A) this
allows multiple Servers and multiple Storage units to be connected to a
Fabric, without "conflicting" traffic on your SAN)

> 5) what is the steps to install the cluster windows server?
Have a read of this first:
- http://technet2.microsoft.com/windowsserver/en/technologies/genclust.mspx
A good collection of cluster related articles can be found here:
- http://www.nw-america.com/

> 6) what is the steps to configure the SQL2005? do I need to install
> SQL twice in each node, or I just need to install once in the vitual
> server?
Have a read about this in the online books

> 7) what is the draft diagram?
I leave this to SQL guys to answer

> 8) what is the private network, public network for SAN?
- private network is the IP network between the Cluster Nodes for cluster
(only) communications
- public network is the IP network both nodes are connected to, and which
will be used for users to connect to your clustered SQL databases
- private/public networks have nothing to do with SAN, SAN is the network
(FC or iSCSI) which connects your nodes to the shared storage.

> Thanks,
> Yve
>
Hope this helps,
Rgds,
Edwin.

closing connection problem

I have setup my loop to loop through textboxes and fill the according textboxes with data it retrives, if seems to work fine, but there is a problem with opening and closing the connection below is my code

int i = 0;for (i = 1; i <= 3; i++)

{

//This gets the stock ID from the textbox.

string stock_ID = ((TextBox)Panel1.FindControl("txtID" + i.ToString())).Text;

//This is the sql statement.

string sql ="SELECT [n_or_sh], [title], [cost_price], [selling_price] FROM tbl_stock WHERE stock_ID = " + stock_ID;

//This creates a sql command which executes the sql statement.

SqlCommand sqlCmd =newSqlCommand(sql, myConn);

myConn.Open();

//This is a reader for the results to go in.

SqlDataReader dr = sqlCmd.ExecuteReader();

//This reads the first result from the sqlReader

dr.Read();

//This sets the title label text to the value of the description column.

TextBox currentBox1 = (TextBox)Panel1.FindControl("txtDesc" + i);

string strtxtDesc = currentBox1.Text;

strtxtDesc = dr["title"].ToString();

}// end of loop

myConn.Close();

}// end of button click

i have tried putting the myConn.Close() in different places but it dosnt seem to work!

any advice or tips ?

Regards
Jez

1. You should use SqlParameter object to pass your ID. This makes the sql query optimizer to keep your query optimized for future uses, and takes you out of the sql injection attack risk.
2. You should close the SqlDataReader before closing the connection. Try dr.Close() (or better, dr.Dispose() )
3. For best practice, you should also dispose your sql connection. Try myConn.Dispose() (after closing it)

Client Tools

Can I freely download a Setup for SQL 2000 Server Client Tools only?If you have a legal and licensed installation somewhere, presumably you can
install the client tools from the CD. You can't download Enterprise
Manager, Query Analyzer, Profiler, etc.
"Mrc" <StopTheVirus@.microsoft.com> wrote in message
news:lpUrb.3878$hV.211933@.news2.tin.it...
> Can I freely download a Setup for SQL 2000 Server Client Tools only?
>

client setup

Can anyone tell me how to setup a client connection to
SQL server 2000?
All you need is an ODBC driver or OLE DB Provider for SQL Server. Once one
of them is in place, you need a tool like Query Analyzer or Enterprise
Manager to connect to SQL Server. All of them (client tools) can be
installed using the SQL Server setup CD.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"brbaskets" <anonymous@.discussions.microsoft.com> wrote in message
news:944a01c4337c$8f2dc800$a501280a@.phx.gbl...
Can anyone tell me how to setup a client connection to
SQL server 2000?
|||Hi,
Install SQL Server client software coming along with SQL Server Installation CD. While installation select the "client only".
After the installation use any of the below tools to connect to SQL Server
1. Query Analyzer
2. Enterprise manager
3. OSQL / ISQL command line utilities
Note:
If you are not able to connect to servers or if the SQL server name is not automatically displayed in the server list then create a Alias name using "CLIENT NETWORK Utility" by providing the Protocol, IP ADDRESS and PORT number. Then using the Alias name
created you can connect to SQL Server.
Thanks
Hari
MCDBA
-- brbaskets wrote: --
Can anyone tell me how to setup a client connection to
SQL server 2000?
|||If you are asking about client connectivity via an application; you have
everything you need already installed. MDAC contains all necessary
components to connect to SQL Server, except the application to connect. You
can use Query Analyzer or Enterprise Manager or any other application that
connects to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||simply run the connectivity tools which is avalable in sql server cdrom.
"brbaskets" <anonymous@.discussions.microsoft.com> wrote in message
news:944a01c4337c$8f2dc800$a501280a@.phx.gbl...
> Can anyone tell me how to setup a client connection to
> SQL server 2000?