SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Simple databases / warm failover


Simple databases / warm failover

Author
Message
mikeg 31960
mikeg 31960
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 79
I have two database servers on the domain. One for production databases and the other is for warm failover.
And although this sounds like a perfect scenario for log shipping, the rub is that our databases are to remain in Simple mode.
Can you envision any other automated technique to keep Simple databases nearly aligned?
Steve Jones
Steve Jones
SSC Guru
SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)

Group: Administrators
Points: 64407 Visits: 19117
clustering or replication.

Both will suck for different reasons, but those are your options. Personally I'd lean replication if you don't have too many tables and the workload isn't too high.

You could also look at SAN snapshotting regularly if your hardware can do that.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
mikeg 31960
mikeg 31960
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 79
Thanks for the reply.
Can replication be configured if the databases are in simple mode?
Doesn't the nature of replication demand they be in full?
If not, can you give some more background on replication with simple databases?
sqlmunkee
sqlmunkee
Mr or Mrs. 500
Mr or Mrs. 500 (511 reputation)Mr or Mrs. 500 (511 reputation)Mr or Mrs. 500 (511 reputation)Mr or Mrs. 500 (511 reputation)Mr or Mrs. 500 (511 reputation)Mr or Mrs. 500 (511 reputation)Mr or Mrs. 500 (511 reputation)Mr or Mrs. 500 (511 reputation)

Group: General Forum Members
Points: 511 Visits: 286
What's the purpose of the warm standby ? Clustering may be your best bet if it's to protect against hardware failure, but I can't see how you could protect against data loss without a transaction log backup of some type ( be that mirroring / log shipping), which would mean your database can't be in 'simple' recovery.

sqlmunkee
Bringing joy and happiness via SQL Server since 1998
mikeg 31960
mikeg 31960
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 79
Some more background.
I am hosting an application out of datacenter out east and if it goes down, we'll merely redirect things so app hits the datacenter out west.

The nature of our data is fairly static. It is hardly transactional.
Data is loaded a couple times a day from raw source files. Copies of those source files are sent to the out west data center and also imported there to keep the gigantic fact databases sync'd up. Call that the "log" ship. Smile

Where I need help are a couple other databases I use for system control stuff (like a logging database) need to stay up to date, too. They are simple, and aren't populated from raw source files. Perhaps the best solution is to change these couple others to Full and manage things with log shipping.

What are your thoughts?
Steve Jones
Steve Jones
SSC Guru
SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)

Group: Administrators
Points: 64407 Visits: 19117
Replication works with any recovery model. The issue is that the log cannot clear until the changes are out to the subscriber. This means that your simple mode db log can grow if your subscriber can't receive changes.

Given your description, with smaller databases you want to keep up to date, I'd switch them to full and use log shipping. Way less administration than replication and you can manually get things synced up if you need to.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search