New answers tagged high-availability
0
Quick points:
-Don't setup a separate 'transaction log backup' job outside of the 'log shipping' architecture. Doing so will break log shipping. Let log shipping handle all of your transaction log backups.
-You can use log shipping in 'STANDBY' mode but note that the instance will not be accessible when the server is doing a log restore. You can set the ...
1
What is the best practice in order to have this scenario done?
It depends on how much data you are replicating i.e.
Are you replicating selected columns/tables, entire database (all tables), etc ?
Are both nodes located in the same domain or different domains ?
Are you replicating in same region or cross region (US-UK, etc) ?
I have implemented T-Rep ...
0
It really depends on your overhead and how well you can manage that. If you're not on a super busy system then you should be fine, but maintain a baseline before setting it up and compare the results after to see what the impact was.
Hilary Cotter, one of the authorities of replication, had told me that don't worry about it for having 5 publishers using ...
0
One fairly easy solution (and easy to configure), provided you have the hardware resources, is database mirroring with replication failover.
http://msdn.microsoft.com/en-us/library/ms151799.aspx
As for the best high availability solution? There's clustering, log shipping, syncing, and other options but they might all require more resources. This solution ...
3
Have you considered a Failover Cluster Instance? It'll give you the high availability of the entire instance. And provided you have more than one node in the FCI, you would be able to failover while patching the other server.
There are quite a few details regarding failover clusters, but please see this MSDN reference to get an overview and other how-to ...
0
We just got off the phone with Microsoft about this very same question this morning. According to MS, there is an internal document from the product team stating that this is an unsupported scenario. Which really stinks because we wanted to leverage our existing cluster licensing for SSAS rather than paying for an additional stand alone instance. At any ...
Top 50 recent answers are included
