Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Brittleness of Replication


The Brittleness of Replication

Author
Message
Steve Jones
Steve Jones
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: Administrators
Points: 41111 Visits: 18870
Comments posted to this topic are about the item The Brittleness of Replication

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Gary Varga
Gary Varga
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10356 Visits: 6350
From the perspective of a developer who occasionally delves into SQL Server I can see that there is a benefit to the stagnant nature of software i.e. I come back after a couple of years with no real SQL Server interaction and most is still familiar.

I am not convinced though that this benefit cannot be realised if the product was no longer stagnant. If the UI remained as slow moving as before but the features were tidied up then it would sometimes require zero changes in the UI (I am including command line etc. here), sometimes a few small ones and occasionally an overhaul. Most people can live with this especially when considering the benefits.

Backward compatibility is already managed on a compatibility level for the SQL Database Engine. Is it time that each subsystem has a different compatibility level? Should we be looking to allow more changes to eventually break backwards compatibility? These changes are not made lightly so should we consider them permanent breaking changes after a particular advertised time span? Do we need something akin to the product support lifecycle for features?

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Steve Jones
Steve Jones
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: Administrators
Points: 41111 Visits: 18870
I'm not looking to break backwards compatibility. I just want improvements and things fixed that don't work well. There's no shortage of those. In replication, tooling has barely advanced, and robustness-wise, it's barely moved. Certainly in other areas tooling could be improved.

However let me also comment on Oracle. They are very backwards compatible. They also suffer security issues because of this. I'm not sure I want complete backwards compatibility. In fact, I like the move from mirroring to AO/AG. While I like mirroring and I think AO/AGs need some work, I am also glad they didn't try to retrofit this and made a new technology.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
lori.nolen
lori.nolen
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 236
Your post came just as I was initializing a replication subscription that has mysteriously been marked inactive and needed to be reinitialized. My company uses replication from servers in remote locations with limited connectivity so when it breaks it is a long process to get is working again. Fortunately this is not a frequent occurrence and the product works as advertised with just a few 'mysterious' events. I have not found a better product for data exporting with a usable user interface that I can get setup within an hour of getting the request. CDC is rather more complicated that I need as is Service Broker which I have used for other projects. I'll continue to use Replication and hope for less 'brittleness' in future upgrades.
Robert.Sterbal
Robert.Sterbal
SSC Veteran
SSC Veteran (235 reputation)SSC Veteran (235 reputation)SSC Veteran (235 reputation)SSC Veteran (235 reputation)SSC Veteran (235 reputation)SSC Veteran (235 reputation)SSC Veteran (235 reputation)SSC Veteran (235 reputation)

Group: General Forum Members
Points: 235 Visits: 2000
I'm always surprised when people don't use replication, especially with reporting problems. Real time data is very often over rated outside of financial markets.
dstinson-1008865
dstinson-1008865
Forum Newbie
Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: General Forum Members
Points: 6 Visits: 92
"Brittleness of Replication" is the best way I've heard of to describe that feature.

Replication is awesome when it works but there seems to be no end of weird circumstances that can bring it crashing down. So much so that in our shop, we have a No-New-Replication policy. We have a lot of replication already and fixing the frequent problems takes way too much of my team's time.

Replication has definitely improved over the years but it is still not robust enough to do the self-healing it should do.
Andrew Peterson
Andrew Peterson
SSC-Addicted
SSC-Addicted (424 reputation)SSC-Addicted (424 reputation)SSC-Addicted (424 reputation)SSC-Addicted (424 reputation)SSC-Addicted (424 reputation)SSC-Addicted (424 reputation)SSC-Addicted (424 reputation)SSC-Addicted (424 reputation)

Group: General Forum Members
Points: 424 Visits: 713
Love "Brittleness of Replication"

With Cassandra, peer to peer replication is a big selling point. And Hadoop has distributing computing. MSSS has had peer to peer replication for quite a long time, but has it advanced?
If they had invested on making peer to peer in sql server solid, it would give it a multi-site HA, DR and scale-out strategy position. No, they follow the cluster approach, and even deprecate mirroring. We can only guess what it would have been.

The more you are prepared, the less you need it.
Brandon J Williams
Brandon J Williams
SSC Rookie
SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)

Group: General Forum Members
Points: 43 Visits: 928
I know this really old guy who once said that replication is only as reliable as the network and hardware it runs on.
David.Poole
David.Poole
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4471 Visits: 3181
No, they follow the cluster approach, and even deprecate mirroring. We can only guess what it would have been.


It seems to have turned into Always-on availability groups.

LinkedIn Profile

Newbie on www.simple-talk.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search