Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Help! Log File Full Expand / Collapse
Author
Message
Posted Friday, July 19, 2013 8:23 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Today @ 7:38 AM
Points: 18, Visits: 42
Hi there

I'm a novice at SQL so bear with me here. I'm getting the following message when I run a SP:

The transaction log for database '???db' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Recovery mode is simple and I have truncated the log using shrinkfile. The log_reuse_wait_desc column is NOTHING but I'm still getting he same error!

Thanks in advance

Dave.

Post #1475511
Posted Friday, July 19, 2013 8:42 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 3:03 AM
Points: 42, Visits: 243
What is that SP all about?
Run dbcc sqlperf(logspace) to find out the log file usage of dbs
Refer the Errorlog (xp_readerrorlog) to find the error logged.
Post #1475521
Posted Friday, July 19, 2013 8:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:59 AM
Points: 5,227, Visits: 9,437
Sounds like your stored procedure is making more modifications than there is room for the transaction log to record. If that's the case, rewrite the procedure so that it's more efficient. If that's not possible, you'll need to increase the size of your transaction log.

John
Post #1475530
Posted Friday, July 19, 2013 8:52 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Today @ 7:38 AM
Points: 18, Visits: 42
Yes, the transaction log seems to be limited to 99MB because it increases to this size from 10MB after truncation, how can I increase this or make it unlimited?

Thanks
Post #1475532
Posted Friday, July 19, 2013 8:55 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:59 AM
Points: 5,227, Visits: 9,437
ALTER DATABASE MODIFY FILE (....)

If you don't know the syntax, you can search for it. Or you can just use the GUI.

John
Post #1475537
Posted Friday, July 19, 2013 8:59 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Today @ 7:38 AM
Points: 18, Visits: 42
Super, that's sorted now through the GUI.

Thanks for your help.

Dave.
Post #1475539
Posted Friday, July 19, 2013 9:34 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:54 PM
Points: 42,434, Visits: 35,488
Please read through this: http://www.sqlservercentral.com/articles/Transaction+Log/72488/


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1475558
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse