sql server - Sql Azure Database Mirroring for Traffic Manager Failover -
sql server - Sql Azure Database Mirroring for Traffic Manager Failover -
my objective implement azure traffic manager failover of our web site , databases.
to accomplish this, have 2 identical sql azure databases deployed in different info centres.
the database exhibits 450 tables, 4000 columns, ~8 1000000 records, 3gb in size , written to.
is sql info sync viable alternative implement mirroring or in sql azure terms, bi-directional synchronization between them?my initial concern besides efficiency , cost, , regardless of bi-directional vs one-way, time required setup sql info sync, maintenance overhead when schema evolves , debugging complex schema when sync fails. there added issue of sql info sync still in state of preview.
perhaps one-way geo-replication improve alternative , upon failover, 1 manually reinstate original database synchronized - i'm wondering if such course of study of action ensues database admin?my concern here departure automated failover solution governed traffic manager.
i have concluded sql info sync not ideal maws , sql azure failover strategy.
active geo-replication azure sql database proves improve option.
here points i've considered against sql info sync.
with 450 tables , on 8 1000000 records, database big plenty bring additional complexity , cost setting up, executing , maintaining bi-directional or one-way sql info sync.
sql info sync not appear designed around thought of cross-data centre mirroring of big database. limitations such 100 tables per azure sync group.
setting sql info sync database take time because involves spreading 450 tables across multiple smaller , manageable sync groups well-tuned sync frequencies , each 1 tested ensure synchronization occurs without conflicts. deep analysis of database required right tables grouped avoid foreign key conflicts in target database:
http://www.mssqltips.com/sqlservertip/3062/understanding-sql-data-sync-for-sql-server/
it appears sql info sync not transaction sync model:
sql azure failover / backup strategy web app
sql info sync has been in preview on 2 years , lastly update dec 2012
sql info sync has inherent problems coping big schema. experienced first-hand database schema.
http://social.msdn.microsoft.com/forums/azure/en-us/9c679a74-9a7c-48e7-b4c9-95f6f7cfafd9/sql-azure-data-sync-refresh-schema-not-working
emphasizing first point, two-way replication across info centers tricky , not recommended without intuit knowledge of info , database schema. 1 end creating synchronization loops.
best practice states: include tables required per business needs in sync group; including unnecessary tables can have impact on overall cost on efficiency of synchronization.
http://www.mssqltips.com/sqlservertip/3062/understanding-sql-data-sync-for-sql-server/
sql info sync doubles on tables, creating larger schema adding 450 tables.in regards using active geo-replication azure sql database, upon failover, 1 terminate continuous re-create relationship on active secondary becomes read-write.
from http://msdn.microsoft.com/en-us/library/azure/dn741331.aspx
in case of widespread failure in primary region, might need fail on application secondary region. first, forcefulness terminate continuous re-create relationship on active secondary. after termination, replication stop , transactions not yet replicated primary database never copied active secondary. former active secondary become standalone database. @ point, application can failover former active secondary , resume function. if primary database set read-write, after termination, active secondary set read-write.
as far database sla goes, have next scenarios covered
recovering accidental info corruption or deletion: sql azure premium offers free , automatic point in time restore out of box there no need setup nightly backups blob storage. http://azure.microsoft.com/blog/2014/10/01/azure-sql-database-point-in-time-restore/
monitoring regulatory compliance, understanding database activity , insight discrepancies , anomalies: sql azure offers database auditing on many aspects http://azure.microsoft.com/en-us/documentation/articles/sql-database-auditing-get-started/
cross-region redundancy recover permanent loss of datacenter caused natural disasters, catastrophic human errors, or malicious act: sql azure offers active geo-replication http://msdn.microsoft.com/en-us/library/azure/dn741339.aspx
sql-server azure
Comments
Post a Comment