|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
database log file size (LDF file)Our LDF log files seem to be approching 10 gigs for a database that is only
32MB in size, however the the recover model is set for bulk-logged, I know full does a pretty much copy of the database into the log, but i thought bulk-logged was to take up less space? We back up the database nightly to tape, so is there any good reason to use this backup method or would it be better to use the simple model? The server has 120GB of space for database storage, but almost 110 of that is being used up by different database's LDF log files... any suggestions on how to conserve space or pack the logs to shrink them or such? thanks we also noticed that with the size as big as it is, when the database needs to "grow" to accomidate more data, it takes a good amount of time to expand the size and causes time-out errors (previously it was set to grow at 15% the previous size for the data and log files for each database, we change it to 25MB at a time and seems to of solved the timeout issues) what do you guys think? thanks again! Hi
You may want to check out http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp and the associated links. John Show quote "Brian Henry" wrote: > Our LDF log files seem to be approching 10 gigs for a database that is only > 32MB in size, however the the recover model is set for bulk-logged, I know > full does a pretty much copy of the database into the log, but i thought > bulk-logged was to take up less space? We back up the database nightly to > tape, so is there any good reason to use this backup method or would it be > better to use the simple model? The server has 120GB of space for database > storage, but almost 110 of that is being used up by different database's LDF > log files... any suggestions on how to conserve space or pack the logs to > shrink them or such? thanks > > we also noticed that with the size as big as it is, when the database needs > to "grow" to accomidate more data, it takes a good amount of time to expand > the size and causes time-out errors (previously it was set to grow at 15% > the previous size for the data and log files for each database, we change it > to 25MB at a time and seems to of solved the timeout issues) what do you > guys think? thanks again! > > > Are you doing transaction log backups?
How to stop the transaction log of a SQL Server database from growing unexpectedly http://support.microsoft.com/?kbid=873235 AMB Show quote "Brian Henry" wrote: > Our LDF log files seem to be approching 10 gigs for a database that is only > 32MB in size, however the the recover model is set for bulk-logged, I know > full does a pretty much copy of the database into the log, but i thought > bulk-logged was to take up less space? We back up the database nightly to > tape, so is there any good reason to use this backup method or would it be > better to use the simple model? The server has 120GB of space for database > storage, but almost 110 of that is being used up by different database's LDF > log files... any suggestions on how to conserve space or pack the logs to > shrink them or such? thanks > > we also noticed that with the size as big as it is, when the database needs > to "grow" to accomidate more data, it takes a good amount of time to expand > the size and causes time-out errors (previously it was set to grow at 15% > the previous size for the data and log files for each database, we change it > to 25MB at a time and seems to of solved the timeout issues) what do you > guys think? thanks again! > > > > Our LDF log files seem to be approching 10 gigs for a database that is
http://www.aspfaq.com/2471
> only 32MB in size http://www.aspfaq.com/2446 Is AutoShrink turned on?
To "manually" get the thing back down to size, try the script at http://support.microsoft.com/default.aspx?scid=kb;EN-US;256650 -- Show quoteDaniel Wilson Senior Software Solutions Developer Embtrak Development Team http://www.Embtrak.com DVBrown Company "Brian Henry" <nospam@nospam.com> wrote in message news:u%23r7F4ugFHA.2180@TK2MSFTNGP15.phx.gbl... > Our LDF log files seem to be approching 10 gigs for a database that is only > 32MB in size, however the the recover model is set for bulk-logged, I know > full does a pretty much copy of the database into the log, but i thought > bulk-logged was to take up less space? We back up the database nightly to > tape, so is there any good reason to use this backup method or would it be > better to use the simple model? The server has 120GB of space for database > storage, but almost 110 of that is being used up by different database's LDF > log files... any suggestions on how to conserve space or pack the logs to > shrink them or such? thanks > > we also noticed that with the size as big as it is, when the database needs > to "grow" to accomidate more data, it takes a good amount of time to expand > the size and causes time-out errors (previously it was set to grow at 15% > the previous size for the data and log files for each database, we change it > to 25MB at a time and seems to of solved the timeout issues) what do you > guys think? thanks again! > >  |
|||||||||||||||||||||||
Other interesting topics