Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Lumbago
Norsk Yak Master
3271 Posts |
 Posted - 2005-03-15 : 09:08:29
|
During my post-clusterthinking-period (ref: [url]http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=46420[/url]) it crossed my mind that log shipping might come in handy one day for the production environment I'm currently responsible for. However we only have standard edition SQL-server and I can't imagine doing an upgrade in the forseeable future. But why not fake it??My thought: install ms sql server standard edition on one of my two webservers as a cold standby and add it as a linked server to the regular prod-database. Then for every translog backup (every 30 mins right now, would probably have to shorten to every 10 mins or something) I can do a restore of the translog on the linked server and voila! I would have a fully functional database with 10-30 min old data just beggin to be activated should the other baby crash. Then I could just redirect my web requests to the linked server until I can fix the regular prod-server....or not...? What do you guys think  --Lumbago"Real programmers don't document, if it was hard to write it should be hard to understand" |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-03-15 : 09:21:21
|
| I think other people here already do similar using procedures that have been written for the purpose you describe. The only real difference I think is the lack of the monitoring icon.-------Moo. :) |
 |
|
|
|
|
|
"Fake" log shipping