SQL 2005的客户端提供程序 [英] Client Provider for SQL 2005

查看:79
本文介绍了SQL 2005的客户端提供程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我希望利用Microsoft Synch Framework在两个SQL 2005数据库之间同步数据。即服务器和客户端都是SQL 2005数据库。

似乎还没有适用于SQL 2005的现成客户端提供程序来自Microsoft和"演练:创建同步提供程序"的文档在 http://msdn2.microsoft.com/hi-in/library/bb902809(EN-US,SQL.100)的.aspx 似乎不再存在。

It seems there is not yet an off-the-shelf Client provider for SQL 2005 available from Microsoft and the documention for "Walkthrough: Creating a Synchronization Provider" at http://msdn2.microsoft.com/hi-in/library/bb902809(en-us,SQL.100).aspx no longer seems to exist.

是否真的出现了SQL CE唯一的客户端提供商?

Is it really the case that the only client provider out there is for SQL CE?

我现在正在努力实现允许这种设置的对等实现(SQL2005 - > SQL2005)。但是,由于只有2个对等体,并且任何同步只会在一个已知方向上发生,这似乎有点过分。

I am now moving my efforts to implementing a peer-to-peer implementation which will allow this set up (SQL2005 -> SQL2005). However, as there will only ever be 2 peers, and any synchronisation will only ever occur in one known direction, this seems to be overkill.

任何想法都表示赞赏。

Any thoughts appreciated.

问候,

杰克

推荐答案

嗨杰克,

我想指出的第一件事是基于你告诉我们的内容,我认为你可能想要研究 ADO.NET的同步服务(这是Microsoft Sync的一个组件)框架)因为这是针对基于离线和协作(P2P)的解决方案启用ADO.NET的数据库之间启用同步的组件。

The first thing I would like to point out is that based on what you have told us, I think you will likely want to look into Sync Services for ADO.NET (which is a component of the Microsoft Sync Framework) as this is the component targeted at enabling synchronization between ADO.NET enabled databases for both offline and collaboration (P2P) based solutions. 

其次,客户端提供商将允许您定位SQL 2005,但我不得不承认我们有点在提供如何做到这一点的良好样本方面落后了。我可以告诉你,我们正在努力完成这个样本并将尽快发布到我们的博客上,请关注我们的同步博客了解更新。

Secondly, the client provider will allow you to target SQL 2005 but I have to admit that we are a bit behind in providing a good sample on how to do this.  I can tell you that we are working on completing this sample and will post it to our blog as soon as possible,  Please keep an eye on our Synchronization Blog for updates.

第三,您声明您正在计划实施P2P,但看起来您只是计划支持两个数据库。您是否考虑最终添加更多需要P2P支持的SQL Server?如果没有,您可以真实地使用传统的离线(Hub和Spoke)同步来支持您的环境,这可以稍微简单地实现P2P。请记住,支持P2P使事情变得更复杂,因为诸如保留旧的变更跟踪信息以支持新的同行等问题。

Thirdly, you state that you are planning on implementing P2P, yet it looks as though you are only planning on supporting two database.  Are you thinking of eventually adding more SQL Servers which would require P2P support?  If not, you can realistically use traditional Offline (Hub and Spoke) synchronization to support your environment which can be slightly simpler to implement then P2P.  Keep in mind supporting P2P makes things a little more complicated due to issues such as keeping old change tracking information to support new Peers. 

我希望这会有所帮助。

Liam


这篇关于SQL 2005的客户端提供程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