January 27, 2016 at 2:08 pm
Any help with this would be greatly appreciated.
Our company spun off a branch that is using a copy of our production database on a remote server. I access this database via remote desktop using an IP address. The problem is keeping the two databases in sync. For our vendors, we are inserting and updating records on the production side and then pushing them over to the remote server.
We have a contacts table and an address table that we are allowing the remote site to add records to and update freely based on their vendor interactions while still trying to push over the production data. Vendors have at least one address and at least one contact record in each table and the contacts table is allowed to have contacts for other entities in addition to vendors (clients). As soon as the remote site enters a new address or new contact, the two data bases are out of sync. I have been wracking my brain to conceptualize a solution and I just can't see it.
As stated above, any help would be greatly appreciated.
January 27, 2016 at 2:10 pm
Take a look at transactional replication. Sounds like it might be a pretty fit for your requirements.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
January 28, 2016 at 5:15 am
To get data moving both directions you're probably looking at Merge Replication. But that requires quite a bit of redesign. You could use transactional replication, but it's a one way process. Another option is to look to the cloud. Move the database storage to somewhere accessible by both parties.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 1, 2016 at 11:08 am
Grant Fritchey (1/28/2016)
To get data moving both directions you're probably looking at Merge Replication. But that requires quite a bit of redesign. You could use transactional replication, but it's a one way process. Another option is to look to the cloud. Move the database storage to somewhere accessible by both parties.
What about Transactional Replication with Updateable Subscribers?
Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising
February 3, 2016 at 3:03 am
Br. Kenneth Igiri (2/1/2016)
Grant Fritchey (1/28/2016)
To get data moving both directions you're probably looking at Merge Replication. But that requires quite a bit of redesign. You could use transactional replication, but it's a one way process. Another option is to look to the cloud. Move the database storage to somewhere accessible by both parties.What about Transactional Replication with Updateable Subscribers?
I wasn't that aware of that one. It's an option.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply