On Tue, May 15, 2012 at 1:02 PM, Stephen Russell <[email protected]> wrote: > > As a heads up you want to do a backup and shrink the log files > otherwise you may eat up disk space in the log files while the db is > still tiny. > Stephen Russell
Kurt- don't get too concerned with this log file stuff we are talking about for now... but like SR said, turn the darn thing OFF (Simple log mode) when doing your import, then be darn sure to turn it back ON (Full log mode) when you got your data in there and start using it. This log file stuff is DBA admin stuff which you shouldn't have to concern yourself with right now. Learn how to talk to the DB with INSERT, UPDATE, DELETE etc, then worry about the administrivia part... But one thing SR mentioned took me a long time to deal with and that is the size of these log files... your DB can be something like 100k in size, yet your log file is pushing 2 gigs or something.. yes, your DB is being updated, but it's freaky how that thing can get so huge... (not a good sign BTW - means you aren't doing your maintenance or else your DB has got a boatload of updates hitting it). Oh, and ignore the timestamps on the data files - they mean nothing to you, only to SQL... -- Matt Jarvis Eugene, Oregon USA _______________________________________________ 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/capt54raimw6hj2rle0sy0yvojuh7yuaxmbakbtenpwgxheo...@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.
