First off you might want to check your system date as it seems to be off a
few days. But to answer your question there is no way to turn off logging.
Every thing is logged to some extent or another. Most are fully logged
operations but you can achieve what is called a Minimally logged load under
certain cirstances, but a straight insert is not one of them. Things
like BCP, Bulk Insert and Select Into can be minimally logged if the
conditions met under the "minimally logged load" section of BCP in
BooksOnLine is met. If your doing lots of inserts then you should do them
in batches and backup the log in between. If your in simple mode you can
just truncate it or if you do it in batches it should truncate on it's own
eventually. Don't wrap all the inserts in one big transaction or you can't
Andrew J. Kelly
SQL Server MVP
"Jed Ozone" <jed [email]ozone[/email]> wrote in message
news:%23NWWkODQDHA.1720TK2MSFTNGP11.phx.gbl...etc.)> Is there any way to NOT write to the Log File when doing an INSERT on a
> database setup as Simple? I am hoping there's some T-SQL syntax that can
> prevent the INSERT from being logged.
> I have a table I write to but I don't care if it's saved. All the inserts
> on the table cause the Log to grow sometimes considerably on some days.
> Related question: I'm assuming if using transactions (begin, committ,Log> that you need a Log File. Or is this not true? In the above case, I need
> to be able to do transactions on some tables, but I don't care about the> File as far as doing backups, etc.