In SQL Server Management Studio, in Object Explorer > Management, there is a setting if you right click on SQL Server Logs and select Configure. You can specify how many log files you want to keep. Once it reaches that number it will start removing the old ones.
There are 3 different items in this question:
Incomplete startup packet occuring at server start is inconsequential, you may ignore it. Read Incomplete startup packet help needed (in pgsql-general mailing-list) for more.
syntax error at or near "exit" at character 1 means that a client issued exit as if it was an SQL statement.
The could not exec error when ...
Memory architecture was changed in SQL Server 2012 such that there was little need to worry about the MemToLeave setting anymore, especially if using 64-bit SQL Server. And, starting with SQL Server 2016 (which you are using), SQL Server is only available in 64-bit (see the "Note" at the top of the "What's new in Database Engine - SQL Server 2016" page). So, ...
When an error log is considered to be "big"? Some of our logs take long to load, close to a million of rows.
This is going to be different for certain scenarios, but with your description ("Some of our logs take long to load"), that's my definition of big. When file operations (copying, moving, etc.) start to take a little longer than instant, or parsing an ...
Given that at 2/16/2014 12:23:46 AM the error message states that the instance has been using a process ID since 9/19/2014, I would suspect the system clock was rolled back after the instance startup. If this would be true we would also expect SSPI handshakes to fail due to clock difference between parties, and sure enough there are SSPI failures logged ...
Restart SQL Server 7 times. You will see you still have only 7 ERRORLOG* files (depending on version). This is the current log file and the 6 most recent log files.
Note: You may need to change 7 to something else, in the event you changed the number of error logs SQL Server keeps. The max, I believe, is 99. But no matter what your current setting is, it ...
If you run EXEC sys.sp_enumerrorlogs; it will return one row for each log file, the oldest date in the log file, and the log file size.
Which means you can do something like this:
CREATE TABLE #error_log
INSERT #error_log ( log_number, log_date, log_size )
EXEC ( 'EXEC sys.sp_enumerrorlogs;' );
Bad queries and other invalid actions typically only write to the error log when there's not a client connection to write the error to... such as when a thread that isn't a client thread encounters an error... or from the event scheduler.
From within a scheduled event, SIGNAL can be used to throw errors and warnings that will be written to MySQL's error log....
Seems like you have an activation procedure that explicitly outputs the string y (probably using print but possibly raiserror, select, or output).
Why don't you change the procedure so that it doesn't have any output? Output shouldn't be needed when run through service broker. Or if the procedure is also sometimes run interactively, and output is required ...
SQL Server recycles error logs automatically, as long as you configure it correctly.
See http://msdn.microsoft.com/en-us/library/ms177285.aspx . I've copied the salient points below:
In Object Explorer, expand the instance of SQL Server, expand Management, right-click SQL Server Logs, and then click Configure.
In the Configure SQL Server Error Logs ...
Might look into this:
https://docs.microsoft.com/en-us/sql/relational-databases/memory-management-architecture-guide. Especially the query on what's currently allocated. It will give you somewhere to focus diagnostics on.
I've had this problem before, and it ended up being repeated calls to a CLR procedure that would never close itself down when it was ...
Thats about 25% of the server space.
First and foremost, you really need to increase the size of your drive or move the error logs to a different drive. ~40GB for a C:\ drive might've been an okay default years ago, but you can quickly burn through that with misc files from applications - as you're seeing.
You can easily configure this via SQL Server ...
In the end, it was only after changing my hosting plan (and moving away from cPanel, which seemed to obscure some of the logging) that I was able to see the issue. Turns out that from time to time, memory usage would spike (I'm guessing that this was because of a dramatic spike in apache child processes) and this would cause memory pressure. The out-of-...
Because there are only 8208 pages allocated to MEMORYCLERK_SQLLOGPOOL in the excerpt not sure kb2769594 is the culprit/fix.
Also no reference to internal pool or HADR as in the kb2769594 example.
So I think culprit/fix may be something else.
Surprising that no large pages allocated at all - I'd expect some for non-...
Yes, this is possible by creating a user with 'securityadmin' server role and then if required Deny his access to SQL Server Query Window through LOGON Trigger
CREATE LOGIN [DBA_ErrorLogUser]
WITH PASSWORD=N'123', DEFAULT_DATABASE=[master],
--- Add ...
I would assume it's more likely that the procedure sp_cycle_errorlog was called. There's a possibility someone accidentally right clicked on Error Log and then clicked Recycle instead of Configure which also calls this procedure.
What I would do is create an audit event on this procedure for the future so you can see how this occurs. If you do have some SQL ...
This is expected behavior with TRY/CATCH in T-SQL. The related Connect bug report was closed as "won't fix":
You'll need to use a client application (e.g. SQLCMD, PowerShell) to capture all error messages.
I don't have an answer for what exactly they mean, but I see them on every machine where I have a memory optimized file group.
Since they start with "HK" they seem to be related to In-Memory OLTP (codenamed Hekaton prior to the production release in SQL Server 2014).
I would say that since they are INFO messages, and they are common on instances with ...
Fixing this required changing the WAL record format for tuple
freezing. While this is no issue for standalone servers, when using
replication it means that standby servers must be upgraded to 9.3.3 or
later before their masters are. An older standby will be unable to
interpret freeze ...
For future readers :
The last integer describes the AG state
0 - Not Joined to AG
1 - Not Synchronized
2 - Suspended
4 - Synchronized
8 - Redo (redoing log)
Ref : DbMgrPartnerCommitPolicy::SetSyncState May Seem More Mysterious than It Actually Is
Just to provide another answer. I just ran into the same error messages and this issue seems to be related yet not the same issue fixed in the KB linked in the other 2 answers.
The error messages you get seem to indicate the same, but in your case (and mine) it's not MEMORYCLERK_SQLLOGPOOL that's taking a lot of memory but MEMORYCLERK_XE that's taking up ...
Have you ever considered converting the slow log into a MyISAM table?
As for MySQL 5.1.30, you can choose the format of the slow log and general log as either TABLE or FILE by means of the log_output option. It is also available in MySQL 5.5.
To support the TABLE option for log_output, MySQL provided two tables:
For the ...
From System Error Codes (1300-1699): OS error 1392 indicates file corruption.
The file or directory is corrupted and unreadable.
So it looks like you have corruption on your G: drive.
I would start with a chkdsk of that drive and all other drives.
Since corruption usually doesn't fix itself and can have the tendency ...
You can easily extract that information from the default trace:
DECLARE @path nvarchar(4000);
SELECT @path= path
WHERE id = 1;
SELECT TextData, HostName, ApplicationName, LoginName, SPID, StartTime
FROM fn_trace_gettable(@path, DEFAULT)
WHERE TextData LIKE '%xp_cmdshell%';
Windows patching and majid's solution is what worked for us too. Just adding my 2c that may help others. We have a cluster with 2008, 2014 SP2 and 2016 CU2. After upgrading an instance to 2016, we had the following errors:
2014 and 2016: syspolicy_purge_history job failed on step 3
2016: SQL agent would start then stop
2016: Couldn't view SQL error logs
SQL Error Log, how do I determine the most appropriate error log size?
Whatever is above the "normal" for each individual environment. Some environments require the logging of successful and unsuccessful logins to the errorlog, obviously that's going to bloat the log if it's a highly chatty server. Other environments are required to have backup information ...
Alright, I have a resolution maybe, and an explanation for the log entries.
Following the advise of @John-Eisbrener & @Danielle-Paquette-Harvey (did I do the attribution right?) In particular John's advise of a different user for Crystal I learned the following.
Issue: Log entries that say that the user (sa originally) has entered bad credentials.
SQL Server in your case is patched to SP1. Microsoft has released SQL Server 2012 SP2 and there was fix for such type of errors.
As per Microsoft Article reason is
Microsoft SQL Server 2012 may experience some out-of-memory errors
because of an internal memory leak. In this situation, the leaked
memory is consumed by the MEMORYCLERK_SQLLOGPOOL ...