Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
amihshah10
Starting Member
1 Post |
Posted - 2010-12-29 : 03:38:18
|
Hi!I have 2 different database (A and B) in a sql server 2008. Databse A has around 100 tables out of which i want to synchronize 15 tables from database A to database B. So if any addition/deletion/updation happens on those 15 tables then those entries should be updated on database B. But here the challenge is i will have different Primary key data in source and target, i.e. lets say one row is added to Database A-Table A with pk value as 10 then when i will copy that row to Database B- Table A, PK might be auto generated and can have any value other than 10.Same way i need to keep track of update and delete.ssis will help me in this scenario?Ami Shah |
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2010-12-29 : 03:55:13
|
It's not an ssis issue - it might help but your problem is the requirements definition.You say you want to synchronise tables but the destination can have a different PK to the source. What do you mean by synchronise? Also means that referential integrity will not be maintained in the destination (probably reduces the value of the database).First of all define what you want to do in detail then you can decide on the best means of doing it. Don't try to decide on a method then try to find requirements that suit it.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|