SQL Server不同版本之间发布订阅的主意事项
来源:互联网 发布:数据帧 格式 编辑:程序博客网 时间:2024/04/28 08:32
I was asked recently about Replication with different versions of SQL Server i.e. Multiple versions of SQL Server in a Replication topology. Generally, Microsoft supports replication back to two previous versions. We just need to know the rules. Let's take a look.
Including the two previous releases, we can therefore replicate between SQL Server 2008, 2005 and 2000. Of course, certain service packs need to be applied: SQL 2000 has to have SP3 and SQL 2005 needs SP2.
If you do mix versions, you should know that SQL Server takes the lowest common denominator approach. That means that if you have at least one SQL 2000 Subscriber, you are limited to SQL 2000 functionality for replication. When you set up the Publication, the wizard asks you about the levels of SQL Server supported by the subscribers. The more levels you check off, the more you are limiting replication functionality. Obviously, running Publishers, Distributors and Subscribers at the latest release is going to allow the maximum features, but that is not always possible.
One general rule is that the Distributor cannot be an earlier version than the Publisher. Many times the Publisher and Distributor roles are on the same server so this is not an issue. However, if you have a large number of subscribers you may choose to have a separate Distributor server. The Distributor can be a later version or the same, just not earlier.
For Transactional replication, you can mix and match the supported versions as you like between Publishers and Subscribers. The Publisher can be SQL 2000 with SQL 2005 and SQL 2008 Subscribers or a SQL 2008 Publisher with SQL 2008, 2005 and 2000 Subscribers. Just remember the lowest common denominator rule.
Merge replication is a little less flexible: the subscriber needs to be at a version no later than the Publisher. Earlier or the same is fine. For example, a SQL 2008 Publisher with SQL 2008, 2005 and 2000 Subscribers is supported. If you are replicating "down-level" in this way, you will need to be careful with new data types as they will be mapped to compatible data types for the older version. For instance, a data type of Geography in a 2008 Publication will be mapped to a data type of Varbinary(max) in a 2005 Subscription and to a data type of Image in a 2000 Subscription.
New SQL Server 2008 features like Data Compression and Filestream data are supported with replication, as long as the Publisher, Distributor and Subscribers are at the 2008 level. Otherwise replication will not work. This makes sense.
As always the proof is in the testing.
原文来自:http://www.sqlmanager.net/en/articles/1548
- SQL Server不同版本之间发布订阅的主意事项
- Sql Server 订阅发布
- sql server 发布订阅需要注意的
- SQL Server 2008通过发布订阅的方式实现数据库之间的同步操作
- 【重要】ViewPager的主意事项
- PCL+MFC+OpenGL程序发布主意事项
- sql server 订阅和发布
- SQL SERVER发布与订阅
- sql server 2005 发布订阅
- SQL Server + Oracle订阅发布
- SQL SERVER 2000中订阅与发布的具体操作(转)
- SQL Server 2000订阅与发布的具体操作
- SQL Server 2000订阅与发布的具体操作
- [SQL Server]自动监控“发布订阅”的滞后时间(延迟时间)
- SQL Server 2008 R2的发布订阅配置实践
- SQL Server 2008 R2的发布订阅配置实践
- 不同版本的SQL Server之间数据导出导入的方法及性能比较
- 不同版本的SQL Server之间数据导出导入的方法及性能比较
- android获取手机信息以及服务商信息
- 网页css优先级
- JSP自定义标签库
- 一个简要的详细设计的模版
- Hibernate 主键生成策略选择
- SQL Server不同版本之间发布订阅的主意事项
- 如何去评估一个Story的时间?
- 改变自己,改变世界
- Physicists Discover a Whopping 13 New Solutions to Three-Body Problem
- 测试序列下载地址
- VS Installer 多个安装包程序打包安装 .
- 指针和引用的比较小结
- 基于 Jenkins 快速搭建持续集成环境
- Linux下Redis安装详解