Transaction log full / Filespace full problems 
Author Message
 Transaction log full / Filespace full problems

Does anyone know if it's possible for data updates to go through even if you
get a "SQL0964C The transaction log for the database is full" error.
Currently we are using JDBC throgh a Java Servlet for all of our updates.
We had a window of about 24 hours where our transaction log was full.  The
Java Servlet on the web should have been receiving transaction log full
errors and not committing however the updates seemed to go through (at least
for a while it did... that's another story).  Does the update to the
database actually take place in this case?


Sun, 31 Jul 2005 05:27:49 GMT
 Transaction log full / Filespace full problems

Hi,
1)If you don't apply the full backup, please set the log type of the db as
circular logging.
2) After certain records update, issue the commit command. it will allow the
page used for all committed transactions to be reused.

Ming


Quote:
> Does anyone know if it's possible for data updates to go through even if
you
> get a "SQL0964C The transaction log for the database is full" error.
> Currently we are using JDBC throgh a Java Servlet for all of our updates.
> We had a window of about 24 hours where our transaction log was full.  The
> Java Servlet on the web should have been receiving transaction log full
> errors and not committing however the updates seemed to go through (at
least
> for a while it did... that's another story).  Does the update to the
> database actually take place in this case?



Mon, 01 Aug 2005 01:00:19 GMT
 Transaction log full / Filespace full problems
Hi,

Basically, the logfile is going to log everything you try to do against. If
the logfile is full, the database just stops working right way and the
update won't take place any more.


Quote:
> Does anyone know if it's possible for data updates to go through even if
you
> get a "SQL0964C The transaction log for the database is full" error.
> Currently we are using JDBC throgh a Java Servlet for all of our updates.
> We had a window of about 24 hours where our transaction log was full.  The
> Java Servlet on the web should have been receiving transaction log full
> errors and not committing however the updates seemed to go through (at
least
> for a while it did... that's another story).  Does the update to the
> database actually take place in this case?



Mon, 01 Aug 2005 01:06:04 GMT
 Transaction log full / Filespace full problems

Quote:

> Does anyone know if it's possible for data updates to go through even if you
> get a "SQL0964C The transaction log for the database is full" error.
> Currently we are using JDBC throgh a Java Servlet for all of our updates.
> We had a window of about 24 hours where our transaction log was full.  The
> Java Servlet on the web should have been receiving transaction log full
> errors and not committing however the updates seemed to go through (at least
> for a while it did... that's another story).  Does the update to the
> database actually take place in this case?

The application that encountered this state will ROLLBACK its transactions.
The ROLLBACK will free log space so other applications can continue
processing;  however until the rollback is complete other applications
may also receive the same SQL0964C error (and their transactions will be
rolled back, too).

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----



Mon, 01 Aug 2005 14:25:59 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Transaction logs problems ( Distribution and Publisher DB are FULL)

2. Transaction log full problem

3. problem: long transaction aborted, logs full

4. problem: long transaction aborted, logs full

5. Transaction log full?

6. Transaction Log Full

7. SQL Server 6.5 Transaction Log Full Can't Connect

8. URGENT: transaction log full

9. URGENT Transaction log full

10. tempdb full error - daily transaction log dump?

11. Transaction log full

12. Transaction log 65% full after dump.


 
Powered by phpBB® Forum Software