Transaction log - full ?
SQL SERVER 6.5
Doing a large update on a table is causing syslogs full error.
My log is 400MB.
When I do a DBCC CHECKTABLE(SYSLOGS) I see 388mb still
free on the log. Dumping the transaction log with no_log clears the log
to 400mb again.
Increasing the log to 500mb allows some updates to complete
but large ones fail again with syslogs full though there is 388mb free when
I do DBCC CHECKTABLE(SYSLOGS)
Anybody come across this before ? Is my log corrupt ?
Came across the following on the web to rebuild the log but it doesn't work
dbcc rebuildlog (@dbname, 1, 0)
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL