• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

How would you create redundant SQL?

M

marley1

Supreme [H]ardness
Joined
Jul 18, 2000
Messages
5,447
I have a client that has 2 servers.

Server1 - AD, DNS, DHCP, File, SQL for a contracting program (Bid2Win)
Server2 - blank

I am going to be making server2 a secondary ad, dns, and file replication(haven't looked into this much but probably DFS or whatnot).

My question is how can I make it a redundant SQL so if server1 does crash it wouldn't even be noticed.

Both machines will be Server 2003 Standard R2 and the version of SQL is Microsoft SQL SERVER DESKTOP ENGINE.

Is there anyway to do the failover for the SQL? I mean sure worse comes to worse server crashes, I can connect and just install the software to get them going.

Thanks!
 
Yes, you can setup redundant SQL. No, it won't be easy, and probably not possible with the desktop engine version.

In the grand scheme of things, it's better for a client of this size to expect downtime when something fails. You start getting fancy with the backend, and things get more and more complicated to support ( which makes sense for larger places ).
 
sounds good, thats what i figured.

i think we are adding a second hard drive and raid 1 card and then just gonna set it up as a secondary domain, file replication, dns. they already have the server hardware, just need software
 
I don't think you can do redundant SQL with the desktop engine however what you could do to give you some sort of a "go back" option would be to setup a nightly complete backup of the DB then copy it to the other server, that way in a "worst case" scenario where you primary system completely dies you at least have something to bring back up and get back to work on.
 
I agree with the prior poster. At work, we dup SQL Server and SQL Anywhere databases from one server to anothe rjust in case of problems. This is done by scripts that run overnight.
 
There are some down and drity way to do it for a setup that small. Failover clustering requires two servers running Server 2003 Enterrpise w/ full versions of sql.

You could point your applications that user the sql database to a Hostname you manually setup in DNS. Then script the replication of the database to the 2nd server. that way if server 1 fails you can update the IP for that A Host and point it to server 2.


Just remember.... Just because it can be done. Doesn't mean it should ;)
 
Yes, it can be done - check this out:

http://support.microsoft.com/kb/324992

Simply set up transactional replication (ie every transaction on SQL Server 1 gets replicated to SQL Server 2). The trick is getting it to fail over nicely....probably the best way to do that is to set your second server up as a BDC (or whatever the terminology is in AD) and have it run as secondary DNS in your DHCP zone, and then have the SQL hostname point at the second server instead of the first.
 
You must log in or register to reply here.
Back
Top