Re: Can I pick your brains for a second? transferring a large database problem

No. Unfortunately the data that I would like to compare it to is in one location.

I MIGHT be able to execute the query there then only pump back the updates........ HUmmm.... I COULD execute it on the server (source) and not the server(destination) :)

THANKS MUCH!!

You have been a lifesaver!!! I'll try that tomorrow during the day and see how this plays out.

<Myles.Matheson@xxxxxxxxx> wrote in message news:1118278616.128839.55570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 
Good question, I have read something similar around joining tables.

To be honest I try and avoid a pull process from any source system
(although is may not be possible in all cases). I prefer the source to
push the required files (data extracts) to the data warehouse.

This way if the source system goes down the data warehouse is not
affected and like wise if the DW server goes down the source server is
not affected.

In your case can you create the audit table on the source system? This
way you will process everything on the source server and only pull back
the new, updated records. To make this work DTS would call the Store
procedures from a SQL Execute Task or in the data pump task. This would
stop you from using Linked Servers.

Myles


.

Loading