On Fri, Jul 6, 2012 at 10:02 PM, Vincent Teachout <[email protected]> wrote: > > Uhm, imagine a DB the size of a certain Texas client (It's not). It's > even larger. IIRC, I once tried to script the Texas client and MS > struggled and then told me to jump in the lake. >
Well, that's a pretty poor tool you're using, or the OS needs a kick. I work with multi-gig databases and text files all the time. Isn't the backup (nearly) just as large? Hmmm. The scripting tool has an option, after you've selected all but the one file, to generate a separate file "for each object" -- in this case tables. That might solve your problem. The obvious kludge is to duplicate a copy of the table you don't want to overwrite, create a full dump backup, restore that, then overwrite the one table with the copy you made. That's ugly, but it ought to get the job done. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4tcpxe_3kno5teatmcessdzcybhtqwuasl1tv4cr-3...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
