Sql server log shipping space consumption

I have implemented sql server logs shipping from hq to dr server
The secondary databases are in standby mode .
The issue is that after configuring it , my dr server is running out of space very rapidly
I have checked the log shipping folders where the trn files resides and they are of very decent size , and the retention is configured for twenty four hours
I checked the secondary databases and their size is exactly same as that of the corresponding primary databases
Could you guys please help me out in identifying the reason behind this odd space increase
I would be grateful if you could point me to some online resources that explains this matter with depth

The retention is happening . I have checked the folders they do not have records older then 24 hours .
I dont know may be its because in the secondary server (Dr) there is no full backup job working , is it because of this the ldf file is getting bigger and bigger but again I far as my understanding goes we cannot take a database full backup in the stand
by mode .
The TLog files of log shipped DBs on the secondary will be same size as that of primary. The only way to shrink the TLog files on secondary (I am not advising you to do this) is to shrink them on the primary, force-start the TLog backup job, then the copy
job, then the restore job on the secondary, which will sync the size of the TLog file on the secondary.
If you have allocated the same sized disk on both primary and secondary for TLog files, then check if the Volume Shadow Copy is consuming the space on the secondary
Satish Kartan www.sqlfood.com

Similar Messages

I see most recent file is called sql server log shipping work file

What is "SQL server log shipping work file"?

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/62a6556e-6655-4d19-9112-1788cf7bbcfc/wrk-file-in-logshipping-2005
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

Sql Server Log shipping

Hi,
We have configured log shipping in our production setup. Now we are planning to change the service account from local system on which SQL Server is running to to other domain account.
Pls let me know changing the service account would have any impact on Log Shipping.
Regards,
Varun

Hi n.varun,
According to your description, about startup account for SQL Server and SQL Server Agent Services on Log Shipping Servers, if you have placed SQL Servers in a domain, Microsoft recommends that you use a domain account to start SQL Server services. As other
post, the domain account has full control permissions on the shared location and is sysadmin role in SQL Server security. Even if
you change the account form Local System to the domain account in SQL Server Configuration Manager (SSCM), it would have no impact on Log Shipping.
In addition, if you configure SQL Server Log shipping in a different domain or workgroup, we need to verify that the SQL Server Agent service account running on the secondary server must have read access to the folder that the log backups are located in,
and has permissions to the local folder that it will copy the logs to, then in secondary server, we can change the SQL Server Agent from using Local System to the domain account you are configuring. For more information, see:
http://www.mssqltips.com/sqlservertip/2562/sql-server-log-shipping-to-a-different-domain-or-workgroup/
There is an detail about how to configure security for SQL Server log shipping, you can review the following link.
http://support.microsoft.com/kb/321247
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

2012 SQL server log shipping problem

Scenario:
Site 1: 2012 Enterprise version 64-bit (11.0.3128.0) - Log shipping is enabled for four databases. Shipping logs over a WAN every 15 minutes to a DR site.
Site 2: 2012 Enterprise version 64-bit (11.0.3128.0) - Secondary server for log shipping.
Site two functions for a period of time with the databases in Standby/Read-Only mode, then the databases will mysteriously switch to "restoring..." mode and error 14420 Severity 16 State 1 will appear in the logs. I have located kb2987585
and this did apply to the situtation as the sector sizes were different, so as a work around I moved the log shipping shared folder on the secondary server to a drive with the same sector settings as the primary server but this did not resolve the issue.
Has anyone had this issue and can you offer potential solutions?
Thank you -

Hi,
I still consider the bug raised in
https://support.microsoft.com/kb/2987585?wa=wsignin1.0
is not fixed. I have seen lot of other users complaining. But at this point I need to have look at SQL Server errorlog
sp_readerrorlog
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

SQL Server Logs

Hi,
I am getting an errors in SQL Server Logs.
Its eating up all my space from C: Drive.
now it says 0 bytes left.
What could be an issue???
Please help. its urgent.
Regards, Kunjay Shah

Hello,
Meanwhile you can limit the error log size with the following instruction:
USE
[master];
GO
EXEC
xp_instance_regwrite
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'ErrorLogSizeInKb',
REG_DWORD, 5120;
GO
For more information, please read the following article:
http://support.microsoft.com/kb/2199578/en-us
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Crystal Report 2008 results "Password did not match error" in SQL Server Log

