I work with a decent size SQL Server footprint with an ever increasing set of customers that are using replication. After looking at some conflicts that our clients are having with their replication topologies, my coworker asked me if there was a "simple" way for us to offer a "conflict resolution" handler that could be used as a "service" for our growing list of customers that use the varying types of replication models.
I found out about the "business logic handler" and the "COM-based custom resolver" on Microsoft's website and read a few blogs. I'm not a C# expert, I dabble, but I'm certainly no expert. I'm pretty decent with PowerShell, and its fair to say that the rest of my SQL team is similarly capable.
So... My question is about feasibility and skillset.
1. For a C# expert, what is the level of difficulty/amount of time to create your own handler based on the existing .NET documentation on Microsoft's websites, and some blogs?
2. For a DBA of our skillset, what is the level of difficulty/amount of time to create your own handler based on the existing .NET documentation on Microsoft's websites, and some blogs?
3. Are the SQL Server Stored procedure options full featured, or are the C# the better alternative?
4. How feasible is it to "hand off" these handlers to a non DBA team set of customers?
Thanks for your consideration,
Keith