Home > Archive > MS SQL Server > March 2006 > Turn off logging for JDBC insert statements









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Turn off logging for JDBC insert statements
John Doody

2006-03-27, 1:23 pm

I'm performing many insert statements into SQL Server 2000 via JDBC. Is
there a way to turnoff database logging via JDBC before I start
inserting rows?

Thanks.
Geoff N. Hiten

2006-03-27, 1:23 pm

No. The log is required to maintain database consistency in case of a
client disconnect or a power failure or any other transactional
interruption.

Depending on the type of data loading you are doing, you may find the
"BULK-LOGGED" recovery model helpful. Look up the topic in BOL (Books
On-Line) to find out if this will work in your circumstance.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP


"John Doody" <perseid@worldnet.att.net> wrote in message
news:8CWVf.636795$qk4.627077@bgtnsc05-news.ops.worldnet.att.net...
> I'm performing many insert statements into SQL Server 2000 via JDBC. Is
> there a way to turnoff database logging via JDBC before I start inserting
> rows?
>
> Thanks.



John Doody

2006-03-27, 8:23 pm

Thanks. That looks like a viable option. Makes sense one wouldn't want
to impact database logging via a JDBC connection.

Geoff N. Hiten wrote:
> No. The log is required to maintain database consistency in case of a
> client disconnect or a power failure or any other transactional
> interruption.
>
> Depending on the type of data loading you are doing, you may find the
> "BULK-LOGGED" recovery model helpful. Look up the topic in BOL (Books
> On-Line) to find out if this will work in your circumstance.
>

David J. Cartwright

2006-03-27, 8:23 pm

you could alter database to change logging, then change back.


"Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message
news:%23FDrEKdUGHA.5468@TK2MSFTNGP14.phx.gbl...
> No. The log is required to maintain database consistency in case of a
> client disconnect or a power failure or any other transactional
> interruption.
>
> Depending on the type of data loading you are doing, you may find the
> "BULK-LOGGED" recovery model helpful. Look up the topic in BOL (Books
> On-Line) to find out if this will work in your circumstance.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "John Doody" <perseid@worldnet.att.net> wrote in message
> news:8CWVf.636795$qk4.627077@bgtnsc05-news.ops.worldnet.att.net...
>
>



Tibor Karaszi

2006-03-28, 7:23 am

Such alteration doesn't affect regular inserts, only imports performed any of the bulk loading
mechanisms.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/



"David J. Cartwright" < davidcartwright@hotm
ail.com> wrote in message
news:%23jMSzudUGHA.5660@TK2MSFTNGP12.phx.gbl...
> you could alter database to change logging, then change back.
>
>
> "Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message
> news:%23FDrEKdUGHA.5468@TK2MSFTNGP14.phx.gbl...
>
>



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com