Hi,
I am trying to develop some crystal reports using Crystal Report 2008 SP4 to connect to SQL server 2008 through RDO (ODBC). My problem is that anytime Crystal Report is trying to establish a connection with SQL Server, first it tries to connect with the wrong password and results the following error message in SQL Server log:
Login failed for user 'peyman'. Reason: Password did not match that for the login provided. [CLIENT: 192.168.2.198]
The login name 'peyman' is the right one as I have quoted the same in setting up ODBC System DSN using "SQL Server Native Client 10". But somehow Crystal Report is taking its chance and trying to connect before prompting me for the password. After this error logged to SQL server side, I can see Crystal Report pops up the prompt to enter DSN password. After supplying password to this prompt, Crystal Report works fine and pulls the data and renders the report without having any more incorrect password error logged to SQL Server.
The attached file shows the step I am taking to regenerate the issue. I need this to be fixed as anytime uses any of these reports and tries to render it with crystal runtime engine the same error message raises in SQL Server side and logged in the log file.
Thanks,

Hi Peyman,
This is the way it should work, In CR designer when you open the report it does nothing. As soon as you hit the Refresh button then CR tries to use the connection saved with the report. It assumes what is saved with the report is a valid server and connection info. CR simply tries to verify the server is still active.
If you don't want it to fail in CRD then before opening any report Click the File, Log on Database option and connect. Now when refreshing reports it won't log the failed.
In the SDK it does the same thing, it assumes the Server info is the same and does try to connect to verify the Server does exist. It only takes a few milli-seconds to do this
To stop this from happening set the log on info first then it won't log the attempt to connect, it's checking to see if Trusted is allowed.
TIMESTAMP    THREAD_ID    FILENAME    LINE_NUMBER    LOGGED_DATA    LEVEL
2014-6-2 8:30:11.439    57320    .\QESession.cpp    444    Set Product View Locale: 4105    20
2014-6-2 8:30:11.439    57320    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
2014-6-2 8:30:11.439    57320    .\QESession.cpp    500    Set Process Locale: 4105    20
2014-6-2 8:30:11.440    57320    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
2014-6-2 8:30:11.967    57208    .\QESession.cpp    444    Set Product View Locale: 4105    20
2014-6-2 8:30:11.967    57208    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
2014-6-2 8:30:11.967    57208    .\QESession.cpp    500    Set Process Locale: 4105    20
2014-6-2 8:30:11.968    57208    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
2014-6-2 8:30:11.999    57208    .\QESession.cpp    444    Set Product View Locale: 1033    20
2014-6-2 8:30:12.4    57320    .\qecommon.cpp    117    This value is write-only. File Name: ".\QEProperty.cpp". Line: 145    1
2014-6-2 8:30:56.278    57208    .\odbcapi.cpp    301    Beginning COdbcapi::DriverConnect    20
2014-6-2 8:30:56.342    57208    .\odbcapi.cpp    335    Ending COdbcapi::DriverConnect    20
2014-6-2 8:30:56.342    57208    .\connect.cpp    2170    SQLDriverConnect succeeded: DSN = 192.168.13.172, User ID = sa, Password = ********    10
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 916    1
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    1184    Beginning CQERowset::readFirstRecord    20
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2149    Beginning CQERowset::restart    20
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2370    Beginning CQERowset::execute    20
2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    514    Query Targets: sqlncli10, ODBC3SQLServer    10
2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    525    Successfully built query:    SELECT "Orders"."Customer ID", "Orders"."Employee ID"   FROM   "xtreme"."dbo"."Orders" "Orders"    10
2014-6-2 8:30:56.353    57208    .\odbcapi.cpp    875    Beginning COdbcapi::ExecDirect    20
2014-6-2 8:30:56.354    57208    .\odbcapi.cpp    884    Finishing COdbcapi::ExecDirect    20
2014-6-2 8:30:56.354    57208    .\rowset.cpp    220    SQLExecDirect succeeded: SELECT "Orders"."Customer ID", "Orders"."Employee ID" FROM   "xtreme"."dbo"."Orders" "Orders"    10
2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Customer ID is using client buffer    10
2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Employee ID is using client buffer    10
Notice it doesn't try to connect first if I set the log on info first using code.
So nothing we can do to stop SQL server from logging this info. Check with the DBA, possibly they can "filter" out the application attempts to connect or change your work flow in the app.
If you have a Preview Button to view the report then simply add your Database log on info prompt there if Connectioninfo.Trusted is not true:
mainSecureDB = rpt.Database.Tables[tableIndex].LogOnInfo.ConnectionInfo.IntegratedSecurity;
if mainSecureDB = false then prompt the user for log on info and set accordingly, if it is true the it should not fail when it connects.
This is simply a matter of changing your App work flow...
Thanks
Don

