I am not a database administrator; however, my small company uses SQL Server for the project we are working on. The same instance of SQL Server has the MS Great Plains database (Dynamics GP), because we transfer data back and forth between the two databases (mainly the scribe process, which receives our data and transfers it to the GP).
We use database replication (snapshot) as a means of synchronizing our development and development environment (and soon DR). Currently, his selection is repeated every three hours during the main working hours - mainly in order to extend production and development for us while we work.
1) Is this done correctly? Is there a better way? 2) Does this have voltage on the server or SQL Server? Is this a possible cause of problems with the GP database since they are on the same server and instance? 3) Replication occurs only in the non GP database - should this not affect the GP database? [/ P>
Our database should remain fairly small. When I take a snapshot, I understand that tables are locked during replication. Do locks persist until all replication is complete or are not downloaded after they are completed as the process continues?
source
share