2021-12-16 19:23:14.73 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows 10 Home Single Language 10.0 (Build 22000: ) 2021-12-16 19:23:14.73 Server UTC adjustment: 5:30 2021-12-16 19:23:14.73 Server (c) Microsoft Corporation. 2021-12-16 19:23:14.73 Server All rights reserved. 2021-12-16 19:23:14.73 Server Server process ID is 16596. 2021-12-16 19:23:14.73 Server System Manufacturer: 'LENOVO', System Model: '82LM'. 2021-12-16 19:23:14.73 Server Authentication mode is WINDOWS-ONLY. 2021-12-16 19:23:14.73 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 2021-12-16 19:23:14.73 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required. 2021-12-16 19:23:14.73 Server Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\mastlog.ldf -T 3608 -T 1800 2021-12-16 19:23:14.73 Server Command Line Startup Parameters: -s "MSSQLSERVER" 2021-12-16 19:23:14.73 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2021-12-16 19:23:14.73 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2021-12-16 19:23:14.73 Server Detected 7514 MB of RAM. This is an informational message; no user action is required. 2021-12-16 19:23:14.73 Server Using conventional memory in the memory manager. 2021-12-16 19:23:14.73 Server Page exclusion bitmap is enabled. 2021-12-16 19:23:14.88 Server Buffer Pool: Allocating 1048576 bytes for 668641 hashPages. 2021-12-16 19:23:14.91 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033) 2021-12-16 19:23:14.93 Server Buffer pool extension is already disabled. No action is necessary. 2021-12-16 19:23:14.96 Server Query Store settings initialized with enabled = 1, 2021-12-16 19:23:14.96 Server The maximum number of dedicated administrator connections for this instance is '1' 2021-12-16 19:23:14.96 Server This instance of SQL Server last reported using a process ID of 18124 at 16-12-2021 19:22:10 (local) 16-12-2021 13:52:10 (UTC). This is an informational message only; no user action is required. 2021-12-16 19:23:14.96 Server Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2021-12-16 19:23:14.96 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. 2021-12-16 19:23:14.96 Server Lock partitioning is enabled. This is an informational message only. No user action is required. 2021-12-16 19:23:14.97 Server In-Memory OLTP initialized on lowend machine. 2021-12-16 19:23:14.99 Server [INFO] Created Extended Events session 'hkenginexesession' 2021-12-16 19:23:14.99 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. 2021-12-16 19:23:15.00 Server Total Log Writer threads: 2. This is an informational message; no user action is required. 2021-12-16 19:23:15.01 Server Database Mirroring Transport is disabled in the endpoint configuration. 2021-12-16 19:23:15.01 Server clwb is selected for pmem flush operation. 2021-12-16 19:23:15.01 Server Software Usage Metrics is disabled. 2021-12-16 19:23:15.02 spid9s Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required. 2021-12-16 19:23:15.02 spid9s Starting up database 'master'. 2021-12-16 19:23:15.03 spid9s Snapshot isolation or read committed snapshot is not available in database 'master' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:15.04 spid9s Snapshot isolation or read committed snapshot is not available in database 'master' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:15.04 spid9s Snapshot isolation or read committed snapshot is not available in database 'master' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:15.08 Server CLR version v4.0.30319 loaded. 2021-12-16 19:23:15.10 spid9s Resource governor reconfiguration succeeded. 2021-12-16 19:23:15.10 spid9s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2021-12-16 19:23:15.10 spid9s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2021-12-16 19:23:15.11 spid9s SQL Trace ID 1 was started by login "sa". 2021-12-16 19:23:15.11 spid9s Server name is 'ANIKET'. This is an informational message only. No user action is required. 2021-12-16 19:23:15.12 spid20s Always On: The availability replica manager is starting. This is an informational message only. No user action is required. 2021-12-16 19:23:15.12 spid20s 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. 2021-12-16 19:23:15.14 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 2021-12-16 19:23:15.21 spid19s A self-generated certificate was successfully loaded for encryption. 2021-12-16 19:23:15.21 spid19s Server is listening on [ 'any' 1433]. 2021-12-16 19:23:15.21 spid19s Server is listening on [ 'any' 1433]. 2021-12-16 19:23:15.21 spid19s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. 2021-12-16 19:23:15.21 spid19s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ]. 2021-12-16 19:23:15.21 Server Server is listening on [ ::1 1434]. 2021-12-16 19:23:15.21 Server Server is listening on [ 127.0.0.1 1434]. 2021-12-16 19:23:15.21 Server Dedicated admin connection support was established for listening locally on port 1434. 2021-12-16 19:23:15.22 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. 2021-12-16 19:23:15.22 spid19s Recovery is complete. This is an informational message only. No user action is required. 2021-12-16 19:23:15.22 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required. 2021-12-16 19:23:15.22 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Aniket ] 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. 2021-12-16 19:23:15.22 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Aniket: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. 2021-12-16 19:23:34.77 spid51 Starting up database 'mssqlsystemresource'. 2021-12-16 19:23:34.77 spid51 The resource database build version is 15.00.2000. This is an informational message only. No user action is required. 2021-12-16 19:23:34.78 spid51 Snapshot isolation or read committed snapshot is not available in database 'mssqlsystemresource' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:34.78 spid51 Snapshot isolation or read committed snapshot is not available in database 'mssqlsystemresource' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:34.78 spid51 Snapshot isolation or read committed snapshot is not available in database 'mssqlsystemresource' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:34.82 spid51 Clearing tempdb database. 2021-12-16 19:23:34.82 spid51 Starting up database 'model'. 2021-12-16 19:23:34.88 spid51 Starting up database 'tempdb'. 2021-12-16 19:23:35.21 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required. 2021-12-16 19:23:35.22 spid51 Using 'xplog70.dll' version '2019.150.2000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required. 2021-12-16 19:23:35.26 spid52 Starting up database 'msdb'. 2021-12-16 19:23:35.28 spid52 Snapshot isolation or read committed snapshot is not available in database 'msdb' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:35.28 spid52 Snapshot isolation or read committed snapshot is not available in database 'msdb' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:35.28 spid52 Snapshot isolation or read committed snapshot is not available in database 'msdb' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 2021-12-16 19:23:35.41 spid53 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required. 2021-12-16 19:23:35.41 spid53 Using 'xpsqlbot.dll' version '2019.150.2000' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required. 2021-12-16 19:24:22.07 spid54 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required. 2021-12-16 19:24:22.07 spid54 Using 'xpstar.dll' version '2019.150.2000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required. 2021-12-16 19:24:45.04 spid51 Starting up database 'FrstDb'. 2021-12-16 19:24:45.07 spid51 Parallel redo is started for database 'FrstDb' with worker pool size [8]. 2021-12-16 19:24:45.08 spid51 Parallel redo is shutdown for database 'FrstDb' with worker pool size [8]. 2021-12-16 22:36:38.58 spid12s 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): 102904, committed (KB): 215752, memory utilization: 47%. 2021-12-16 22:42:12.10 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 333 seconds. Working set (KB): 103960, committed (KB): 215872, memory utilization: 48%. 2021-12-16 22:46:43.03 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 604 seconds. Working set (KB): 103836, committed (KB): 215912, memory utilization: 48%. 2021-12-16 22:52:09.29 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 930 seconds. Working set (KB): 102372, committed (KB): 215960, memory utilization: 47%. 2021-12-16 23:04:02.06 spid12s 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): 97056, committed (KB): 216064, memory utilization: 44%. 2021-12-16 23:09:34.02 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 331 seconds. Working set (KB): 99892, committed (KB): 216144, memory utilization: 46%. 2021-12-16 23:14:04.52 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 602 seconds. Working set (KB): 99680, committed (KB): 216176, memory utilization: 46%. 2021-12-16 23:19:30.18 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 928 seconds. Working set (KB): 98092, committed (KB): 216224, memory utilization: 45%. 2021-12-16 23:34:05.86 spid12s 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): 99080, committed (KB): 216392, memory utilization: 45%. 2021-12-16 23:39:36.96 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 331 seconds. Working set (KB): 99724, committed (KB): 215832, memory utilization: 46%. 2021-12-16 23:44:06.30 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 600 seconds. Working set (KB): 99128, committed (KB): 215440, memory utilization: 46%. 2021-12-16 23:49:32.92 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 927 seconds. Working set (KB): 97444, committed (KB): 215456, memory utilization: 45%. 2021-12-17 00:00:53.07 spid28s This instance of SQL Server has been using a process ID of 16596 since 16-12-2021 19:23:15 (local) 16-12-2021 13:53:15 (UTC). This is an informational message only; no user action is required. 2021-12-17 00:04:08.54 spid12s 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): 97544, committed (KB): 216152, memory utilization: 45%. 2021-12-17 00:09:41.01 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 332 seconds. Working set (KB): 100076, committed (KB): 216048, memory utilization: 46%. 2021-12-17 00:14:11.79 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 603 seconds. Working set (KB): 99100, committed (KB): 215384, memory utilization: 46%. 2021-12-17 00:19:40.77 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 932 seconds. Working set (KB): 97660, committed (KB): 215512, memory utilization: 45%. 2021-12-17 00:24:12.37 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1203 seconds. Working set (KB): 99396, committed (KB): 215600, memory utilization: 46%. 2021-12-17 00:25:49.64 spid12s 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): 110000, committed (KB): 216200, memory utilization: 50%. 2021-12-17 00:31:18.64 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 328 seconds. Working set (KB): 109036, committed (KB): 215376, memory utilization: 50%. 2021-12-17 00:36:47.38 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 657 seconds. Working set (KB): 97832, committed (KB): 215392, memory utilization: 45%. 2021-12-17 00:41:10.74 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 921 seconds. Working set (KB): 99544, committed (KB): 215424, memory utilization: 46%. 2021-12-17 00:46:39.33 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1249 seconds. Working set (KB): 99624, committed (KB): 215440, memory utilization: 46%. 2021-12-17 00:51:04.55 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1514 seconds. Working set (KB): 97772, committed (KB): 215472, memory utilization: 45%. 2021-12-17 00:55:29.36 spid12s 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): 110276, committed (KB): 216408, memory utilization: 50%. 2021-12-17 01:00:57.88 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 328 seconds. Working set (KB): 109964, committed (KB): 216288, memory utilization: 50%. 2021-12-17 01:06:27.17 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 657 seconds. Working set (KB): 98708, committed (KB): 216320, memory utilization: 45%. 2021-12-17 01:10:50.23 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 920 seconds. Working set (KB): 100260, committed (KB): 216280, memory utilization: 46%. 2021-12-17 12:34:14.73 spid12s 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): 99068, committed (KB): 216496, memory utilization: 45%. 2021-12-17 12:39:48.36 spid12s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 332 seconds. Working set (KB): 99760, committed (KB): 215400, memory utilization: 46%. 2021-12-17 12:41:21.85 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. 2021-12-17 12:41:21.89 spid9s Always On: The availability replica manager is going offline because SQL Server is shutting down. This is an informational message only. No user action is required. 2021-12-17 12:41:21.90 spid9s .NET Framework runtime has been stopped. 2021-12-17 12:41:22.01 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. 2021-12-17 12:41:22.02 spid9s Error: 17054, Severity: 16, State: 1. 2021-12-17 12:41:22.02 spid9s The current event was not reported to the operating system error log. Operating system error = (null). You may need to clear the operating system error log if it is full.