Sql server复制问题 [英] Sql server replication problem

问题描述

您好，

我有一个阶段服务器数据库，其中包含20个表。这些要从此服务器传输到另一台服务器，比如生产服务器。以前，我们的dba是复制的，他们已安排每小时和每日快照复制，因此每小时和每天创建一个具有唯一名称的文件夹。是否可以使用相同的名称进行复制，以便我们可以用新创建的传入文件替换传出文件？

我们现在遇到的问题是数据检索延迟10分钟（意味着数据）在我们的申请表上显示空白。这种情况每天都会发生在一个特定的时间点。根据我们的分析，我们得出结论，在从阶段复制到生产时，数据正在删除并在生产服务器中添加新数据。在此会话期间，应用程序可能会延迟显示记录或快照进程丢弃所有对象并重新创建和重新填充表。

如果这是实际情况，是否有其他方法可以解决这个问题，以便数据不会影响应用程序？如果没有，这将是什么原因和解决方案？

请帮助。

谢谢



< b>我尝试了什么：



当我读到与本文相关的一些论坛时，更多的dba有问题，比如

如何在快照复制后从分发服务器中删除旧文件夹？

因为，每日新鲜数据都添加了唯一的名称，因此新的数据不能被旧的替换，因此它将创建它的副本。我开始知道旧的将自动删除，因为我们设置@max_distretention具有指定的值。

Hi There,
I have one stage server database in which consists of 20 tables. These to be transferred from this server to another server, say to production server. Previously, our dba’s are replicated those and they have scheduled hourly and daily snapshots replication, so every hour and daily a folder is created with unique name. Is it possible to replicate with same name, so that we can replace the outgoing file with the newly created incoming one?
The problem we have right now is a 10 min delay in the data retrieval (means data is showing blank) on our application. This is happening daily in one particular point of time. As per our analysis we came to a conclusion that while replicating from stage to production, the data is deleting and adding a new one in the production server. During this session, the application might be delaying to display the records or the snapshot process dropping all objects and recreating and repopulating the tables.
If this will be the actual case, is there any alternative to overcome this issue, so that data should not affect the application? If not, what will be the reason and solution for this?
Please help.
Thanks

What I have tried:

As I read some forums related to this article, more dba’s have the problems such as
How to delete the old folder from distributor after snapshot replication?
Because, the daily fresh data is added with unique name, so that the new one cannot be replaced with old one, hence it will create a copy of it. And I came to know that the old one will delete automatically as we set the @max_distretention with a specified value.

推荐答案

我从上面了解你的评论..为什么不去Trasational Replication。

此方法记录将在目标数据库中删除（一次性全部），而不是根据发布者数据库执行的操作添加/删除。希望这个mtd能适用于您的案例..

Hi,

As i understood from above your comments.. Why not you go for Trasational Replication.
This Method records will deleted(All at once) in destination database, instead of this it will add/delete based the action performed at publisher database. Hope this mtd will work on your case..

这篇关于Sql server复制问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！