Skip to content

Instantly share code, notes, and snippets.

@TehWardy
Created November 20, 2019 19:04
Show Gist options
  • Save TehWardy/a471c5b48be3462033972ff834fcd5f3 to your computer and use it in GitHub Desktop.
Save TehWardy/a471c5b48be3462033972ff834fcd5f3 to your computer and use it in GitHub Desktop.
2019-11-20 18:13:43.78 Server Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)
Aug 22 2017 17:04:49
Copyright (C) 2017 Microsoft Corporation
Standard Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 18362: )
2019-11-20 18:13:43.79 Server UTC adjustment: 0:00
2019-11-20 18:13:43.79 Server (c) Microsoft Corporation.
2019-11-20 18:13:43.79 Server All rights reserved.
2019-11-20 18:13:43.79 Server Server process ID is 21120.
2019-11-20 18:13:43.79 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2019-11-20 18:13:43.79 Server Authentication mode is MIXED.
2019-11-20 18:13:43.79 Server Logging SQL Server messages in file 'D:\Sql\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2019-11-20 18:13:43.79 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2019-11-20 18:13:43.79 Server Registry startup parameters:
-d D:\Sql\MSSQL14.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\Sql\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\Sql\MSSQL14.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2019-11-20 18:13:43.79 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2019-11-20 18:13:43.79 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-11-20 18:13:43.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-11-20 18:13:43.79 Server Detected 12154 MB of RAM. This is an informational message; no user action is required.
2019-11-20 18:13:43.79 Server Using conventional memory in the memory manager.
2019-11-20 18:13:43.82 Server Default collation: Latin1_General_CI_AS (us_english 1033)
2019-11-20 18:13:43.84 Server Buffer pool extension is already disabled. No action is necessary.
2019-11-20 18:13:43.87 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-11-20 18:13:43.87 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-11-20 18:13:43.88 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-11-20 18:13:43.88 Server This instance of SQL Server last reported using a process ID of 7944 at 20/11/2019 18:13:36 (local) 20/11/2019 18:13:36 (UTC). This is an informational message only; no user action is required.
2019-11-20 18:13:43.88 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-11-20 18:13:43.89 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2019-11-20 18:13:43.89 Server In-Memory OLTP initialized on standard machine.
2019-11-20 18:13:43.90 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2019-11-20 18:13:43.91 Server Query Store settings initialized with enabled = 1,
2019-11-20 18:13:43.91 Server Software Usage Metrics is disabled.
2019-11-20 18:13:43.91 spid6s Starting up database 'master'.
2019-11-20 18:13:43.97 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-11-20 18:13:43.97 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-11-20 18:13:43.97 spid6s SQL Trace ID 1 was started by login "sa".
2019-11-20 18:13:43.98 spid6s Server name is 'HOME'. This is an informational message only. No user action is required.
2019-11-20 18:13:43.98 spid19s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-11-20 18:13:43.98 spid19s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2019-11-20 18:13:43.98 spid6s Starting up database 'msdb'.
2019-11-20 18:13:43.98 spid12s Starting up database 'mssqlsystemresource'.
2019-11-20 18:13:43.99 spid12s The resource database build version is 14.00.1000. This is an informational message only. No user action is required.
2019-11-20 18:13:44.00 spid6s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2019-11-20 18:13:44.00 spid12s Starting up database 'model'.
2019-11-20 18:13:44.02 spid12s Polybase feature disabled.
2019-11-20 18:13:44.02 spid12s Clearing tempdb database.
2019-11-20 18:13:44.05 spid16s A self-generated certificate was successfully loaded for encryption.
2019-11-20 18:13:44.05 spid16s Server is listening on [ 'any' <ipv6> 1433].
2019-11-20 18:13:44.06 spid16s Server is listening on [ 'any' <ipv4> 1433].
2019-11-20 18:13:44.06 spid16s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2019-11-20 18:13:44.06 spid16s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2019-11-20 18:13:44.06 Server Server is listening on [ ::1 <ipv6> 1434].
2019-11-20 18:13:44.06 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2019-11-20 18:13:44.06 Server Dedicated admin connection support was established for listening locally on port 1434.
2019-11-20 18:13:44.06 spid16s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-11-20 18:13:44.06 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2019-11-20 18:13:44.06 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Home ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-11-20 18:13:44.06 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Home:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-11-20 18:13:44.07 Server CLR version v4.0.30319 loaded.
2019-11-20 18:13:44.08 spid12s Starting up database 'tempdb'.
2019-11-20 18:13:44.10 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2019-11-20 18:13:44.20 spid12s The tempdb database has 8 data file(s).
2019-11-20 18:13:44.20 spid19s The Service Broker endpoint is in disabled or stopped state.
2019-11-20 18:13:44.20 spid19s The Database Mirroring endpoint is in disabled or stopped state.
2019-11-20 18:13:44.21 spid19s Service Broker manager has started.
2019-11-20 18:13:44.26 spid6s Recovery is complete. This is an informational message only. No user action is required.
2019-11-20 18:13:47.94 spid54 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-11-20 18:13:47.94 spid54 Using 'xplog70.dll' version '2017.140.1000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2019-11-20 18:13:47.99 spid54 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2019-11-20 18:13:48.00 spid54 Using 'xpsqlbot.dll' version '2017.140.1000' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2019-11-20 18:13:56.66 spid58 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2019-11-20 18:13:56.66 spid58 Using 'xpstar.dll' version '2017.140.1000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2019-11-20 18:14:53.52 Logon Error: 18456, Severity: 14, State: 38.
2019-11-20 18:14:53.52 Logon Login failed for user 'User'. Reason: Failed to open the explicitly specified database 'Core'. [CLIENT: <local machine>]
2019-11-20 18:15:02.15 spid58 Using 'dbghelp.dll' version '4.0.5'
2019-11-20 18:15:49.44 Logon Error: 18456, Severity: 14, State: 38.
2019-11-20 18:15:49.44 Logon Login failed for user 'User'. Reason: Failed to open the explicitly specified database 'Core'. [CLIENT: <local machine>]
2019-11-20 18:19:01.71 Logon Error: 18456, Severity: 14, State: 38.
2019-11-20 18:19:01.71 Logon Login failed for user 'User'. Reason: Failed to open the explicitly specified database 'Core'. [CLIENT: <local machine>]
2019-11-20 18:35:48.22 Logon Error: 18456, Severity: 14, State: 38.
2019-11-20 18:35:48.22 Logon Login failed for user 'User'. Reason: Failed to open the explicitly specified database 'Core'. [CLIENT: <local machine>]
2019-11-20 18:46:54.99 spid9s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 116548, committed (KB): 240592, memory utilization: 48%.
2019-11-20 18:46:58.63 spid9s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 94824, committed (KB): 208976, memory utilization: 45%.
2019-11-20 18:52:29.02 spid9s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 330 seconds. Working set (KB): 87824, committed (KB): 209352, memory utilization: 41%.
2019-11-20 18:57:58.80 spid9s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 660 seconds. Working set (KB): 90084, committed (KB): 209416, memory utilization: 43%.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment