Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Log File Growth

Status
Not open for further replies.

sendba

Programmer
Sep 7, 2005
113
US
Hi all

The SQL Server 2000 database logfile is there any default size which is configured for the growth

I see the database is logging information in 10 MB chunks is there any way i can increase this size.

I am not specifying about the file growth.There are plenty of free space.

Thanks in advance
Sen
 
Enterprise Management
Right Click DB
Select Properties
Transaction Log
Set it up the way you need


There are plenty of free space.
comment: There is never plenty of free space. Be careful with transaction log growth. You run out of disk space you're done ;-)

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]
 
I have specified that it is not related to file growth.
when transactions are logging why the file size increase only by 10 MB why cant it be 100 MB or so

Is there any way
 
How is how the transaction file increases in size NOT related to file growth :/ The answer to your question is in the screen I pointed you to. bottom section. Select the "In megabytes" to grow by. Default growth is 10 percent

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]
 
Sen,

If the logging is not causing the log to grow by 10MB every time it logs, your problem is probably due to the size of the transactions. You need to locate the query that is inputting these transactions and see if it is limiting itself to certain sized chucks (which you can change) or verify whether the "source" of your transactions are only ever 10MB (which you may not be able to change).

I advise using Profiler to help you locate the query/job in question. Once you know that, you can start rooting around for what is causing the size issue. If there's nothing obvious, then you might be stuck simply because that's the "biggest" size of information that comes in during your transactions.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top