Log file is 13 gigs

Posted by Mark MVN on September 14, 2005, 8:42 pm

Please log in for more thread options

My log files for the SQL that comes with HeadquartersRMS is now up to 13
gigs in the log file directory. How do I change this size or even stop it?

What happens if I deleted that log file?

Posted by Greg Staples on September 14, 2005, 9:36 pm

Please log in for more thread options

Wow, that is huge. The log file should be cleared when you run backups. I
spend most of my time in SQL using the server tools--enterprise manager. If
you have access to enterprise manager, backup both the database and
transaction log and shrink the database. The log file should return to the
KB range. You can also take the database offline with a detach database
command. Offline, delete the ldf file and then reattach the db. A new,
small, empty ldf will be created.
I can look up the scripts to detach/reattach if you need that and somebody
else doesn't jump in with a better solution.

> My log files for the SQL that comes with HeadquartersRMS is now up to 13

> gigs in the log file directory. How do I change this size or even stop it?

> What happens if I deleted that log file?

Posted by @nirgendwo on September 14, 2005, 10:06 pm

Please log in for more thread options

When the transaction logs grow to an unacceptable limit, you must immediately
back up your transaction log file. While the backup of your transaction log
files is created, SQL Server automatically truncates the inactive part of the
transaction log. The inactive part of the transaction log file contains the
completed transactions, and therefore, the transaction log file is no longer
used by SQL Server during the recovery process. SQL Server reuses this
truncated, inactive space in the transaction log instead of permitting the
transaction log to continue to grow and to use more space.

I recommend not deleting log file directly. If a disaster or data corruption
occurs, you can recover your database to the point when the failure occurred
by restoring your database with the transaction log file backups.

The backup operation does not reduce the log file size. To reduce the size
of the transaction log file, you must shrink the transaction log file. To
shrink a transaction log file to the requested size and to remove the unused
pages, you must use the DBCC SHRINKFILE operation. The DBCC SHRINKFILE
statement can only shrink the inactive part inside the log file.

"Mark_MVN" wrote:

> My log files for the SQL that comes with HeadquartersRMS is now up to 13

> gigs in the log file directory. How do I change this size or even stop it?

> What happens if I deleted that log file?

Posted by Mark MVN on September 15, 2005, 8:16 am

Please log in for more thread options

The log file was deleted and now the databse is hosed. We re-setup the store
with the last database backup (from Feb, 2005). None of the store level
configurations have been changed, but it may need to have updates to the
global database. What worksheets should we run? All our data is stored at
another location on a SQL 2000 server with Headquarters server on a seperate
box.
Are we going to be able to replicate
1. Employees
2. Changes to the inventory
3. Changes to sales taxes
4. Any of the historical info?

If so how do I replicate this to my store?

"Kaibin" wrote:

> When the transaction logs grow to an unacceptable limit, you must immediately

> back up your transaction log file. While the backup of your transaction log

> files is created, SQL Server automatically truncates the inactive part of the

> transaction log. The inactive part of the transaction log file contains the

> completed transactions, and therefore, the transaction log file is no longer

> used by SQL Server during the recovery process. SQL Server reuses this

> truncated, inactive space in the transaction log instead of permitting the

> transaction log to continue to grow and to use more space.

> I recommend not deleting log file directly. If a disaster or data corruption

> occurs, you can recover your database to the point when the failure occurred

> by restoring your database with the transaction log file backups.

> The backup operation does not reduce the log file size. To reduce the size

> of the transaction log file, you must shrink the transaction log file. To

> shrink a transaction log file to the requested size and to remove the unused

> pages, you must use the DBCC SHRINKFILE operation. The DBCC SHRINKFILE

> statement can only shrink the inactive part inside the log file.

> "Mark_MVN" wrote:

> > My log files for the SQL that comes with HeadquartersRMS is now up to 13

> > gigs in the log file directory. How do I change this size or even stop it?

> >

> > What happens if I deleted that log file?

Posted by Jason on September 15, 2005, 2:59 pm

Please log in for more thread options

There may be a way to save your data if you still have the original .mdf
file for your company. I'd call MS...you are treading on awfully thin ice,
especially if you don't know how to work with a SQL database.

Jason

> The log file was deleted and now the databse is hosed. We re-setup the

> store

> with the last database backup (from Feb, 2005). None of the store level

> configurations have been changed, but it may need to have updates to the

> global database. What worksheets should we run? All our data is stored at

> another location on a SQL 2000 server with Headquarters server on a

> seperate

> box.

> Are we going to be able to replicate

> 1. Employees

> 2. Changes to the inventory

> 3. Changes to sales taxes

> 4. Any of the historical info?

> If so how do I replicate this to my store?

> "Kaibin" wrote:

>> When the transaction logs grow to an unacceptable limit, you must

>> immediately

>> back up your transaction log file. While the backup of your transaction

>> log

>> files is created, SQL Server automatically truncates the inactive part of

>> the

>> transaction log. The inactive part of the transaction log file contains

>> the

>> completed transactions, and therefore, the transaction log file is no

>> longer

>> used by SQL Server during the recovery process. SQL Server reuses this

>> truncated, inactive space in the transaction log instead of permitting

>> the

>> transaction log to continue to grow and to use more space.

>> I recommend not deleting log file directly. If a disaster or data

>> corruption

>> occurs, you can recover your database to the point when the failure

>> occurred

>> by restoring your database with the transaction log file backups.

>> The backup operation does not reduce the log file size. To reduce the

>> size

>> of the transaction log file, you must shrink the transaction log file. To

>> shrink a transaction log file to the requested size and to remove the

>> unused

>> pages, you must use the DBCC SHRINKFILE operation. The DBCC SHRINKFILE

>> statement can only shrink the inactive part inside the log file.

>> "Mark_MVN" wrote:

>> > My log files for the SQL that comes with HeadquartersRMS is now up to

>> > 13

>> > gigs in the log file directory. How do I change this size or even stop

>> > it?

>> >

>> > What happens if I deleted that log file?