Clustering Docs/Books

Hi All
Happy new year. I am looking for any good books/websites/guides that can
teach me how to cluster SQl server and the kind of interfaces i will be using
to monitor that clustered environment. What will be the diferences between
the usuall monitoring tools (enterprise manager/SQl anlyser) in a normal and
the clustered environment? Thank you in advance.
Which SQL version and OS do you intend to use? The material is somewhat
different for each version and OS.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
news:F730035A-B623-4F30-9A75-ED8BF063F55C@.microsoft.com...
> Hi All
> Happy new year. I am looking for any good books/websites/guides that can
> teach me how to cluster SQl server and the kind of interfaces i will be
> using
> to monitor that clustered environment. What will be the diferences between
> the usuall monitoring tools (enterprise manager/SQl anlyser) in a normal
> and
> the clustered environment? Thank you in advance.
>
|||Thank for the reply. I am using Windows 2000 os and SQL Server 2000.
"Geoff N. Hiten" wrote:

> Which SQL version and OS do you intend to use? The material is somewhat
> different for each version and OS.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
> news:F730035A-B623-4F30-9A75-ED8BF063F55C@.microsoft.com...
>
>
|||If you are building a new cluster, I strongly suggest Windows 2003 for the
base OS. The clustering components alone are worth the upgrade.
Here is an excellent starting point for SQL 2000 clustering.
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Here is a general High Availability presentation. I like it becuase it
reminds everyone that clustering is only one element towards a highly
availabile system
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
news:0955F177-255C-4D1A-AC8E-A71E63DCE38F@.microsoft.com...[vbcol=seagreen]
> Thank for the reply. I am using Windows 2000 os and SQL Server 2000.
>
> "Geoff N. Hiten" wrote:
|||Thank you so much Geoff. I will read this.
"Geoff N. Hiten" wrote:

> If you are building a new cluster, I strongly suggest Windows 2003 for the
> base OS. The clustering components alone are worth the upgrade.
> Here is an excellent starting point for SQL 2000 clustering.
> SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/pro.../failclus.mspx
> Here is a general High Availability presentation. I like it becuase it
> reminds everyone that clustering is only one element towards a highly
> availabile system
> http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
> news:0955F177-255C-4D1A-AC8E-A71E63DCE38F@.microsoft.com...
>
>
|||
The first thing is that just about everyone makes this WAY too complicated
and winds up making a VERY big issue out of a lot of things that have
absolutely nothing at all to do with clustering.
You are going to find people going on and on and on and on about processor
resources, memory, disk drives, I/O, processor affinity, SQL Server
configuration, etc. NONE of which has anything at all to do with
clustering. People always want to chuck this stuff under clustering, to
basically give themselves something to talk about. (You face 100% of these
issues if you are installing multiple instances of SQL Server on a
standalone machine.) They aren't cluster issues, they are multiple instance
issues.
What do you need to know about clustering? You need to install the Windows
cluster. Windows Help will give you step by step instructions for doing
that. Once you finish the Windows cluster install, you need to know exactly
1 thing. The Windows cluster (regardless of the number of physical pieces
of hardware under it) is a single hardware platform with respect to SQL
Server. Any SQL Server installed into the cluster will look, act, and
function exactly like any other SQL Server installed to a standalone
machine. You management tools, maintenance routines, applications,
monitoring, etc. only know they are connecting to a SQL Server instance and
do not care if that instance just happens to be running in a cluster or it
is sitting on a standalone machine.
A SQL Server DBA does absolutely nothing at all different for a SQL Server
in a cluster than they would for a SQL Server on a standalone machine.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
news:F730035A-B623-4F30-9A75-ED8BF063F55C@.microsoft.com...
> Hi All
> Happy new year. I am looking for any good books/websites/guides that can
> teach me how to cluster SQl server and the kind of interfaces i will be
> using
> to monitor that clustered environment. What will be the diferences between
> the usuall monitoring tools (enterprise manager/SQl anlyser) in a normal
> and
> the clustered environment? Thank you in advance.
>
|||> A SQL Server DBA does absolutely nothing at all different for a SQL Server
> in a cluster than they would for a SQL Server on a standalone machine.
That is the case until one needs to fix things.
Linchi
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:ecYxVaMEGHA.3856@.TK2MSFTNGP12.phx.gbl...
>
> The first thing is that just about everyone makes this WAY too complicated
> and winds up making a VERY big issue out of a lot of things that have
> absolutely nothing at all to do with clustering.
> You are going to find people going on and on and on and on about processor
> resources, memory, disk drives, I/O, processor affinity, SQL Server
> configuration, etc. NONE of which has anything at all to do with
> clustering. People always want to chuck this stuff under clustering, to
> basically give themselves something to talk about. (You face 100% of
> these issues if you are installing multiple instances of SQL Server on a
> standalone machine.) They aren't cluster issues, they are multiple
> instance issues.
> What do you need to know about clustering? You need to install the
> Windows cluster. Windows Help will give you step by step instructions for
> doing that. Once you finish the Windows cluster install, you need to know
> exactly 1 thing. The Windows cluster (regardless of the number of
> physical pieces of hardware under it) is a single hardware platform with
> respect to SQL Server. Any SQL Server installed into the cluster will
> look, act, and function exactly like any other SQL Server installed to a
> standalone machine. You management tools, maintenance routines,
> applications, monitoring, etc. only know they are connecting to a SQL
> Server instance and do not care if that instance just happens to be
> running in a cluster or it is sitting on a standalone machine.
> A SQL Server DBA does absolutely nothing at all different for a SQL Server
> in a cluster than they would for a SQL Server on a standalone machine.
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
> news:F730035A-B623-4F30-9A75-ED8BF063F55C@.microsoft.com...
>