If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)

Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

SQL Server Transaction Log Full

rsynnott · 2005-05-08 12:07:22

Hi, I'm currently doing some work on a virtally-hosted site that uses an SQL server backend. When trying to add data to the server I'm getting "Transaction Log Full", with advice to backup the transaction log. Transaction log backup fails, however, with a no permission to write error. Am I doing something silly here? Rob

Options

08-05-2005 1:07pm

#1

rsynnott

Registered Users Posts: 4,003 ✭✭✭

Join Date: July 2003

Posts: 3930

Hi,
I'm currently doing some work on a virtally-hosted site that uses an SQL server backend. When trying to add data to the server I'm getting "Transaction Log Full", with advice to backup the transaction log. Transaction log backup fails, however, with a no permission to write error. Am I doing something silly here?
Rob

0

Comments

Options
#2 08-05-2005 2:49pm
oscarBravo

Technology & Internet Moderators Posts: 28,804 Mod ✭✭✭✭

Join Date: May 2001

Posts: 26924

The problem is that dumping the log tries to create a log entry itself, and there's no room. If memory serves, you have to stop SQL Server, delete the transaction log, restart SQL Server and dump the database immediately.

It's heading on for ten years since I admin'd a SQL Server, so there may be a better way.

0
Options
#3 08-05-2005 3:23pm
Ivan Dunaev

Closed Accounts Posts: 35 ✭

Join Date: July 2004

Posts: 35

http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
http://support.microsoft.com/Default.aspx?kbid=873235

0
Options
#4 09-05-2005 12:31pm
rsynnott

Registered Users Posts: 4,003 ✭✭✭

Join Date: July 2003

Posts: 3930

Ah, fixed now; the db was set to FULL recovery model and the host's backup drive was full. :rolleyes:

0