I have a peculiar problem here. I have a table MasterDB.Employee and its being replicated in ReplicationDB.Employee.
I have a .Net screen which has boxes to key in information about an employee and when they hit save, it gets inserted into the MasterDB.Employee table and it takes about let's say 30 secs for it to get to ReplicationDB.Employee. As soon as they save and exit out it shows a screen with all employees along with their information. The storedproc that loads the employees is only on the ReplicationDB because it has more information than what's on MasterDB. So as soon as one saves and exits out of that screen, that employee is not loaded on the list since there is a latency.
I need some help here on how to tackle this issue.