SQL log file

Hi guys. I know this is not adapted for this forum, but could anybody show me a way to read SQL server log(.ldf) files. have already tried SQL log Rescue, Apex SQL. I am trying to read a log file that got muh bigger in a couple of days. These 2 softwares do not seem to work

No. Go ask your question on an SQL forum.

Similar Messages

SQL LOG FILE SIZE INCREASING

Hi DBA's
SQL Log file size occupies more disk space on the server, the overall database size is 8GB
How to decrease the SQL LDF file size on the server, please explain the suitable steps to perform
Thanks
DBA

use master
go
dump transaction <YourDBName>
with no_log
go
use <YourDBName>
go
DBCC SHRINKFILE (<YourDBNameLogFileName>,
100) -- where 100 is the size you may want to shrink it to in MB, change it to your needs
go
-- then you can call to check that all went fine
dbcc checkdb(<YourDBName>)
Andy ,
what point in asking user to use No_log and you did not even motioned about what this eveil command will do. Actually its
seriously not required reason being initial size of log file set to 8 G.
Plus what is point in running checkdb ?
I don't agree to any part you pointed
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

CPO SQL Log Files

Hey guys
We have started to see an exponential growth in our SQL log files that is in direct correlation with running more processes more consistently.
Has anyone had any issues with running a log truncating script to both the TEO_processlog and TEO_reportinglog files?
something along the lines of
ALTER DATABASE ExampleDB SET RECOVERY SIMPLE
DBCC SHRINKFILE('ExampleDB_log', 0, TRUNCATEONLY)
Thanks
Matt

Matt,
Yes, many people (if they do not need the t-logs) will reduce them. In 3.0 (during install) you can actually set it to SIMPLE mode instead of the more full recovery mode. I do that on most all of my boxes. Prior to CPO 3.0 you would have to do it like you show above.
On most of my pre 3.0 boxes I would do something like
USE <TEOProcess_DB_Name>;GO
-- Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE <TEOProces_DB_Name> SET RECOVERY SIMPLE;GO
-- Shrink the truncated log file to 1000MB.
DBCC SHRINKFILE ("<TEOProcess_log_file_name>", 1000); GO
Of course this is on SQL only. You can find more information on DBCC Shrinkfile at Microsoft's help site.
If you need to reset the database to full mode it's:
-- Reset the database recovery model.
ALTER DATABASE <TEOProcess_DB_Name> SET RECOVERY FULL;GO
--Shaun

SMS_NOTIFICATION_SERVER process Active Transaction preventing SQL log file backup

Hello,
I have been working on adding a few thousand machines into our SCCM 2012 R2 environment. Recently after attaching several of these systems there was a spike in activity in the transaction log due to the communication and inventory of these new
machines. The log file would fill up quickly but the log file backup would not function and allow the reuse of the log file. Upon investigation by my DB Admin we noticed that the SMS_NOTIFICATION_SERVER process was holding open an Active Transaction
that would last 1 hour and then restart at the end of the hour. This process was essentially preventing the backup of the log file. In a test, I briefly turned off the SMS_NOTIFICATION_SERVER process and we noticed the transaction log file functioning
correctly. I have included a screen shot of the process in the SQL Activity Monitor. Has anyone experienced this issue and resolved it? Is there anyway to reduce the 1 hour time frame or change the behaviour so that the process releases the
log file for backup if the log is getting full?
Regards,
Dave

We had it in Simple only briefly yesterday when working on the issue. It is in Full recovery mode.

SQL log file size is extending rapidly

Hello All,
We are using ECC 6.0, our database is SQL 2005 & operating system is Windows NT 4x AMD64 L.
Our database log file size is increasing rapidly, now its size is more than the all 4 data files (near about 300gb).
Last week I tried to shrink log file but it didn't worked.
Now less space is remained on disk, please help me.
Now the system is started giving dump at the time of log in, & the dump is like "START_CALL_SICK ".
I am attaching dump error text file.
Please help why is this happening.
Thanks in advance
Mahendra

Hi,
I have backed up log file & shrink the file but it didn't worked for me
What is the result? It shrinks the log and release all the space (for all committed transactions).
How can i add another log file?
Can i delete old log file after adding new log file.
You can add another log file by following below steps. but in your case, this is not the right solution because you have good amount of log file configuration for your database (now its size is more than the all 4 data files (near about 300gb)).
Open SQL server management studio > Expand database > Right click on database > Select Files > Click on Add > Give the input parameters (Logical file name, path, initial size etc.) click on OK
If system is not allowing you to shrink the log file, it means you have active transactions in system which are continuously using your log file.
Regards,
Nick Loy

Raid levels for sql server files

Hi,
I have a doubt on raid levels.
What RAID level should be used for SQL Data files and why?
What RAID level should be used for SQL LOG files and why?
What RAID level should be used for Tempdb files and why?
Thank you.

SQL Log File - The I/O is sequential in nature but only if you have a single database on the raid group of disks. If you have 2 or more database each doing its sequential pattern, you result having random I/O on the raid group.
SQL Data files - yes they are random in nature and could be write intensive but consider that SQL Server writes synchronously only in the log file, the writes on the data files are made in background by lazy writer and check point so it is not mandatory
to have RAID10, I will always choose RAID 5. The write penality of the RAID5 does not affect performances.
One last consideration: modern storage do "wide striping" i.e. they spread I/O operation on a pool of raid group. Every read/write operation first hit the cache of the storage (battery protected RAM) if the cache has not the blocks needed by the
rad operation or has not the amount of space to satisfy the write operation, the I/O is demanded to the disks...
Work with your storage admin if you have one and ask him to do cache partitioning and reserve some only for SQL Server log, you will be amazed by the gain in performances...

BPC log files very large

Hi All,
our BPC log files are very large compared to the data files. our
we have separate disks for data and log files:
DATA D:\ = 550GB total
LOG E:\ = 278GB total
D:\ICTSI_BPC.mdf = 5.6GB
E:\ICTSI_BPC_log.ldf = 185GB
is this correct? i have read that Log file should roughly be 25% of the
size of the total amount of data. Example: a 4GB database should have a
1GB log file. How can we adjust the size of the SQL log file?
we are using a multiserver set up, SAP BPC 7 SP04 (32bit)
MS SQL 2008 Server (64 bit)
thanks in advance!

Hi Jeb,
Do you already backup the database from the SQL Server ? Because in my server there is once when the log file is bigger then my database and that's because the backup schedule is not working.
So what i do is , do the backup manual from the sql server and the log file will shrink automatic.
After that , i create the automatic backup schedule again.
Hope this information helps.
Suprapto

Logical sql in log file.

Can someone please tell me how to see the complete sql query in the log file. If I run the same query the sql is not being produced I looked in the server log file and also manage sessions log file. It just says all columns from 'Subject Area'. I want to see all the joins and filters as well. Even for repeated queries how can I see complete sql. I set my logging level to 2.

http://lmgtfy.com/?q=obiee+disable+query+caching
http://catb.org/esr/faqs/smart-questions.html#homework

How to configure log files in SQL 2012?

I'm installing a SharePoint Solution and using Microsoft SQL 2012 and I have limited knowledge in installing SQL. I simply run the wizard and create the DB for SharePoint.
Is there any links/materials available demonstrating how to correctly configure the log files step by step in a specific partition during the SQL installation for SharePoint 2013?
thanks,

Hello,
SQL Server database log files benefit from RAID 1 and RAID 10 configurations. RAID 10 is recommended for both data files and log files.
To control de grow of transaction log files, please backup them regularly. The following article may explain you in detail why:
http://technet.microsoft.com/en-us/library/ms175495.aspx
Monitor the growth of log files using Performance Monitor and the SQLServer:Databases --> Log Growths counter. Adjust the size of log files until Log Growths
is constantly zero.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Moving the log file of a publisher database SQL Server 2008

There are many threads on this here. Most of them not at all helpful and some of them wrong. Thus a fresh post.
This post regards SQL Server 2008 (10.0.5841)
The PUBLISHER database primary log file which is currently of 3 blocks and not extendable,
must be moved as the LUN is going away.
The database has several TB of data and a large number of push transactional replications as well as a couple of bi-directional replications.
While the primary log file is active, it is almost never (if ever) used due to its small fixed size.
We are in the 20,000 TPS range at peak (according to perfmon). This is a non-trivial installation.
This means that
backup/restore is not even a remotely viable option (it never is in the real world)
downtime minimization is critical - measured in minutes or less.
dismantling and recreating the replications is doable, but I have to say, I have zero trust in the script writer to generate accurate scripts. Many of these replications were originally set up in older versions of SQL Server and have come along for the
ride as upgrades have occurred. I consider scripting everything and dismantling the whole lot pretty high risk. In any case, I do not want to have to reinitialize any replications as this takes, effectively, an eternity.
Possible solution:
The only option I can think of is to wind down everything, such that there are zero outstanding uncommitted transactions and detach the database, delete the offending log file and reattach using the CREATE DATABASE xyz ATTACH_REBUILD_LOG option.
This should, if I have understood things correctly, cause SQL Server to recreate the default log file in the same directory as the .mdf file. I am not sure what will happen to the secondary log file which is not moving anywhere at this point.
The hard bit is insuring that every transaction in the active log files have been replicated before shutdown. This is probably doable. I do not know how to manually flush any left over transactions to replication. I expect if I shut down all "real"
activity and wait for a certain amount of time, eventually all the replications will show "No replicated transactions are available" and then I would be good to go.
Hillary, if you happen to be there, comments appreciated.

Hi Philip
you should try this long back suggested way of stopping replication and restore db and rename or detach attach
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6731803b-3efa-4820-a303-4ffb7edf154a/detaching-a-replicated-database?forum=sqlreplication
Thanks
Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem
I do not wish to be rude, but which part of the OP didn't you understand?
Specifically the bit about 20,000 transactions a second and database size of several TB. Do you have any concept whatsoever of what this means? I will answer for you, "no, you are clueless" as your answer clearly shows.
Stop wasting bandwidth by proposing pointless and wrong solutions which indicate that you did not read the OP, or do you just do this to generate points?
Also, you clearly failed to notice that I was on the thread to which you referred, and I had some pointed comments to make. This thread was an attempt to garner some input for an alternative proposal.

Unable to view SQL Request in Log files

Hi Folks,
I am facing an issue which I am unable to find out the solution to view the physical query generated in log files in Presentation Services.
Below is the SQL Request generated but I want to view the exact physical query i.e SQL Request which is hitting DB.
So please guiude me to resolve this issue, I guess it is because of Initialization blocks created which is blocking to view the SQL request.
-------------------- SQL Request:
set variable LOGLEVEL = 7;SELECT "- Policy Effective-Start Date"."Start Quarter" saw_0, "- Insurance Policy Facts".Revenue saw_1, "- Insurance Policy Facts"."# Insurance Policies" saw_2, "Insurance Policy".Status saw_3, "Insurance Policy".Type saw_4 FROM "Insurance Policies" WHERE ("Insurance Policy".Type = 'Policy') AND ("- Policy Effective-Start Date"."Start Julian Day Number" BETWEEN VALUEOF(CURRENT_JULIAN_DAY)-365 AND VALUEOF("CURRENT_JULIAN_DAY")) ORDER BY saw_0, saw_3, saw_4
/* QUERY_SRC_CD='rawSQL' */
Regards
Dj

There is no Enterprise Edition of SSMS. There is SSMS Basic and SSMS Complete. Prior to 2012 sp1, only SSMS Basic were available with Express Edition - but as of 2012 sp1 Expredd also offers SSMS Complete. SSMS Complete is selected bu default when you install
SSMS (unless you are prior to 2012 sp1 and are using Express, of course).
However, even SSMS Basic *should* show Agent assuming you have permissions for that. This is hearsay, but from trusted sources. Here is what to do:
Check what is installed for the machine from where you are running SSMS. You can do that using SQL Server Installation Center - see this blog post: http://sqlblog.com/blogs/tibor_karaszi/archive/2011/02/10/what-does-this-express-edition-look-like-anyhow.aspx
(towards the end).
On that machine try both this problematic account as well as an account which is sysadmin. Does the sysadmin account see Agent? If so, you know permissions aren't granted properly. If not, then you know the tool is the problme.
Also try the problematic account from a machine where you know you see Agent normally. Again, this will help you assess whether the problem is the tool (SSMS) or permissions for the account.
Tibor Karaszi, SQL Server MVP |
web | blog

Error in sql_engine_core_inst_Cpu64_1.log file for SQL Server 2012

I was running SQL Server 2012 in Win 7 64 bit OS. Some how I found SQLSERVER server is not running and I was not able to run the service. Then I tried to unisntall and install again. And I found that some of the SQL Server
features got failed, like: Reporting Services - Native, Database Engine Services, Data Quality Services, Full-Text and Semantic Extractions for Search and SQL Server Replication. I checked the Summary.txt
file from location C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log. It thsi logs referes to another log file location like:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140127_151409\sql_engine_core_inst_Cpu64_1.log
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639
I did unisntall/install multipel times. But fhw to fix the issue that saying in sql_engine_core_inst_Cpu64_1.log file.:
=== Verbose logging started: 1/27/2014 15:45:04 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\ScenarioEngine.exe ===
MSI (c) (C4:BC) [15:45:04:321]: Resetting cached policy values
MSI (c) (C4:BC) [15:45:04:321]: Machine policy value 'Debug' is 0
MSI (c) (C4:BC) [15:45:04:321]: ******* RunEngine:
******* Product: E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
******* Action:
******* CommandLine: **********
MSI (c) (C4:BC) [15:45:04:322]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (C4:BC) [15:45:04:322]: Grabbed execution mutex.
MSI (c) (C4:BC) [15:45:04:323]: Cloaking enabled.
MSI (c) (C4:BC) [15:45:04:323]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (C4:BC) [15:45:04:323]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:8C) [15:45:04:327]: Running installation inside multi-package transaction E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
MSI (s) (38:8C) [15:45:04:327]: Grabbed execution mutex.
MSI (s) (38:A0) [15:45:04:327]: Resetting cached policy values
MSI (s) (38:A0) [15:45:04:327]: Machine policy value 'Debug' is 0
MSI (s) (38:A0) [15:45:04:327]: ******* RunEngine:
******* Product: E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
******* Action:
******* CommandLine: **********
MSI (s) (38:A0) [15:45:04:452]: Machine policy value 'TransformsSecure' is 0
MSI (s) (38:A0) [15:45:04:452]: User policy value 'TransformsAtSource' is 0
MSI (s) (38:A0) [15:45:04:475]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (38:A0) [15:45:04:475]: Specified instance {18B2A97C-92C3-4AC7-BE72-F823E0BC895B} via transform :InstID01.mst;:InstName02.mst is already installed. MSINEWINSTANCE requires a new instance that is not installed.
MSI (s) (38:A0) [15:45:04:475]: MainEngineThread is returning 1639
MSI (s) (38:8C) [15:45:04:477]: User policy value 'DisableRollback' is 0
MSI (s) (38:8C) [15:45:04:477]: Machine policy value 'DisableRollback' is 0
MSI (s) (38:8C) [15:45:04:477]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:8C) [15:45:04:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:8C) [15:45:04:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:8C) [15:45:04:478]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (38:8C) [15:45:04:478]: Restoring environment variables
MSI (c) (C4:BC) [15:45:04:481]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (C4:BC) [15:45:04:481]: MainEngineThread is returning 1639
=== Verbose logging stopped: 1/27/2014 15:45:04 ===
Please advice. I searched many places and did not get actual solution that will resolve my case.
Nusrat Akhter

Hi Nusrat Akhter,
According to your description, when installing the first install failed, and it looks like the instance did not uninstall completely. To solve the issue I recommend you changed the instance name in re-installing SQL Server, and check if it can work fine.
There is a similar issue that the SQL engine will not start, and there is no method of uninstalling either it, or any of the components etc. You can review the following post.
https://connect.microsoft.com/SQLServer/feedback/details/710892/sql-server-2012-rc0-install-fails-citing-invalid-drivers
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

Hello,
I am glad it worked.
Thank you for visiting MSDN forums!
Regards,
Alberto Morillo
SQLCoffee.com

Odi 11g - IKM SQL to Hyperion Essbase (DATA) log file always empty

In odi 11g when using *"IKM SQL to Hyperion Essbase (DATA)"* setting the the "LOG_ENABLED" = true,
only an empty file are generated.
Just "LOG_ERRORS" file (if errors occurs) are created.
Is this just an my issue?
Can someone help me?
p.s.: the same issue, I got even with the *"IKM SQL to Hyperion Planning"*
Thx in advance, Paolo

Thanks John for your suggestion.
here the patch *"Patch 10302682: IKM SQL TO PLANNING: LOG FILE IS CREATED BUT NOTHING INSIDE."*
I didn't see any other about Essbase...
I try to check all day on support site.
Paolo
Edited by: Paolo on 19-apr-2011 8.44

Steps to move Data and Log file for clustered SQL Server

Hi guys
we have Active'passive SQL 2008R2 cluster environment.
looking for steps to move Data and log files from user Database and System Database for SQL Server Clustered Instance.
Currently Data and log files resides on same drive for user and system Databases..
Thanks
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

Try the below link
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/468de435-3432-45c2-a50b-23519cd2686e/moving-the-system-databases-in-a-sql-cluster?forum=sqldisasterrecovery
-Prashanth

SQL log file

Similar Messages

Maybe you are looking for