I'm trying to find a better solution when publishing data to a remote table.
So we have Server A and Server B. Server A holds a master table which should be replicated to Server B.
Currently, we have this pretty chaotic stored procedure that runs every minute or so. It locates any changes and inserts them into a temporary table on Server B. Once loaded, it inserts new records or updates existing records from this temp table (The table is hit constantly and we want to limit any for of lock).
We don't have a DBA currently so I'm trying my best (I'm just a web developer) to figure out better solutions that could scale in the future.
Note: We have a couple dozen stored procedures that are like this.