Last post Apr 26, 2011 06:14 AM by r_nassabeh
Apr 13, 2011 11:09 AM|mrblitz|LINK
I am looking for a design pattern / architectural recommendation for my problem:
I need to sync two databases (Master/Detail, just one way). The master db I will connect using ODBC and I will have full control over the detail db, which will be running on SQL2005 and on .NET 3.5 (Upgrades planned but no schedule yet.).
I don't need real time syncronization, 1 sync every two hours would be sufficient.
Any hints/suggestions are much appreciated!
Apr 14, 2011 09:29 AM|abhisheks|LINK
why not create SSIS package that runs every 2 hours ?
Apr 20, 2011 09:28 PM|atconway|LINK
I need to sync two databases (Master/Detail, just one way). The
I would not recommend writing code from scratch to preform this operation. There are plenty of utilities/functions within SQL Server to handle such needs. I recomend you seek out the advice of the SQL Server forums for questions like this:
SQL Server, SQL Server Express, and SQL Compact Edition:
Apr 26, 2011 06:07 AM|anujtripathi|LINK
Woah ! We have synchronization framework for this..
Hope this will help
Apr 26, 2011 06:14 AM|r_nassabeh|LINK
You have three diffrent ways to sync your databases.
1- Writing a solution from scratch, which I do not recommend unless you have VERY VERY special requirements that can not be met with other technologies.
2- Using SQL Server Replication. It is automatic, it performs change tracking, it's nearly realtime but have some limitations. Use this option if you just need to transfer data and do not need to perform any data manipulation between two servers.
3- Use SQL Server Integration Services (SSIS) to do the job. It is very customizable and provides most data manipulation actions out of the box but you need to do change tracking yourself (if needed).
Choosing the best solution is up to you. Just consider your specific requirements and choose the right method accordingly.