Re: Cluster Set up Question
- From: "Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx>
- Date: Wed, 11 Jan 2006 16:13:54 -0500
The SQL Installer is cluster-aware. That is, it handles all the details of
cluster-wide installation. It creates the virtual server and installs the
local binaries on all nodes. It also groups all the cluster resources and
sets the dependencies correctly. Once SQL is running and you are connected,
there is almost no difference in SQL operations between clustered and
non-clustered SQL Servers. You end up connecting to a virtual SQL Server
instance that looks identical regardless of which node is actually hosting
it at the moment.
Here is an excellent overview of SQL failover clustering that you may find
helpful:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"mvp" <mvp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:95A55E02-1BCB-47E1-9458-E01080486B3D@xxxxxxxxxxxxxxxx
> Thanks Geoff.
> So From your reply, I understand that i will have to install SQL SERVER
> 2000
> on both the windows 2003 server.
>
> I have following questions.
>
> 1) After installing SQL SERVER on both the windows m/c, When i create
> database on both the machine, Would i have to mentioned same Data files
> and
> Transaction Log Path ( Because we will have storage will be in SAN), when
> i
> create DB ?
> 2) For example if i create one table in the FinDB of on ServerA and then
> if
> i go to FinDB of ServerB, I will see that table there too, if i will have
> Datafiles and Transaction Log Path are same for both the servers ?
>
> "Geoff N. Hiten" wrote:
>
>> A cluster consists of two machines and a storage system that is
>> physically
>> connected to both systems. The Cluster software arbitrates ownership of
>> the
>> disk resource so that only one server can access it at a time. The
>> cluster
>> software also monitor the sql instance on the active host node for
>> failure.
>> If the first node fails, ownership of the SQL instance and the
>> corresponding
>> disk resource is transferred to the other node. From the outside, it
>> looks
>> like the SQL Server stopped and restarted.
>>
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "mvp" <mvp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@xxxxxxxxxxxxxxxx
>> > Hello,
>> > We are implementing clustering (Active/Passive) in our Production
>> > environment.
>> > So we will have two windows server 2003 for SQL SERVER. (ProdDbServer1
>> > and
>> > ProdDbServer2)
>> > I will install SQL Server on both the machine and i will create my
>> > database
>> > (FinDB)
>> > on both the machine's SQL SERVER with all the tables,store procs,
>> > functions
>> > etc.
>> >
>> > So lets say if my Active Server is in action and accepting all the OLTP
>> > transaction
>> > and for some reason if it goes fail...How can passive server can take
>> > over,
>> > how
>> > passive server can be at the same point of the fail of active server ?
>> >
>> > Bacically how both the Database will be in sink with each other ?
>> >
>> > Pls help me
>>
>>
>>
.
- References:
- Re: Cluster Set up Question
- From: Geoff N. Hiten
- Re: Cluster Set up Question
- Prev by Date: Re: Cluster Set up Question
- Next by Date: Re: Clustering for Performance
- Previous by thread: Re: Cluster Set up Question
- Next by thread: Re: Cluster Set up Question
- Index(es):
Relevant Pages
|