Question : Adding a second SQL 2005 Server for redundancy

Hello. We are running a SQL 2005 Standard edition on a Windows Server 2003 R2 Enterprise Edition system. This system has been running for the last two years, and the amount of databases has grown significantly. We are considering the addition of a second server for redundancy, and would like some insight on the best way to do this. I see two possible options. One is to create a cluster with the two servers. The other is to add a second server, and distribute the DBs between the two servers. So my questions are, what is the best option, considering our current setup? If we have to go with the second option, is there a way to copy the DBs from server A to server B using SQL management jobs?

Also, the existing server has enough hardware specs, so performance is not an issue at this time.

Answer : Adding a second SQL 2005 Server for redundancy

To create a cluster you have to have a storage sollution which supports clustering, so the same disks are available to both servers. Not all storage sollutions are certified by microsoft for use in clustering. So if you have a share storagesollution this option is open.  
Secondly, to support clustering, you have to have the Enterprise edition of SQL server 2005.
It seems this is not an option, unless you want to invest some money.

The second sollution, you can distribute different db's to each server. Database partitioning is also not an option (splitting one large db accross servers) because again this is a sql server enterprise edition feature.
So if you put different databases on different servers you could do log-shipping and keep the databases quasi in sync. But you will loose much of the performance gain, because both servers will have to do the same tasks.  Maybe you could run different databases on each server and keep them in sync once a day. You could then go forth from there or take the appropriate actions of transfering the log upon failure of one server, and updating the second and this only when needed.

Random Solutions  
 
programming4us programming4us