Possible to view MS SQL Server Log in SAP GUI?

Hi,
I am wondering if I can view the SQL Server log in SAP GUI using a transaction code.
I don't readily see how to do this with the TEs. It would be helpful to see things like: who has tried to log into the SQL Server via a Database Management tool : agnostic to SAP.: is SQL Server Management Studio or DBArtisan or other services.
thanks
Chris

Hi chris
Yes,you can view the Sql server log in transaction code ST04 & DBA Cockpit in SAPGUI.
Kindly refer the SAP notes.
139945 - SAP Database Monitor for MS SQL Server
1027512 - MSSQL: DBA cockpit for basis release 7.00 and later
Regards
Ram

"HadrLogCapture" messages in SQL Server Log

HI
After activating AlwaysOn High Availibility Groups in SQL Server 2012 R2 and adding databases at the availibilitygroup, SQL Server started genereting lots of messages in the SQL Server Logs.
Some example Messages are: "DbId (1466) log capture is rescheduled with partner generation: 45, log consumer id: 9828",
"HadrLogCapture::BuildMsgBodyForSend - DbId [2535]->[1807D374-DA55-4CAC-A831-AA3C3A8B8EC4] Send From
saved msg - LogBlockId (0x000221e800000010)"
Is there is a possibility to stop generating these messages?

I guess supressing them would be a wrong approach. there is some underlying problem with the data movement which you have between primary and secondary replicas.
Here are my questions:
What is the sync setting and how many replicas you have?
What is the SQL Version? Output of Select @@version query
Do you see any latency on Dashboard? Check if redo queue or log send queue is high
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

How to Open Or read SQL Server log file .ldf

Hi all,
How to Open Or read SQL Server log file .ldf
When ever we create database from sql server, it's create two file. (1) .mdf (2) .ldf.
I want to see what's available inside the .ldf file.
Thanks,
Ashok

I am not too sure but may be the below two undocumented commands might yield the desired result.
DBCC Log
Fn_dblog function
Refer these links for more info,
http://www.mssqlcity.com/Articles/Undoc/SQL2000UndocDBCC.htm
http://blogs.sqlserver.org.au/blogs/greg_linwood/archive/2004/11/27/37.aspx
http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1173464,00.html
Some 3rd party tools like Log Explorer can do the job for you.
http://www.lumigent.com/products/le_sql.html
- Deepak

SQL Server Log: Login failed for user ''

We've found in SQL Server Log many records:
Date
3/22/2013 11:13:03 AM
Log
Windows NT (Application)
Source
MSSQLSERVER
Category
Logon
Event
3221243928
Computer
SBO05
Message
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <local machine>]
The server autentification is set to "SQL Server and Windows Autentification mode". But when we open SAP, before entering login/password, we see this message in log. But we still could work in SAP.
How could we solve this?
Kind regards,
Anna Shevchenko

Hi Joseph,
It doesn't help. The same things i've already done.
But when I change Mixed Autentification to Windows, i see another error:
Date
3/22/2013 11:04:26 AM
Log
SQL Server (Current - 3/22/2013 12:33:00 PM)
Source
Logon
Message
Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.145]
Do you know why?
Kind regards,
Anna Shevchenko

Warning: Failure to calculate super-latch promotion threshold. appears in SQL Server log

We are running SQL Server 2008 R2 and have just applied Service Pack 2 to our QA environment.
Today we noticed this message in the SQL Server log:
Warning: Failure to calculate super-latch promotion threshold.
Can someone please tell us what this means and how to fix whatever it is?
There is no associated error message number.
We believe this message is new with Service Pack 2. Can someone tell us for sure?
This entry has occurred in the middle of the night when nothing was running that we could see and during the day.
Environment
SQL server 10.50.4000
Windows Server 2008 R2 Standard Service pack 1
Server has 4 processors, 8 Gig of Ram with 4 Gig set for SQL Server. Usage is generally light as it is a test environment.
KD

Its just a warning message about super latch .
Since SQL 2005 SuperLatches have been introducted which can enable increased performance for accessing the shared pages in the database for a multiple concurrency workload which intrun requires worker threads require SH (shared) latches. No need to set or
enable any configuration this is performed automatically/dynamically based on the mutli-CPU configuration to promote a latch on a page to be a super-latch. Then this SuperLatch partitions the single latch into array of sublatch structure per CPU core.
Super latches are way of promoting a latch for entire NUMA Node to reduce contention.
you can also read following detailed article
http://blogs.msdn.com/b/psssql/archive/2010/03/24/how-it-works-bob-dorr-s-sql-server-i-o-presentation.aspx
Soldier..Sir we are surrounded from all sides by enemy.. Major: Good, we can attack in any direction Thats attitude..

