Re: How to manage the transaction log
- From: "bass_player" <bass_player@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 3 Jun 2009 19:24:32 -0400
You can switch to SIMPLE recovery model before the BCP task and switch back
to FULL recovery model. I doubt that this is a highly critical database
since it is running on SQL Server Express so I'd recommend sticking with
SIMPLE recovery model. Just remember to backup the database before the BCP
task just to be sure
"Accesshelp" <Accesshelp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:179C5290-4BC6-4B19-BD44-BB37653C92A4@xxxxxxxxxxxxxxxx
Hello all,
How do I manage the transaction log file (ldf) so that it would not keep
growing and so that I can import the data into the database?
I am using the SQL Server 2005 Express. All my data are in csv files, and
I
import them into SQL via bcp.
Initially, I set the Autogrowth of log file unrestricted. Then it grew up
to 8 GB. Because of that I was not able to run the queries in SQL.
Then I created another database by setting the log file to 25 MB max with
restricted growth. Now I am no longer able to import the data from csv
via
bcp because the SQL is not able to write to the log.
I will end up importing 4 GB of transactions into SQL from csv files. Is
there a way I can turn off the recording to the log during the import and
turn it back on after the import?
Thanks.
.
- Follow-Ups:
- Re: How to manage the transaction log
- From: Accesshelp
- Re: How to manage the transaction log
- References:
- How to manage the transaction log
- From: Accesshelp
- How to manage the transaction log
- Prev by Date: Re: BCP Error 08001, Nativeerror 2
- Next by Date: Re: How to manage the transaction log
- Previous by thread: How to manage the transaction log
- Next by thread: Re: How to manage the transaction log
- Index(es):
Relevant Pages
|