• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 186
  • Last Modified:

SQL 2008 cluster with out joing server to Active Directory

Can I create the SQL 2008 cluster without joining  the server to the domain. When I tried to make the win 2008 fail over cluster the win 2008 r2 server asking me to join the server to domain since the cluster setting is stored in the AD. I do not have AD in this case how can I do the SQL 2008 cluster.If possible give me the step by step guide with pic.
0
jobby1
Asked:
jobby1
  • 2
1 Solution
 
Krzysztof PytkoActive Directory EngineerCommented:
You need to have Active Directory environment if you wish to install SQL failover cluster. This is required because this kind of cluster relies on AD and DNS server.

So, before that, you need to establish AD environment. Do you have a serer for that? If so, you may follow an article on my blog, how to create forest root domain at
http://kpytko.wordpress.com/2011/09/02/configuring-a-forest-root-domain-on-windows-server-2008-r2/

then you will be able to create SQL failover cluster.

Regards,
Krzysztof
0
 
MrAliCommented:
Windows and SQL Server have a core requirement of AD and there isn't some way to hack around that.  However, have you considered database mirroring?  Mirroring is a better solution a lot of times than clustering anyways, and provides safety for disk failure whereas clustering does not.  Clustering also requires enterprise Windows Server software which is very expensive.
0
 
jobby1Author Commented:
MrAli:

How can I do database mirroring. Can mirroring support fail over of the db server in case of failure of one DB server.
0
 
MrAliCommented:
Hi Jobby,

Mirroring can provide application level failover actually, it's a very good piece of technology.  Just like clustering, it takes some setting up to do but a witness server can see that one is down, and immediately move you to the other node.  You have 2 types of mirroring, synchronous and asynchronous.  If you don't have a full time DBA on hand, you'll want to go Asynch.  Synch mirroring requires the transaction to commit on the mirrored copy first, before applying to the primary and if something goes down, your primary will hang up.  Asynch doesn't require for the transaction to commit on the failover, but you will lose 'in flight' transactions when it fails over, basically the last transaction or so will be lost, but nothing else.  This is a good start here:
http://blogs.msdn.com/b/suhde/archive/2009/07/13/step-by-step-guide-to-configure-database-mirroring-between-sql-server-instances-in-a-workgroup.aspx

good video here:
http://www.sqlserver-training.com/how-to-set-up-database-mirroring-in-sql-server-2008-video/-

let us know if you need more help after reviewing it.  Good luck!  
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now