Friday, March 30, 2012

Pros and Cons

Hi,
I'm writing a proposal for a DR solution for a SQL based application. I've
been looking at clustering, database mirroring, etc. Has anyone come across
any documentation discussing the pro's and cons of the various options
available?
Thanks
Clustering has a distance limitation. Database mirroring is not scalable
beyond 10 or so databases but has no clustering limitation. Clustering
requires expensive hardware. Database Mirroring does not. Database
Mirroring is available on developer and Enterprise and above versions of SQL
Server 2005. Clustering is available on EE versions of SQL 7 and above, and
also on SQL Server Standard in SQL 2005.
Database Mirroring does add some latency to each transaction and as it is
hostbased it works best for low loads on SQL Server. If you have high cpu
utilization your database mirroring solution is likely to fail.
You neglect to mention log shipping and replication in your list of DR
solutions. Both of these word well as well. Log shipping does increase your
exposure to data loss, and is not really scalable beyond a certain size and
number of databases. Replication replicates on an object level and has no
limitation. Failback can be complex.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Hardmandez" <Hardmandez@.discussions.microsoft.com> wrote in message
news:F2DB4016-3D90-4438-B49D-B7B4F76CE03D@.microsoft.com...
> Hi,
> I'm writing a proposal for a DR solution for a SQL based application.
> I've
> been looking at clustering, database mirroring, etc. Has anyone come
> across
> any documentation discussing the pro's and cons of the various options
> available?
> Thanks
>
|||Also check out Stretch Clustering, which can be configured for SQL Server
failover clusters. This can extend the distance limitation mentioned
previously.
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/hasog05.mspx
Anthony Thomas
"Hardmandez" <Hardmandez@.discussions.microsoft.com> wrote in message
news:7E081208-21B9-43D1-A241-A2B15E118575@.microsoft.com...
> Thanks for that Hilary, some good points there. Still to get to log
shipping
> and replication in my proposal. SQL isn't really my area of expertease so
> one more question, does SQL come with replication capabilities out of the
box[vbcol=seagreen]
> or when you talking about replication are you refering to products like
> Neverfail?
> "Hilary Cotter" wrote:
SQL[vbcol=seagreen]
and[vbcol=seagreen]
is[vbcol=seagreen]
cpu[vbcol=seagreen]
your[vbcol=seagreen]
and[vbcol=seagreen]
no[vbcol=seagreen]
|||I also have heard that rumor that Neverfail licenses their replication
from DoubleTake, however, this post from the VP of Product Management
from Neverfail denies that is the case. How long ago did Neverfail
tell you they licensed from DoubleTake? I suppose it may have been
true at one point, but apparently no longer.
[url]http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/375548336a1c2343/f7328f5f4ef3dfc1?lnk=st&q=Neverfail+DoubleTake&rnu m=5&hl=en#f7328f5f4ef3dfc1[/url]
If you ever compare the two products in terms of performance of the
replication, I think you will find that Neverfail's replication is much
more efficient. It is surprising that DoubleTake, being one of the
oldest data replication products around, really is behind everyone else
in terms of performance of their replication IMHO.
David A. Bermingham, MCSE, MCSA:Messaging
Senior Systems Engineer
www.steeleye.com
Hilary Cotter wrote:[vbcol=seagreen]
> Hi David.
> Last time I spoke with Neverfail they told me they licensed their technology
> from Doubletake. You are correct about DFS and Doubletake. My mistake, DFS
> does provide very similar services to Doubletake, and in some cases DFS is a
> better choice than Doubletake (for example in file replication).
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "daveberm" <david.bermingham@.steeleye.com> wrote in message
> news:1161871846.621466.57800@.m7g2000cwm.googlegrou ps.com...

No comments:

Post a Comment