SharePOint 2010 - SQL Server - Logs filling up drive space so quickly - please help

Hi there,
On my DEV SharePoint SQL Server - suddenly the logs have been filling up space so quickly - this morning I increased 10 GIGs and now it is full again just in a few hours.
What action should I take?
- Is it okay to switch Recovery Model from Full to Simple? (It is DEV server)
- Anything else?
Thanks.

Hi frob,
Can please check below link , It might be useful.
https://support.microsoft.com/kb/110139?wa=wsignin1.0
http://www.mssqltips.com/sqlservertip/2092/sql-server-transaction-log-grows-and-fills-up-drive/
If you think is helpful,Vote As Helpful! And if you see a reply being an answer to the question of the thread, click Mark As Answer.
Mahesh

What does _total for instance mean in SQL server log space used alert

Hi,
I would like to know the meaning of specifying _total for instance when creating log space used alert in SQL server 2008R2 server.
Thanks,
Preetha

Hi,
‘_total’ means performance condition alerts are available for all the database and it monitors all the existing databases.
Check out the following TechNet article for more information about
performance condition:
http://technet.microsoft.com/en-us/library/ms180982.aspx
Thanks.
Tracy Cai
TechNet Community Support

SQL Server log table sizes

Our SQL Server 2005 (Idm 7.1.1 (with patch 13 recently applied), running on Win2003 & Appserver 8.2) database has grown to 100GB. The repository was created with the provided create_waveset_tables.sqlserver script.
In looking at the table sizes, the space hogs are:
Data space:
    log       7.6G
    logattr   1.8G
    slogattr 10.3G
    syslog   38.3G
Index space:
    log       4.3G
    logattr   4.3G
    slogattr 26.9G
    syslog    4.2GAs far as usage goes, we have around 20K users, we do a nightly recon against AD, and have 3 daily ActiveSync processes for 3 other attributes sources. So there is alot of potential for heavy duty logging to occur.
We need to do something before we run out of disk space.
Is the level of logging tunable somehow?
If we lh export "default" and "users", then wipe out the repo, reload the init, default and users what will we have lost besides a history of attribute updates?

Hi,
I just fired up my old 7.1 environment to have a look at the syslog and slogattr tables. They looked save to delete as I could not find any "magic" rows in there. So I did a shutdown of my appserver and issued
truncate syslog
truncate slogattr
from my sql tool. After restarting the appserver everything is still working nicely.
The syslog and slogattr tables store technical information about errors. Errors like unable to connect to resource A or Active Sync agains C is not properly configured. It does not store provisioning errors, those go straight to the log/logattr table. So from my point of view it is ok to clean out the syslog and slogattr once in a while.
But there is one thing which I think is not ok - having so many errors in the first place. Before you truncate your syslog you should run a syslog report to identify some of the problems in the environment.
Once identified and fixed you should'nt have many new entries in your syslog per day. There will allways be a few, network hickups and the like. But not as many as you seem to have today.
Regards,
Patrick

Repeated Errors in SQL Server log file

I have hundreds of these errors saying 'Login failed for user 'Reporting' The user is not associated with a trusted SQL Server connection [CLIENT: ip address]
The ip address is that of the server that sql server is installed on.
Looking in my log file, all looks good until I get to Service Broker manager has started, then I get Error: 18452, Severity: 14 State: 1 then these two lines repeat about every minute, for the last 3 days!
I think I must have just missed a tick box somewhere, but where?
I have been into one of the databases, and input and checked data, both via an application I wrote and SQL Server Management Studio.
I am also having trouble connecting using my application to connect to the database, I can only connect if I use a Windows administrator account (this SQL Server 2005 running on a Windows 2003 Server, with the app on PC running Windows 2000)

Hello Graham,
did you find any solutions for that problem? I'm discovering a similar problem. The state of my error message is 5. According to the following source http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx this means the user is not known. This is correct. Neither the SQL-Server nor the Windows system has such a userid.
The faulty user name is 'Reporting'. What is that user used for? I have set up other SQL Server 2005 servers but was never asked for such a name.
Greetings,
Frank

Sql server log shipping space consumption

Similar Messages

Maybe you are looking for