July 12, 2007 at 5:31 am
am using Microsoft Dynamics Great Plain with SQL Server 2000. I am looking for solution by which my 1 database can sync with other database with only new updated records either(Insert, Update and Delete). I also thru from Microsoft define replication process but this will replace my existing record where i need only updated record. If someone help me out i'll grateful to him/her.
Regards
Amin
July 13, 2007 at 5:58 am
What about logshipping or db mirroring?
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 13, 2007 at 6:27 am
Dear Kumar
If we use log ship or mirroring the server mode should be stand by but in my scenario both server available for data enter at their site.
Regards
July 13, 2007 at 7:15 am
hi, you want users to use both ur headoffice and factorys prod servers i.e update simultaneously in any 1 of those depending on the availability....and later jus want to sync both servers........i think it is possible with MERGE replication not sure about it..........but with log shipping its not possible...as it can be used only as a standby server......if your prod server @headoffice is down all your users can conect to the standby server which has the exact replica of your db from production(head office)........so that you can minimize the downtime......also with mirroring the db will be in norecovery mode...you can modify it.......
[font="Verdana"]- Deepak[/font]
July 14, 2007 at 12:12 am
Dear Deepak
Well somehow you are saying right, but my requirement is users are entering at both production server but not like standby as factory users only able to enter data in factory server and head office users only able to enter data in head office server. At some time a utility or tool run and sync both end servers with each other.
July 16, 2007 at 2:30 am
If you want to have a tool then try using data compare tool to sync data between the resources.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 16, 2007 at 9:53 am
Amin,
I think that your first step would be to check with the software manufacturer to see if they will support having two databases. I can't recall any version of GP that is designed to work in that environment, but that doesn't mean it can't be done.
I've worked with GP before, and I know that there are LOTS of tables. You will have to do a great deal of engineering to come up with the correct order in which to make the data changes because of the DRI. There is the added problem of dealing with the identity columns (called DEX_ROW_ID) that are not neccesarily primary keys, but they are present and probably need to be unique between both databases.
If you are careful about limiting the scope of the replication, then you might be able to minimize the amount of work you are going to have to do.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply