Managing rightly the transaction log of a db for a massive import to avoid storage saturation

Hi,
I'm working on a virtual production SQL Server environment that hosts 10-15 databases. The data storage has a capacity about 400-500 GB. All databases are in simple recovery model. A my procedure on a my db (in simple recovery mode) reads 4-5 millions of
row data from 4-5 Oracle tables having 20-30 columns. The SQL Server stored procedure is called by a SSIS 2012 task. During the procedure execution, the transaction log of my db is increased exceeding 120-130 GB. This growth has caused a storage saturation
not pleasant for my customer.
So, my customer has asked me to investigate about the right management of the transaction log growth. In particular, is it possible to avoid to write in the transaction log for a certain procedure or T-SQL operation? My customer has experienced with the
Oracle dbms and has said me that Oracle manages better the storage space also with blob fields.
Also if it is possible to perform a shrink operation for the transaction log, it is need to avoid the exponential growth of the transaction log before that the storage saturates.
Any helps to me, please? Many thanks

Hi,
Please monitor hung transactions which are causing high transaction log utilization.
Also you need to look with capacity planning perspective where you need to identify the transaction with highest transaction log requirement. Accordingly you need to set the size of Transaction log. Also you can set the Autogrowth option for transaction
log based on best practices.
Please check when is the auto checkpoint takes place I mean default recovery interval in your settings.
Because in simple recovery model auto checkpoint takes place based upon recovery interval/% Transaction log used.
If the log has swollen then as a weekly maintenance you can shrink the transaction log size based upon your transaction requirements.
overall better monitoring of your running transactions ,Identify any hung transactions find the root cause,
proper log auto growth setttings will overcome most of your problem.

Similar Messages

The transaction log for database 'ECC' is full + ECC6.0 Installation Failur

Guyz,
my ecc6 installation failed after 8 hours run with following error log snippet...
exec sp_bindefault 'numc3_default','SOMG.MSGNO'
DbSlExecute: rc = 99
(SQL error 9002)
error message returned by DbSl:
The transaction log for database 'ECC' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
(DB) ERROR: DDL statement failed
(ALTER TABLE [SOMG] ADD CONSTRAINT [SOMG~0] PRIMARY KEY CLUSTERED ( [MANDT], [OBJTP], [OBJYR], [OBJNO] ) )
DbSlExecute: rc = 99
(SQL error 4902)
error message returned by DbSl:
Cannot find the object "SOMG" because it does not exist or you do not have permissions.
ECCLOG1 data file has got 25GB initial size and growth was restricted to 10% (PROPOSED BY SAPInst)...
i'm assuming this error was due to lack of growth space for ECCLOG1 datafile...am i right? if so how much should i allocate memory for this log ? or is there any workaround ?
thanks in advance

Kasu,
If SQL is complaining that the log file is full then the phase of the install that creates the SQL data/log files has already occurred (happens early in the install) and the install is importing programs, config and data into the db.
Look at the windows application event log for "Transaction log full" events to confirm.
To continue, in SQL Query analyzer try:
"Backup log [dbname] with truncate_only"
This will remove only inactive parts of the log and is safe when you don't require point-in-time recovery (which you don't during an install).
Then, go to the SQL Enterprise manager, choose the db in question and choose the shrink database function, choose to shrink only the transaction log file and the space made empty by the truncate will be removed from the file.
Change the recovery mode in SQL Server to "simple" so that the log file does not grow for the remainder of the install.
Make sure you change the recovery mode back to "full" after the install is complete.
Your transaction log appears to have filled the disk partition you have assigned to it.
25GB is huge for a transaction log and you would normally not see them grow this large if you are doing regular scheduled tlog backups (say every 30-60 minutes) because the log will truncate every time, but its not unusual to see one get big during an install, upgrade or when applying hotpacks.
Tim

The transaction log for database 'EMP_SP_SearchApp_CrawlStoreDB_32fdb1522c5249088db8b09c1917dbec' is full due to 'ACTIVE_TRANSACTION'

Hi
we have a sharepoint farm for uploading documents in huge number daily and we conifgured RBS for sql server content db.
we are facing issue in sql server instance:
Suddenly the SQL server instance restarts and sometimes failover to node1 and sometimes just restart and keep running on the current server
and did some invistagations we found that
-Analysis of data shows that the slowness of IO for tempdb.ldf is cause of the issue
-tried to check tempdb using db properties but I couldn’t see the properties it gives me error,
-There might be a big transaction locking the tempdb.
Also noted that there are lot of errors:
The transaction log for database 'MOJSP_SearchApp_CrawlStoreDB_32fdb1522c5249088db8b09c1917dbec' is full due to 'ACTIVE_TRANSACTION'
This might also be part of the problem causing locking.
we found the errors like
The transaction log for database 'EMP_SP_SearchApp_CrawlStoreDB_32fdb1522c5249088db8b09c1917dbec' is full due to 'ACTIVE_TRANSACTION'
I see that log_reuse_wait_desc (reuse of transaction log space is currently waiting on as of the last checkpoint) is 'ACTIVE_TRANSACTION'
adil

Hi Adil,
Method1:
On your SharePoint SQL Server database, open the SQL Server Management Studio.
Connect to the local SQL Server.
Right click Your Database Name.
Go to -> Properties -> Options.
Change Recover Model from Full to Simple -> Click OK.
Right click Your Database Name, go to Tasks -> Shrink -> Shrink Files.
Select a File type of Log, then Shrink.
Method2:
Run SQL Management Studio and login to your SharePoint instance.
Click on "New Query".
Type in the following commands:
USE [database name];
BACKUP LOG [Your Database Name] WITH TRUNCATE_ONLY;
DBCC
SHRINKFILE ([Your Log File Name], 1);
Replace [Your Database Name] and [Your Log File Name] with your log file.
This will truncate your log file to 1mb.
Method3:
Issue CHECKPOINT on the tempdb
USE tempdb
GO
CHECKPOINT
GO
Take Transactional log backup on the user database
BACKUP LOG CustomerXS TO DISK = N'M:\MSSQL\Backup\MSSQLSERVER\XS and RT\XS_Movement.trn' WITH COMPRESSION GO

We have "dbbackup.exe" in SqlAnywhere in BI 4.1 for running the transaction log truncation/backup. This wasn't present in BOXI 3.1. Any alternative for 3.1?

1) OS version:
OS Name : Windows Server 2008 R2
2) BO version:
    BusinessObjects XI 3.1 SP05.
3) My question:
    We have “dbbackup.exe” utility in SqlAnywhere in BI 4.1 for running the transaction log ( CMS and Audit) truncation/backup. But the same utility was not present in BOXI 3.1 SP05 for backup.
   Is there an equivalent/alternative utility in BOXI 3.1 SP05 for the same purpose? We use the command below for BI 4.1 Transaction Log truncation/backup:
E:\Program Files\SAP BusinessObjects\sqlanywhere\BIN64>dbbackup.exe -c "dsn=<System DSN>;uid=< SQL_AW_DBA_UID>;pwd=< SQL_AW_DBA_PASSWD>;host=localhost:2638" -t -x -n "E:
\Transaction_log_backup\CMS"
Any help or clarification on this issue would be greatly appreciated.
Thanks in advance.
Conor.

Hi Conor,
BOXI 3.1 SP05 does not include the dbbackup utility. Instead, you issue SQL statements to create the backup. We published a paper on the subject:
http://scn.sap.com/docs/DOC-48608
The paper uses a maintenance plan to schedule regular backups, but you don't need to do that if you want to simply create a backup when required. To do that (along with transaction log truncation), you run the SQL statement:
BACKUP DATABASE DIRECTORY 'backup-dir'
TRANSACTION LOG TRUNCATE;
For complete details about the BACKUP statement, have a look here:
http://dcx.sap.com/index.html#1201/en/dbreference/backup-statement.html
You'll need to execute the statement inside a SQL console - the paper above describes how to get that.
I hope this helps!
José Ramos
Product Manager
SAP Canada

Is the transaction log is changed when i execute select statemetns

hello
i want to ask about updateing the transaction log: is it modified when a select statement is executed
is it changed when update,delete or insert statements are executed ?

In general SELECT statement don't write redo but if you use SELECT with FOR UPDATE clause, then redo is generated and written to redo logs or in special cases like delayed block cleanout. INSERT, UPDATE and DELETE write redo, yes.
Note that Oracle right name to use is redo log and not transaction log which a Sybase/MS SQL Server concept.

Fatal Error: Unable to write to the transaction log

I encounter the following error messsage when i run my jsp:
Fatal Error: Unable to write to the transaction log (/D:/jdev9i_902/jdev/system/oc4j-config/log/transaction.state), possible reasons for this are that Orion lacks permission to write to the file, or that another instance of the server is already running with this configuration (most common): Unable to alter transaction log
P.S. I have checked the 'Run Manager', no active process has been running. Does anyone know how to solve it?

Believe it or not!? I solve it by restarting my computer ... XD. At the mean time, i open a MS-DOS window to monitor my netstat ...

The system failed to flush data to the transaction log. Corruption may occur.

We have a windows server 2008 R2 Virtual machine and we are getting the following Warning Event.
Event 51 Volmgr
The system failed to flush data to the transaction log. Corruption may occur.
Any idea what is wrong with this server? Why this event is occurring?

Hi Jitender KT,
Before going further, would you please let me know the complete error message that you can find (such as a
screenshot if you can provide)? Please check and confirm in Event Viewer if there other related event you can find, such as Event 57 and so on. Meanwhile, can you remember what operations you have done before the warning occurred?
Based on current message that you provided, please run
Chkdsk command to check if you can find error. The issue seems to be related to the storage device. Please refer to the following similar question.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/044b10af-c253-46de-b40d-ce9d128b83d7/event-id-57-source-volmgr?forum=winservergen
In addition, please also refer to the following link. It should be helpful.
http://www.eventid.net/display-eventid-57-source-volmgr-eventno-8865-phase-1.htm
Hope this helps.
Best regards,
Justin Gu

The transaction log for database 'Test_db' is full due to 'LOG_BACKUP'

My dear All,
Came up with another issue:
App team is pushing the data from one Prod1 server 'test_1db' to another Prod2 server 'User_db' through a job, here while pushing the data after some duration job is failing and throwing the following error
'Error: 9002, Severity: 17, State: 2.'The transaction log for database 'User_db' is full due to 'LOG_BACKUP'''.
On Prod2 server 'User_db' log is having enough space 400gb on drive and growth is 250mb. I really confused that why job is failing as there is lot of space available. Kindly guide me to troubleshoot the issue as this issue is occuring from more than
1 week. Kindly refer the screenshot for the same.
Environment: SQL Server 2012 with sp1 Ent-edition. and log backup duration is every 15 mints and there is no High availability between the servers.
Note: Changing to simple recovery model may resolve but App team is required to run in Full recovery model as they need of log backups.
Thanks in advance,
Nagesh
Nagesh

Dear V,
Thanks for the susggestions.
I have followed some steps to resolve the issue, as of now my jobs are working without issue.
Steps:
Generating log backup for every 5 minutes
Increased the growth 500mb to unrestricted.
Once whole job completed we are shrinking the log file.
Nagesh

You want to know the amount of space the transaction log for the Customer database is using. Which T-SQL command would you use?

You want to know the amount of space the transaction log for the Customer database is using. Which T-SQL command would you use?

Forced me to do a little research.
DBCC SQLPERF(logspace)
See also
http://stackoverflow.com/questions/198343/how-can-i-get-the-size-of-the-transaction-log-in-sql-2005-programmatically
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
My TechNet articles

The transaction log for database 'SharePoint_Config' is full

Hi all ,
I am very new to sharepoint. when i tried to remove a wsp file from central administration i got the message like
The transaction log for database 'SharePoint_Config' is full. To find out why space in the log cannot
be reused, see the log_reuse_wait_desc column in sys.databases.
Can anybody help me to solve this please. I saw one solution in net like this but i don't know how to do this. Can anybody help me how to do these steps please.
1.
Take the configuration database offline and detach it
2.
Copy the current MDF to a new location (to be used as a way of recovering the database if needed)
3.
Put the database back on-line, reattach it and then put it within simple mode (from full), with an aim of this stopping the database from
increasing in size
4.
Shrink the database and recover log space
5.
Should the shrinking fail, we'd look at detaching the database, making a sideways copy of the log file to another database
6.
We would then reattach the database, which should generate a new log file
Thank you

Hi Soumya,
I don't have any dba resource. And it is not a lab environment. It's Corporate environment.
Thanks alot for ur quick reply.
I normally don't just come onto the threads and tell people that they need a consultant, but you might want to look at getting a consultant to help make sure that your SharePoint environment is health and can be restored in the event of a server failure.
Based on the problem that you have described it might not be recoverable, or at least it might not be as recoverable as you want it to be.
At the very least you'll want to watch this video of my session at TechEd 2014 which talks about backups and how to set them up.
http://channel9.msdn.com/events/TechEd/NorthAmerica/2014/DBI-B214#fbid=
Thank You,
Denny Cherry

Why is the transaction log file not truncated though its simple recovery model?

My database is simple recovery model and when I view the free space in log file it shows 99%. Why doesn't my log file truncate the committed
data automatically to free space in ldf file? When I shrink it does shrink. Please advice.
mayooran99

My database is simple recovery model and when I view the free space in log file it shows 99%. Why doesn't my log file truncate the committed
data automatically to free space in ldf file? When I shrink it does shrink. Please advice.
mayooran99
If log records were never deleted(truncated) from the transaction log it wont show as 99% free.Simple recoveyr model
Log truncation automatically frees space in the logical log for reuse by the transaction log and thats what you are seeing. Truncation wont change file size. It more like
log clearing, marking
parts of the log free for reuse.
As you said "When I shrink it does shrink" I dont see any issues here. Log truncation and shrink file is 2 different things.
Please read below link for understanding "Transaction log Truncate vs Shrink"
http://blog.sqlxdetails.com/transaction-log-truncate-why-it-didnt-shrink-my-log/

How to find out whether the transaction logs are being truncated or not

Hi,
We are using Veritas Backup tool for Backups and restores on our MS SQL 2000.
One of our Veritas Tech has disabled the Truncation of Transaction Log Backup using the Job setup in Veritas. We want to confirm whether the Truncation is happening or not. I don't see any difference in the Transaction Log file size.
How to find out whether truncation is active or not?
Thanks
Vijay

Hello Vijay,
On MSSQL truncation of transaction log does not shrink the size of the transaction log. It simply removes the content within the transaction log and writes it to the backup.
Meaning the free percentage within the transaction log will increase.
If you want to Resize the transaction log size, you need to do something else.
The shrinking procedure is given here:
http://support.microsoft.com/kb/907511
Regards,
Siddhesh

SQL0964C The transaction log for the database is full

Hi,
i am planning to do QAS refresh from PRD system using Client export\import method. i have done export in PRD and the same has been moved to QAS then started imported.
DB Size:160gb
DB:DB2 9.7
os: windows 2008.
I facing SQL0964C The transaction log for the database is full issue while client import and regarding this i have raised incident to SAP then they replied to increase some parameter like(LOGPRIMARY,LOGSECOND,LOGFILSIZ) temporarily and revert them back after the import. Based on that i have increased from as below mentioned calculation.
the filesystem size of /db2/<SID>/log_dir should be greater than LOGFILSIZ*4*(Sum of LOGPRIMARY+LOGSECONDARY) KB
From:
Log file size (4KB)                         (LOGFILSIZ) = 60000
Number of primary log files                (LOGPRIMARY) = 50
Number of secondary log files               (LOGSECOND) = 100
Total drive space required: 33GB
To:
Log file size (4KB)                         (LOGFILSIZ) = 70000
Number of primary log files                (LOGPRIMARY) = 60
Number of secondary log files               (LOGSECOND) = 120
Total drive space required: 47GB
But still facing the same issue. Please help me to resolve the ASAP.
Last error TP log details:
3 ETW674Xstart import of "R3TRTABUFAGLFLEX08" ...
4 ETW000   1 entry from FAGLFLEX08 (210) deleted.
4 ETW000   1 entry for FAGLFLEX08 inserted (210*).
4 ETW675 end import of "R3TRTABUFAGLFLEX08".
3 ETW674Xstart import of "R3TRTABUFAGLFLEXA" ...
4 ETW000 [     dev trc,00000] Fri Jun 27 02:20:21 2014                                             -774509399 65811.628079
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] CON = 0 (BEGIN)                    85 65811.628164
4 ETW000 [     dev trc,00000] &+     DbSlModifyDB6( SQLExecute ): [IBM][CLI Driver][DB2/NT64] SQL0964C The transaction log for the database is full.
4 ETW000                                                                                                  83 65811.628247
4 ETW000 [     dev trc,00000] &+     SQLSTATE=57011 row=1
4 ETW000                                                                                                  51 65811.628298
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  67 65811.628365
4 ETW000 [     dev trc,00000] &+     DELETE FROM "FAGLFLEXA" WHERE "RCLNT" = ?
4 ETW000                                                                                                  62 65811.628427
4 ETW000 [     dev trc,00000] &+       cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, op_type=8, reopt=0
4 ETW000                                                                                                  58 65811.628485
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  53 65811.628538
4 ETW000 [     dev trc,00000] &+     Input SQLDA:
4 ETW000                                                                                                  52 65811.628590
4 ETW000 [     dev trc,00000] &+                        1 CT=WCHAR           T=VARCHAR         L=6     P=9     S=0
4 ETW000                                                                                                  49 65811.628639
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  50 65811.628689
4 ETW000 [     dev trc,00000] &+     Input data:
4 ETW000                                                                                                  49 65811.628738
4 ETW000 [     dev trc,00000] &+     row 1:             1 WCHAR           I=6       "210"               34 65811.628772
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  51 65811.628823
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  50 65811.628873
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] (END)                              27 65811.628900
4 ETW000 [    dbtran ,00000] ***LOG BY4=>sql error -964   performing DEL on table FAGLFLEXA
4 ETW000                                                                                                3428 65811.632328
4 ETW000 [    dbtran ,00000] ***LOG BY0=>SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1
4 ETW000                                                                                                  46 65811.632374
4 ETW000 [     dev trc,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'                             59 65811.632433
4 ETW000                         RSLT: {dbsl=99, tran=1}
4 ETW000                         FHDR: {tab='FAGLFLEXA', fcode=194, mode=2, bpb=0, dbcnt=0, crsr=0,
4 ETW000                                hold=0, keep=0, xfer=0, pkg=0, upto=0, init:b=0,
4 ETW000                                init:p=0000000000000000, init:#=0, wa:p=0X00000000020290C0, wa:#=10000}
4 ETW000 [     dev trc,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'                            126 65811.632559
4 ETW000                         STMT: {stmt:#=0, bndfld:#=1, prop=0, distinct=0,
4 ETW000                                fld:#=0, alias:p=0000000000000000, fupd:#=0, tab:#=1, where:#=2,
4 ETW000                                groupby:#=0, having:#=0, order:#=0, primary=0, hint:#=0}
4 ETW000                         CRSR: {tab='', id=0, hold=0, prop=0, max.in@0=1, fae:blk=0,
4 ETW000                                con:id=0, con:vndr=7, val=2,
4 ETW000                                key:#=3, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=0X00000001421A3000}
2EETW125 SQL error "-964" during "-964" access: "SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1"
4 ETW690 COMMIT "14208" "-1"
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] CON = 0 (BEGIN)                 16208 65811.648767
4 ETW000 [     dev trc,00000] &+     DbSlModifyDB6( SQLExecute ): [IBM][CLI Driver][DB2/NT64] SQL0964C The transaction log for the database is full.
4 ETW000                                                                                                  75 65811.648842
4 ETW000 [     dev trc,00000] &+     SQLSTATE=57011 row=1
4 ETW000                                                                                                  52 65811.648894
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  51 65811.648945
4 ETW000 [     dev trc,00000] &+     INSERT INTO DDLOG (SYSTEMID, TIMESTAMP, NBLENGTH, NOTEBOOK) VALUES ( ? , CHAR(   CURRENT TIMESTAMP - CURRENT TIME
4 ETW000                                                                                                  50 65811.648995
4 ETW000 [     dev trc,00000] &+     ZONE   ), ?, ? )
4 ETW000                                                                                                  49 65811.649044
4 ETW000 [     dev trc,00000] &+       cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, op_type=15, reopt=0
4 ETW000                                                                                                  55 65811.649099
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  49 65811.649148
4 ETW000 [     dev trc,00000] &+     Input SQLDA:
4 ETW000                                                                                                  50 65811.649198
4 ETW000 [     dev trc,00000] &+                        1 CT=WCHAR           T=VARCHAR         L=44    P=66    S=0
4 ETW000                                                                                                  47 65811.649245
4 ETW000 [     dev trc,00000] &+                        2 CT=SHORT           T=SMALLINT        L=2     P=2     S=0
4 ETW000                                                                                                  48 65811.649293
4 ETW000 [     dev trc,00000] &+                        3 CT=BINARY          T=VARBINARY       L=32000 P=32000 S=0
4 ETW000                                                                                                  47 65811.649340
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  50 65811.649390
4 ETW000 [     dev trc,00000] &+     Input data:
4 ETW000                                                                                                  49 65811.649439
4 ETW000 [     dev trc,00000] &+     row 1:             1 WCHAR           I=14      "R3trans"           32 65811.649471
4 ETW000 [     dev trc,00000] &+                        2 SHORT           I=2        12744              32 65811.649503
4 ETW000 [     dev trc,00000] &+                        3 BINARY          I=12744   00600306003200300030003900300033003300310031003300320036003400390000...
4 ETW000                                                                                                  64 65811.649567
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  52 65811.649619
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  51 65811.649670
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] (END)                              28 65811.649698
4 ETW000 [    dbsyntsp,00000] ***LOG BY4=>sql error -964   performing SEL on table DDLOG                36 65811.649734
4 ETW000 [    dbsyntsp,00000] ***LOG BY0=>SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1
4 ETW000                                                                                                  46 65811.649780
4 ETW000 [    dbsync ,00000] ***LOG BZY=>unexpected return code 2          calling ins_ddlog           37 65811.649817
4 ETW000 [     dev trc,00000] db_syflush (TRUE) failed                                                  26 65811.649843
4 ETW000 [     dev trc,00000] db_con_commit received error 1024 in before-commit action, returning 8
4 ETW000                                                                                                  57 65811.649900
4 ETW000 [    dbeh.c ,00000] *** ERROR => missing return code handler                               1974 65811.651874
4 ETW000                         caller does not handle code 1024 from dblink#5[321]
4 ETW000                         ==> calling sap_dext to abort transaction
2EETW000 sap_dext called with msgnr "900":
2EETW125 SQL error "-964" during "-964" access: "SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1"
1 ETP154 MAIN IMPORT
1 ETP110 end date and time   : "20140627022021"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
Regards,
Rajesh

Hi Babu,
I believe you should have taken a restart of your system if log primary are changed. If so, then increase log primary to 120 and secondary to 80 provide size and space are enough.
Note 1293475 - DB6: Transaction Log Full
Note 1308895 - DB6: File System for Transaction Log is Full
Note: 495297 - DB6: Monitoring transaction log
Regards,
Divyanshu

If I set database mode to Simple and do deleting with batches, Will these delete not written to the Transaction log ?

Hi
I have large database and i need to perform batch deleting without affecting the transaction log. So if I set the Recovery mode to Simple before deleting the transaction log will not grow ??
Thanks.

Hi
I have large database and i need to perform batch deleting without affecting the transaction log. So if I set the Recovery mode to Simple before deleting the transaction log will not grow ??
Thanks.
You CANNOT delete records in sql server without getting information logged in transaction log. Please note every thing in SQL Server is logged and logging depends on recovery model used. When you use simple recovery logging will
almost be same as full just after checkpoint logs would be truncated and also when log file grows 70 % of its size. This can only not happen IF some ongoing transaction is not holding the VLF or requires the VLF(virtual
log file)
So you made good choice to delete in batches. Also have a look on Lock escalation
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Turn off the Transaction log

All,
My client copy is really big.
How can I switch off the Transaction logs in SQL server whie doing client copy.
I DO NOT want Trans log keep increasing.
In oracle, I can turn off the archive logs.
Please advise.
Thanks again and hope to hear from you soon.
From,
PT.

Hello,
the log backup on simple mode is not necessary. The full database after switching back to full is a must.
Please keep in mind, that even running on simple mode the log can be filled up, as all transactions are still written to the log. Commited transaction then can truncated from the log. But when you run a hugh transaction like a client copy, the log might grow as well. The log will be freed once the transaction commits or rolls back. And no, you can't split a client copy in several transactions.
Best regards
Clas

Managing rightly the transaction log of a db for a massive import to avoid storage saturation

Similar Messages

Maybe you are looking for