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.
Submit an article or tip