Do you have large text columns or blobs (not even sure how they work) that could explain this?

Or large fragmentation (on the disk).

Lol, those complaints will subside when everything gets put back into ram and recompiled. But that can take a while in a test environement

You might also want to check this out : DBCC DROPCLEANBUFFERS

Those are not to be used on prod environement unless you realllllllllllllly have to

Well you'll have to send me one cause I ain't got it yet.

Need my adress ?

Sorry I have not learned any of that stuff in books.  Only online from this site and a couple articles on other sites.

Have you searched this site's articles on disaster recovery??

Would be a great place to start!

Also do not cross-post.  It makes it much harder to follow the conversation.  Please finish the thread here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=92&messageid=310807

Assuming here... wouldn't it be simpler to just use sql server to import the data monthly from that database using its scheduling capabilities?