April 15, 2013 at 11:54 pm
Hi All,
if my windows in clustering mode, is my database in SQL server also in Clustering? or I will have to do it for SQL server.
Actually we have huge database for client. Now we want to cluster for windows and for Database. Now my question is will we have to do 2 different clustering one for windows and one for database...or just clustering for only windows?
Please reply...
April 16, 2013 at 12:18 am
A well formed Windows cluster is a pre requisite for a clustered sql server instance.
First you must cluster the Windows operating system on the computer nodes. Once this is done you then have to install the sql server instance as a cluster aware application.
If you're going to be using Veritas Cluster Server or HP Polyserve instead of Windows Server Failover Cluster, then the process is somewhat more complicated.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 16, 2013 at 7:34 pm
niladri.primalink (4/15/2013)
Hi All,if my windows in clustering mode, is my database in SQL server also in Clustering? or I will have to do it for SQL server.
Actually we have huge database for client. Now we want to cluster for windows and for Database. Now my question is will we have to do 2 different clustering one for windows and one for database...or just clustering for only windows?
Please reply...
-You install MS Clustering services 1st (two node at min. You can actually with one, but makes no sense)
-You install MS-SQL as a failover instance. Then it will run as a cluster aware SQL installation
If you do not require geographical dispersion, MS Clustering should work. Keep in mind that if the same datacenter or SAN fails, or both servers, the whole Cluster goes down.
If you need geographical dispersion, let's say Houston and Dallas, then you may need a software like Veritas. In my experience, most companies do not require it, unless the database is MC and extremely important for the business.
So, two steps... one Windows Cluster..... one SQL failover (at least) after installing the Cluster Service or make it run ... also, you need a SAN (common storage) for your Cluster.
You can start learning more, with a very simple link or resource like this one: Windows Clustering
April 16, 2013 at 7:36 pm
Perry Whittle (4/16/2013)
If you're going to be using Veritas Cluster Server or HP Polyserve instead of Windows Server Failover Cluster, then the process is somewhat more complicated.
Wow, never heard of that HP service or software. Any link or resource? ...
April 16, 2013 at 10:44 pm
Google??
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 17, 2013 at 2:33 am
HP Polyserve is not just a Cluster software but it does provide a well consolidation feature where 15-20 SQL server instances can be well managed on a well configured server (number of instances can be more on one server but this is just a well estimated guess as per my experience). However, getting the support for HP Polyserve is not so easy and not sure the future of product as I had heard that HP is working on newer similar product and the Polyserve is almost to an end of life!
You can get more information on HP's site.
Thanks,
Vikas
April 17, 2013 at 2:52 am
If you already know SQL Server but do not know SQL Clustering then you have a lot of learning to do. SQL Clustering introduces new and interesting ways to trash your data if you get things wrong.
My advice is to start with a SQL Cluster in your development environment, and spent 2 or 3 weeks trying to break it and then fixing the problems. You should then have the skills you need to troubleshoot problems you might get in Production.
This assumes that Clustering is the right answer for your problem. SQL Clustering gives high availability but not high resilience. There are many single points of failure in SQL Clustering, so if you want high resilience then you need a different solution. Have you considered database mirroring or Peer to Peer replication - both of these options give you high resilience as wel as high availability.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply