Transaction log used 200GB unable to shrink

Hi All,
Currently I am facing diskspace(0 KB available) issue in one of my application server..
When I checked SQL server SMS_UDB (is our DB name) containing 70GB but SMS_UDB_LOG (Transaction log) Containing more than 200GB. When I checked the diskspace report 200GB space used (showing Green). I am unable to shrink the file. I am running 2008 SQL with
simple recovery model. I taken bak to other server. It's urgent Kindly help me to reduce the transaction log
thanks

Hello,
Please verify if the initial size for the log on the properties of the database is set to big number of MB and for that reason the database
shrink does not work.
Please run the following query and share the results with us:
SELECT
name,
log_reuse_wait_desc
FROM
sys.databases
WHERE
log_reuse_wait_desc='ACTIVE_TRANSACTION'
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Big transaction log file

Hi,
I found a sql server database with a transaction log file of 65 GB.
The database is configured with the recovery model option = full.
Also, I noticed than since the database exist, they only took database backup.
No transaction log backup were executed.
Now, the "65 GB transaction log file" use more than 70% of the disk space.
Which scenario do you recommend?
1- Backup the database, backup the transaction log to a new disk, shrink the transaction log file, schedule transaction log backup each hour.
2- Backup the database, put the recovery model option= simple, shrink the transaction log file, Backup the database.
Does the " 65 GB file shrink" operation would have impact on my database users ?
The sql server version is 2008 sp2 (10.0.4000)
regards
D

I've read the other posts and I'm at the position of: It really doesn't matter.
You've not needed point in time restore abilities inclusive of this date and time since inception. Since a full database backup contains all of the log needed to bring the database into a consistent state, doing a full backup and then log backup is redundant
and just taking up space.
For the fastest option I would personally do the following:
1. Take a full database backup
2. Set the database recovery model to Simple
3. Manually issue two checkpoints for good measure or check to make sure the current VLF(active) is near the beginning of the log file
4. Shrink the log using the truncate option to lop off the end of the log
5. Manually re-size the log based on usage needed
6. Set the recovery model to full
7. Take a differential database backup to bridge the log gap
The total time that will take is really just the full database backup and the expanding of the log file. The shrink should be close to instantaneous since you're just truncating the end and the differential backup should be fairly quick as well. If you don't
need the full recovery model, leave it in simple and reset the log size (through multiple grows if needed) and take a new full backup for safe keeping.
Sean Gallardy | Blog |
Twitter

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.

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/

Read transaction log

hello,
I have seen that a user is using too much ressources on my exchange server 2010 (used Exmon to get the user)
the point is, i do not know whats going on. I see on each log file on the server that is name is coming a lot of time, but the file is crypted (file like E0000000A.log).
Do you know any tools or something to help me out to get what is going on on this mailbox ?
So much traffic and packet like 4000 per minutes...
thx for your help.

Jero,
Parse the transaction logs using log parser.
http://blogs.msdn.com/b/scottos/archive/2007/11/07/remix-using-powershell-to-parse-ese-transaction-logs.aspx?wa=wsignin1.0
http://hermannmaurer.blogspot.in/2012/05/exchange-2010-transaction-logfiles-grow.html
Regards,
ASP20
Hello
I have tryied, log parser 2.2, but no result as i dont know the log type to put. Any more information or tutorials ?
Also i tried the Get-StoreUsageStatistics -Database DB | sort logrecordbytes -descending | select -first 10 | select displayname, timeinserver, digestcategory,logrecordcount,logrecordbytes,@{n='logrecordMb';e={[math]::round($_.logrecordbytes/1MB,3)}},SampleTime,ServerName,DatabaseName
| ft -AutoSize, return me the user i have targeted with exmon.exe, but still no info about whats wrong.
get this return (where User X is the hammering user on the server)
DisplayName TimeInServer DigestCategory LogRecordCount LogRecordBytes logrecordMb SampleTim
Boîte aux lettres - User X 32793 LogBytes 58186 58771332 56,049 16/05/20.
Boîte aux lettres - User X 33430 LogBytes 55670 56481469 53,865 16/05/20.
Boîte aux lettres - User X 30057 LogBytes 54078 54983694 52,437 16/05/20.
Boîte aux lettres - User X 33104 LogBytes 54137 54338453 51,821 16/05/20.
Boîte aux lettres - User X 28259 LogBytes 49456 50254831 47,927 16/05/20.
Boîte aux lettres - User X 23761 LogBytes 38417 39139380 37,326 16/05/20.
Boîte aux lettres - User HHHHH 20137 LogBytes 19993 7451912 7,107 16/05/20.
Boîte aux lettres - User X 3982 TimeInServer 6701 6879487 6,561 16/05/20.
Boîte aux lettres - User X 4134 TimeInServer 6760 6846904 6,53 16/05/20.
Boîte aux lettres - User BB 7139 LogBytes 5013 6787055 6,473 16/05/20.
User X is using an Ipad, Iphone and Outlook 2013 to access to mail / calendar.

Error trying to shrink logs using management studio

hi,
i am trying to shrink my transaction logs. my database is 4.4TB in size. the trn logs are backed up every 15mins to nas so not quite sure how they blew up from 100gb to over 200gb in one night.
when i try to shrink files i get. cannot show requested dialog. value of 4625504 is not
valid for value. value should be between minimum and maximum parameter name: vlaue.
nothing in the event log......
any help appreciated.
thanks
phill

Hello,
Try applying the latest service pack on SSMS or use a newer version of SSMS. My suggestion is based on the following Connect item:
http://connect.microsoft.com/SQLServer/feedback/details/688397/ssms-database-shrink-dialog-displays-value-of-x-is-not-valid-for-value-value-should-be-between-minimum-and-maximum
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Unable to delete records as the transaction log file is full

My disk is running out of space and as a result I decided to free some space by deleting old data. I tried to delete 100,000 by 100,000 as there are 240 million records to be deleted. But I am unable to delete them at once and shrinking the database doesn't
free much space. This is the error im getting at times.
The transaction log for database 'TEST_ARCHIVE' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
How can I overcome this situation and delete all the old records? Please advice.
mayooran99

In order to delete the SQL Server need to write the information in the log file, and you do not have the place for those rows in the log file. You might succeeded to delete less in each time -> next backup the log file each time -> next shrink the
log file... but this is not the way that I would chose.
Best option is probably to add another disc (a simple disk do not cost a lot), move the log file there permanently. It will increase the database work as well (it is highly recommend not to put the log file on the same disk as the data file in most cases).
If you can't add new disk permanently then add one temporary. Then add file to the database in this disk -> create new table in this disk -> move all the data that you do
not want to delete to the new table -> truncate the current table -> bring back the data om the new table -> drop the new table and the new file to release the temporary disk.
Are you using full mode or simple recovery mode ?
* in full mode you have to backup the log file if you want to shrink it
Ronen Ariely
[Personal Site] [Blog] [Facebook]

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

Transaction log usage grows due to replication even if I don't use replication at all

Hi
The transaction log usage keeps growing a lot on my user database since few days back. the database is in full recovery model and I do transaction log backups every 10 minutes. The DB was part of Database Mirroring but I removed it. The usage was controlled
for many years by the backups but something happened that is messing up the transaction log
this is DBCC OPENTRAN
Transaction information for database 'MyDB'.
Replicated Transaction Information:
Oldest distributed LSN : (0:0:0)
Oldest non-distributed LSN : (1450911:6823:1)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
log_reuse_wait_desc reports REPLICATION
the funny thing is that I am not using replication at all. I am using CDC.
To reduce the transaction log usage I run below statement every day since the problem started
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL,
@numtrans = 0, @time = 0, @reset = 1
Any idea what should I do to solve this problem and be back on a normal situation?
BTW, The server is SQL 2012 (11.0.2383)
Thanks
Javier Villegas |
@javier_vill | http://sql-javier-villegas.blogspot.com/
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

CDC uses the replication log reader agent and if you manually ran sp_repldone like that you lost information in your CDC capture. If the capture job can't keep up with the workload or is not running for CDC, you would have the exact problems you describe.
If you execute sp_repldone like that, you might as well disable CDC.
http://technet.microsoft.com/en-us/library/dd266396(v=sql.100).aspx
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog |
Twitter |
MVP Profile
Training |
Consulting |
Become a SQLskills Insider
Troubleshooting SQL Server

Shrink Transaction log file - - - SAP BPC NW

HI friends,
We want to shrink the transaction log files in SAP BPC NW 7.0, how can we achieve thsi
Please can you throw some light on this
why we thought of ghrinking the file ?
we are getting "out of memory " error when ever we do any activity. so we thought of shrinking the file (this is not a production server - FYI)
example of an activity where the out of memeory issueee appears
SAP BPC excel >>> etools >>> client options >>> refresh dimension members >>> this leads to a pop-up screen stating that "out of memory"
so we thought of shrinking the file.
Please any suggestions
Thank you and Kindest Regards
Srikaanth

HI Poonam,
Not only the excel is throwing this kind of message (out of memory) - the SAP note is helpful, if we have error in excel alone
But we are facing this error every where
We have also found out that our Hard disk capacity as run out of space.
we want to empty the log files and make some space for us.
our hard disk is now having only few MegaBytes now
we want to clear our all test data, log files, and other stuffs
Please can you recommed us some way
Thank you and Kindest regards
Srikaanth

Cancel the query which uses full transaction log file

Hi,
We have reindexing job to run every week sunday. During the last run, the transaction log got full and the subsequent transactions to the database got errorred out stating 'Transaction log is full'. I want to restrict the utilization of the log file, that
is, when the reindexing job reaches the utilization of the log file to a certain threshold automatically the job should get cancelled. Is there any way to get it.

Hi,
We have reindexing job to run every week sunday. During the last run, the transaction log got full and the subsequent transactions to the database got errorred out stating 'Transaction log is full'. I want to restrict the utilization of the log file, that
is, when the reindexing job reaches the utilization of the log file to a certain threshold automatically the job should get cancelled. Is there any way to get it.
Hello,
Instead of Putting limit on trn log it would be good to find out cause causing high utilization.Even if you find that your log is growing because of some transaction it would be a blunder to rollback its little easy to do it for Index rebuild but if you
cancel for some delete operation you would end up in mess.Please don't create a program to delete or kill running operation.
You can create custom job for alert for trn log file growth.That would be good.
From 2008 onwards Index rebuild is fully logged so sometimes it causes trn log issue.To solve this either you run index rebuild for specific tables or for selective tables.
Other option is widely accepted Ola Hallengren script for index rebuild.I suggest you try this
http://ola.hallengren.com/
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Recovering data using SQL transaction logs

Hi-If we have a backup of our HFM database (in SQL) as of 8am today, and we backup the transaction logs too, can we use them to restore the database in case of an issue. Example, the database gets corrupted or someone deletes the wrong data. Can we restore the backup and then use the transaction logs to recreate the activities since the backup? Would this work if some of those activities were data loads via FDQM?
just checking if it makes sense to do these transaction log backups in SQL as it relates to HFM 9.2.1
Thanks
Wags

If your company performs full backups at the close of business every Friday and differential backups every Monday through Thursday evening. You could include hourly backups of the transaction log during business hours. Assume a database failure at 11:05AM Wednesday. Under this strategy, you would use Friday's full backup and Tuesday's differential backup to restore the database to it's state at the close of business Tuesday. This resulted in a loss of two hours of data (9-11AM Wednesday). Using the transaction log backups, you could apply the 9AM and 10AM transaction log backups after the Tuesday differential backup to restore our database to it's state at 11AM Wednesday. Restoring all but five minutes of database activity.

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 ...

IPhones using activesync causing excessive transaction log growth on Exchange 2010

Hi there.
We have around 60 iPhone or iPad users who are retrieving their emails from our Exchange 2010 SP2 servers using activesync.
Back when everyone was using the 3GS this worked just fine but late in 2011 we noticed that the transaction logs on our exchange servers were growing out of control. They should be roughly two times the volume of emails sent or received but all of a sudden we were getting fourty times as many! We only send just over 1GB of emails per week but have 50GB of transaction logs in that time.
I've spent ages trying to track down the cause and have an open TAC case with Microsoft that's been dragging on for several months now. We have recently proved that it's activesync causing the log growth - disable it and everything returns to normal - but they don't seem to be in any rush to identify a fix and I suspect their answer will be "Stop using iPhones".
Has anyone else seen this behaviour before and if so did you find a fix?
I was hoping iOS 6 might provide a solution but I'm reluctant to get everyone to upgrade because of the well publicised problems with maps and now I see that there are different Activesync bugs involving cancellation of meeting requests.
Anyone who can provide me with a resolution will win a prize as I'm at my wits end here.
Thanks

I have seen the issue twice in two weeks. Two different users, the commonality is both an iphone, and an ipad. In both cases the ipad was on wifi. I was able to turn on device logging in the ECP and in 20 minutes captured over 1 MB log on i-pad. I disabled the i-pad via the ecp and issue disipated.
When I reviewed the log the content that was being sync'd was over 5 months old. I instructed the user to back off to 30 days. Device is still stable, and the 30 days is just a temporary solution. I have opened a case with Microsoft for further review of the session log. What is interesting is that the log is consumed with a particular fetch and message class: ipm.note.eas <- EAS is the Exchange Archiving System stub created by Zantaz. I confirmed with our admin that we did not do any sync on the EAS server. I am looking into if the User initiated an Outlook resync of stubs.
<Fetch>
     <ServerId>8:19930</ServerId>
     <Status>1</Status>
     <ApplicationData>
      <To xmlns="Email:" bytes="50"/>
      <From xmlns="Email:" bytes="35"/>
      <Subject xmlns="Email:" bytes="18"/>
      <DateReceived xmlns="Email:">2012-08-26T04:01:29.964Z</DateReceived>
      <DisplayTo xmlns="Email:" bytes="16"/>
      <ThreadTopic xmlns="Email:" bytes="14"/>
      <Importance xmlns="Email:">1</Importance>
      <Read xmlns="Email:">0</Read>
      <Body=4502 bytes/>
      <MessageClass xmlns="Email:">IPM.Note.EAS</MessageClass>
      <InternetCPID xmlns="Email:">1252</InternetCPID>
      <Flag xmlns="Email:"/>
      <ContentClass xmlns="Email:">urn:content-classes:message</ContentClass>
      <NativeBodyType xmlns="AirSyncBase:">3</NativeBodyType>
      <ConversationId xmlns="Email2:">BEF20C7413954F8DAC2C558F7AE26FF0</ConversationId>
      <ConversationIndex xmlns="Email2:">CD8206EA510011DCEC00FFFF9F122F8002B86D80</ConversationIndex>
      <Categories xmlns="Email:"/>
     </ApplicationData>
    </Fetch>
device details:
Device OS:
iOS 6.0.1 10A523
Device language:
en
User agent:
Apple-iPhone4C1/1001.523
Device OS:
iOS 6.0.1 10A523
Device language:
en
User agent:
Apple-iPad3C2/1001.523

"The transaction log for database 'speakasiaonline' is full." I'm getting this message when I m trying to login to speakasia website and am unable to open it. Pl help.

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

What does it return?
SELECT log_reuse_wait_desc FROM sys.databases WHERE database_id=2
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Transaction log used 200GB unable to shrink

Similar Messages

Maybe you are looking for