Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12345»»»

Creating A SQL Server 2008\2008 R2 Failover Cluster Expand / Collapse
Author
Message
Posted Tuesday, January 18, 2011 9:37 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:56 PM
Points: 6,365, Visits: 13,695
Comments posted to this topic are about the item Creating A SQL Server 2008\2008 R2 Failover Cluster

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1049786
Posted Wednesday, January 19, 2011 3:16 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 2:34 PM
Points: 1,458, Visits: 3,003
If you're smart you'll make use of the new slipstream features and integrate the Service Pack and\or Cumulative Update to decrease the time taken to deploy your new SQL Server instance(s).


This is a must if you want to alter the collation from the US default. Otherwise you may need to rebuild the master database to alter the collation, not sure if this is still true in R2, but it certainly was before R2.


Facts are stubborn things, but statistics are more pliable - Mark Twain
Carolyn
SQLServerSpecialists
Post #1049879
Posted Wednesday, January 19, 2011 3:19 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, September 15, 2014 8:08 AM
Points: 51, Visits: 162
We're undergoing an enterprise consolidation and virtualisation project at the moment, and I currently have an external consultant proposing to replace our physical, clustered SQL Servers, with non-clustered VM's where the high availability is provided by VMWare HA.

Does anyone have a view on this? Any serious pitfalls / constraints to take into consideration?

Thanks in advance.
Reuben
Post #1049880
Posted Wednesday, January 19, 2011 5:38 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, November 30, 2011 4:32 PM
Points: 16, Visits: 158
Hello,

Can I receive a copy of the VMWare Server\SQL Server 2008 install.

Currently our site has a clustered 2008 R2 sql server instal built by a third party vendor and we are experencing huge network problems. The cluster has two nodes (SQL1,SQL2) with SQL2 being the active node and SQL1 being the failover node. We are recieving the following erros and user are unable to access the database at certain times of the day. We are at the mercy of the vendor o help us resolve the issue however they are not providing the proper resources to help us resolve the problem.
I would like to evaluate the Windows Server 2008 R2 64 bit and see if the installation has been performed correctly. Any help or guidance on this situation would be great.

Cluster network name resource 'SQL Network Name (XXXXXXSQL)' failed registration of one or more associated DNS name(s) for the following reason:
DNS signature failed to verify..
Post #1049961
Posted Wednesday, January 19, 2011 5:51 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 15, 2014 8:39 AM
Points: 1, Visits: 242

Nice article, however, I would include some reference to the MSDTC and SPN records, for instance:

"If you are installing only the Database Engine, the MSDTC cluster resource is not required. If you are installing the Database Engine and SSIS, Workstation Components, or if you will use distributed transactions, you must install MSDTC. Note that MSDTC is not required for Analysis Services-only instances."

Best regards ...

_Ak!

Post #1049973
Posted Wednesday, January 19, 2011 6:44 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, January 22, 2014 6:38 AM
Points: 104, Visits: 305
What edition of Windows & SQL does this article relate to? I would assume Windows Enterprise due to limitations on memory with Standard edition. Will this 3 node solution work with Standard SQL or does it require Enterprise?
Post #1050008
Posted Wednesday, January 19, 2011 7:30 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:56 PM
Points: 6,365, Visits: 13,695
BigSam (1/19/2011)
What edition of Windows & SQL does this article relate to? I would assume Windows Enterprise due to limitations on memory with Standard edition. Will this 3 node solution work with Standard SQL or does it require Enterprise?

Hi

as clustering requires a minimum of Enterprise for the operating system, I am using either Windows 2003 R2 Enterprise or Windows 2008 R2 Enterprise. SQL Server Standard edition supports 2 node clustering so this will be suitable for your test environment as you are only deploying each instance to 2 nodes.

INST1 nodes A and C
INST2 nodes B and C


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1050058
Posted Wednesday, January 19, 2011 7:33 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Yesterday @ 7:48 AM
Points: 1, Visits: 58
Can I get the tutorial from you, please.

Thanks!
Post #1050060
Posted Wednesday, January 19, 2011 7:43 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 11:08 AM
Points: 5,992, Visits: 12,941
reuben.anderson (1/19/2011)
We're undergoing an enterprise consolidation and virtualisation project at the moment, and I currently have an external consultant proposing to replace our physical, clustered SQL Servers, with non-clustered VM's where the high availability is provided by VMWare HA.

Does anyone have a view on this? Any serious pitfalls / constraints to take into consideration?

Thanks in advance.
Reuben


I believe that would mean you only have failover at the host level, not individual virtual servers.


---------------------------------------------------------------------

Post #1050067
Posted Wednesday, January 19, 2011 7:44 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 11:08 AM
Points: 5,992, Visits: 12,941
Perry,

maybe it is taken as read but it should be mentioned another drive would be needed to install SQL application files to (i.e. the instance root directory) and this would not be a cluster resource.

C drive could be used for this but a drive for the purpose would be usual.

thanks for putting the article together. Any plans for an article on clustering other SQL components (mainly SSIS and SSRS)


---------------------------------------------------------------------

Post #1050068
« Prev Topic | Next Topic »

Add to briefcase 12345»»»

Permissions Expand / Collapse