merge for a solution

  • I have a warehouse developed by some consultants. They have one large transaction table that they basically delete last 12 months data, and then reload it every nite (would include new records and changes/updates which rarely ever happen) Kind of ugly. There are about 30 columns in the database. I think for the insert for new records it sounds like a great idea, for the update merge considering that about 25 of the 30 columns could change, would the merge be viable solution.

  • Were they charging by GB Transferred or something?

    There are a million better ways to do it, including the one you mentioned. Merge is great. If you happen to have Record Created/Updated fields in your columns also and can filter it by the last 24 hours (or last successful run if you log results, etc), even better. That's how I end up doing most of my DW/ETL jobs since I like to store those timestamps anyway.

  • No time is becoming an issue the complete delete and reload takes 3 hours and these are flash drives

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply