April 13, 2016 at 5:48 am
Hi,
I've SQL Server 2012 STD and SQL Server 2014 STD and i need to implement some kind of DR or HA to it so i can reduce the load from the production server by running some reports and other stored proc and even backup on the DR or HA server (lets call it DR).
the problem is - while the DR is sync with the production server the DR server needs to be available almost instantly.
can it be done?
p.s - if the only chance is by running the SQL server in ENT edition it can be done.
THX
April 13, 2016 at 5:52 am
If you can afford Enterprise Edition, then AlwaysOn Availability Groups might be suitable.
If you need a cheap option that can be unavailable intermittently, then log-shipping might work for you.
April 13, 2016 at 5:58 am
Beatrix Kiddo (4/13/2016)
If you can afford Enterprise Edition, then AlwaysOn Availability Groups might be suitable.If you need a cheap option that can be unavailable intermittently, then log-shipping might work for you.
+1, though I would say 'would' rather than 'might'
---------------------------------------------------------------------
April 13, 2016 at 6:00 am
😀 I'm covering my back.
April 13, 2016 at 6:03 am
Beatrix Kiddo (4/13/2016)
😀 I'm covering my back.
consider it covered
---------------------------------------------------------------------
April 13, 2016 at 6:09 am
thx.
in alwayson i will not suffer from the intermittently break in connections?
April 13, 2016 at 7:48 am
No, assuming your network is ok your data should be continuously available, but if you're looking to offload read-only work to a secondary replica do bear in mind that there are licensing implications. (I don't know the ins and outs, so check with your licensing vendor.)
April 13, 2016 at 2:50 pm
You could look to mirroring. The failover to the secondary won't be instant, at all, but it'll almost do what you're looking for.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 14, 2016 at 3:35 am
only always on is going to provide all the options the op asks for with a DR secondary and a read only secondary, but complicated and expensive, log shipping will do it imperfectly (high latency, interrupted access, no instant failover), but cheaply and simply. You could of course have two log shipped secondaries.
Mirroring I have never thought of as really providing off primary reporting well, and if you use it for DR rather than HA to be robust and instant you really need a third data centre for the witness.
I think the OP needs to think carefully about what he really wants out of this system, what's most important and what he's RTO and RPO are.
DR and HA are not the same thing.
---------------------------------------------------------------------
April 14, 2016 at 11:26 am
Mad-Dog (4/13/2016)
Hi,I've SQL Server 2012 STD and SQL Server 2014 STD and i need to implement some kind of DR or HA to it so i can reduce the load from the production server by running some reports and other stored proc and even backup on the DR or HA server (lets call it DR).
the problem is - while the DR is sync with the production server the DR server needs to be available almost instantly.
can it be done?
p.s - if the only chance is by running the SQL server in ENT edition it can be done.
THX
Does the prod server and the dr server have the same version of sql server or is one 2012 and the other 2014?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply