May 3, 2017 at 10:17 am
I have a database where some of he tables can only be in snapshot (no PK), but I need them to be refreshed at different times.. and do not want to refresh all of these, as they tend to be the tables with the most amount of data in them.
What is the best way to deal with this?
May 3, 2017 at 10:57 am
dwilliscp - Wednesday, May 3, 2017 10:17 AMI have a database where some of he tables can only be in snapshot (no PK), but I need them to be refreshed at different times.. and do not want to refresh all of these, as they tend to be the tables with the most amount of data in them.What is the best way to deal with this?
The best way would be to add primary keys to the tables, since tables should have a PK anyway.
Sue
May 3, 2017 at 2:56 pm
It is a vendor table and they are just pulling in data... into the table.. and you have no single group of columns that can become a key.. and then they delete the rows and re-build.. so there is no way to say a certain row matches across the replication.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply