high usage ldf file of memory in simple recovery

Hi,
My database is in the simple recovery mode. During bulk-operations it is growing very high and utilization of memory space is very high and we had a seperate drive for ldf files. After some time again it came to its original size.
Pl, let know why it is growing when it is in simple recovery? The cause might be SQL Server may not have enough time to run a checkpoint and complete the log truncation? Correct if I’m wrong?
Let me know the best practice to maintain the log file when it is in simple recovery?
krishna_harikAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chapmandewCommented:
So, there is really nothing different between simple and full, other than simple will not fully log some bulk logged operations and it truncates the log on checkpoint.  If you've got long running transactions, then your log is likely not having an opportunity to truncate.
0
Máté FarkasDatabase Developer and AdministratorCommented:
You don't have to care about the size of the transaction log (.ldf file). At the optimal case, it is better at what bigger.
First, every modification in the database file is written to log. If the commit of the transaction is executed succesfully then the logged modifications will be copied to the data file. So if your transaction modifies large amount of pages (such as bulk insert) then the log file will grow but after the commit this large log file becomes empty (in simple recovery model) and the space within the file can be reusable (but the physical size will not decrease automatically).
If the log file is not enough large for the actual transaction the storage engine must increase the size of the log file. These space allocations can cause the high disk usage. You have to set the size and the decreasing size enough large and it is not a good idea to truncate and shrink it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
krishna_harikAuthor Commented:
test
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.