On Tue, May 15, 2012 at 2:37 PM, Kurt Wendt <[email protected]> wrote: > Stephen - when you mentioned this Logging thing (which, I'm assuming > that SQL write a Log record for each record inserted - which we really > don't need to do when we are just converting data) - you are referring > only to the conversion process that I attempted to do. Right? > > But, as I mentioned previously - I used the Import/Export Wizard tool of > SQL - and I already got it to work and properly convert the data from > VFP to SQL. Well, actually, I'm going to start comparing the actual data > now - just to see if there were any problems with the conversion. > > However, if I am creating a program to convert the data - I should NOT > have to worry about turning off logging of Inserts! Correct? ----------------
These are transaction logs. For doing an import there is no need to have a backup of the row, is there? You still have the .dbf. This log records all insert, update and delete statements and allows you to generate a backup plan to keep your data safe if you want to. 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 Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell _______________________________________________ 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/CAJidMYJgpmYYsCSwYtXiHYBY0GpoqGfWVA-azEmKV2b5=xx...@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.
