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 |
iskanda
Starting Member
1 Post |
Posted - 2011-09-20 : 11:41:52
|
Hi All, I’ve got some SQL admin experience but pretty basic SQL programming experience, and I’m a little stuck with what I’ve been asked to do. I’ve got a weekly full backup of purged transactions from a messaging system that I’ve been asked to amalgamate into one, yearly database. The purge happens every 10 days meaning there is an overlap of duplicates within each database backup of 3 days. The end product should be (hopefully) one database of unique messages. My first thought was to create an empty database and start importing on a week by week basis but it's not happening. Whenever I try using the SQL export function in this way, I keep getting errors relating to duplicate primary keys. Obviously, this is 100% logical and correct, but can I create a master database of one years worth of transactions in this way? Can't I just skip the duplicate error? Many thanks for any help you can provideI |
|
|
|
|