2025-10-31 09:03:54.49 Server      Microsoft SQL Server 2025 (RTM-CU1) - 17.0.4000.2 (X64) 
	Oct 29 2025 17:12:58 
	Copyright (C) 2025 Microsoft Corporation
	Enterprise Edition (64-bit) on Windows Server 2025 Standard 10.0 <X64> (Build 26100: )

2025-10-31 09:03:54.50 Server      UTC adjustment: -7:00
2025-10-31 09:03:54.50 Server      (c) Microsoft Corporation.
2025-10-31 09:03:54.50 Server      All rights reserved.
2025-10-31 09:03:54.50 Server      Server process ID is 29860.
2025-10-31 09:03:54.50 Server      System Manufacturer: 'HPE', System Model: 'ProLiant DL345 Gen11'.
2025-10-31 09:03:54.50 Server      Authentication mode is MIXED.
2025-10-31 09:03:54.50 Server      Logging SQL Server messages in file 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\log\errorlog'.
2025-10-31 09:03:54.50 Server      The service account is '3M1D0M13CH\Administrator'. This is an informational message; no user action is required.
2025-10-31 09:03:54.50 Server      Registry startup parameters: 
	 -d G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\data\master.mdf
	 -l G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\data\mastlog.ldf
	 -e G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\log\errorlog
2025-10-31 09:03:54.50 Server      Command Line Startup Parameters:
	 -xcopy
	 -c
	 -x
	 -E
	 -T 834
	 -T 902
	 -T 8086
	 -T 8076
	 -T 9389
	 -T 9349
	 -T 1260
	 -T 8902
	 -T 8744
	 -T 3468
	 -T 1296
	 -T 16452
	 -T 16450
	 -T 16448
	 -T 817
	 -T 8151
	 -T 8158
	 -T 9370
	 -c
2025-10-31 09:03:54.50 Server      Environment Variable Startup Parameters:
	 MSSQL_AGENT_LOGGING_LEVEL=00000007
	 MSSQL_NUMBER_ERROR_LOGS=128
	 SQLSERVR_ADDLFLAGS= -c -x -E -T834 -T902 -T8086 -T8076 -T9389 -T9349 -T1260 -T8902 -T8744 -T3468 -T1296 -T16452 -T16450 -T16448 -T817 -T8151 -T8158 -T9370
	 SQLSERVR_ADDLSVCFLAGS=-V "SQLSERVR_ROOT=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr" -V "SQLSERVR_INSTNAME=MSSQLSERVER" -V "SQLSERVR_PORT=1433" -V "SQLSERVR_DAC_PORT=1434" -V "SQLSERVR_NAMED_PIPE=\\.\pipe\sql\query" -V "SQLSERVR_DAC_NAMED_PIPE=\\.\pipe\sql\dac\query" -V "SQLSERVR_DATA=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr" -V "SQLSERVR_LOGDIR=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\log" -V "SQLSERVR_TDS_CERTIFICATE="
	 SQLSERVR_AT_PORT=5000
	 SQLSERVR_CMDLINE="G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\sqlservr.exe" -xcopy ""   -c -x -E -T834 -T902 -T8086 -T8076 -T9389 -T9349 -T1260 -T8902 -T8744 -T3468 -T1296 -T16452 -T16450 -T16448 -T817 -T8151 -T8158 -T9370 -c
	 SQLSERVR_DAC_NAMED_PIPE=\\.\pipe\sql\dac\query
	 SQLSERVR_DAC_PORT=1434
	 SQLSERVR_DATA=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr
	 SQLSERVR_DEBUGGER_DIR=C:\Debuggers
	 SQLSERVR_ESCAPED_PATH=G:\x5c\x5csql25cu1\x5c\x5csql2025_cu1-17-0-4000-2-20251029-1649\x5c\x5csql2025_cu1-17-0-4000-2-20251029-1649\x5c\x5cretail\x5c\x5camd64\x5c\x5csqlservr\x5c\x5cbinn
	 SQLSERVR_INSTALLED_INSTANCES=MSSQLSERVER25\MSSQLSERVER
	 SQLSERVR_INSTALLED_INSTANCES_ADDED=MSSQLSERVER25\MSSQLSERVER\MSSQLSERVER
	 SQLSERVR_INSTALLED_INSTANCES_REMOVED=MSSQLSERVER25
	 SQLSERVR_INSTID=MSSQL17.MSSQLSERVER
	 SQLSERVR_INSTNAME=MSSQLSERVER
	 SQLSERVR_INSTNUM=0
2025-10-31 09:03:54.50 Server      Environment Variable Startup Parameters:
	 SQLSERVR_NAMED_PIPE=\\.\pipe\sql\query
	 SQLSERVR_PERFCTR_FIRST_COUNTER=REG_DWORD    0xe9b2
	 SQLSERVR_PERFCTR_HASH=39E8B3529AF293A352C2988A66F5B6125A62DB9E5B838202FA19ADC7DF5C3CD7
	 SQLSERVR_PERFCTR_HASH_CURRENT=39E8B3529AF293A352C2988A66F5B6125A62DB9E5B838202FA19ADC7DF5C3CD7
	 SQLSERVR_PERFCTR_PATH=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\sqlctr170.dll
	 SQLSERVR_PORT=1433
	 SQLSERVR_REG=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\reg\MSSQLSERVER
	 SQLSERVR_ROOT=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr
	 SQLSERVR_SCRIPT_ROOT=G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\
	 SQLSERVR_SN_ADDREMOVE=add
	 SQLSERVR_SVCNAME=MSSQLSERVER
	 SQLSERVR_TDS_CERTIFICATE=""
	 SQLSERVR_USE_REGISTRY=1
	 SQLSERVR_XCOPYFLAG=""
2025-10-31 09:03:54.50 Server      SQL Server detected 1 sockets with 64 cores per socket and 128 logical processors per socket, 128 total logical processors; using 128 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2025-10-31 09:03:54.50 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2025-10-31 09:03:54.50 Server      Using large pages in the memory manager.
2025-10-31 09:03:54.50 Server      The SQL Server image sqlservr.exe was allocated using the large pages option.
2025-10-31 09:03:54.50 Server      The SQL Server image sqlmin.dll was allocated using the large pages option.
2025-10-31 09:03:54.50 Server      The SQL Server image sqldk.dll was allocated using the large pages option.
2025-10-31 09:03:54.50 Server      The SQL Server image sqllang.dll was allocated using the large pages option.
2025-10-31 09:03:54.50 Server      The SQL Server image sqltses.dll was allocated using the large pages option.
2025-10-31 09:03:54.50 Server      SQL Server detected the following NUMA node configuration (NUMA Node number 0, Processor Group number 0, CPU Mask 0xffffffffffffffff).
2025-10-31 09:03:54.50 Server      SQL Server detected the following NUMA node configuration (NUMA Node number 1, Processor Group number 1, CPU Mask 0xffffffffffffffff).
2025-10-31 09:03:55.12 Server      Detected 1572562 MB of RAM, 188906 MB of available memory, 245347 MB of available page file. This is an informational message; no user action is required.
2025-10-31 09:03:55.13 Server      Buffer Pool: Allocating 2147483648 bytes for 226492320 hashPages.
2025-10-31 09:03:55.13 Server      The available memory for this SQL Server instance (188906 MB) is lower than the configured maximum server memory (1415577 MB). This might occur because of external memory pressure or faulty hardware. If the operating system does not have sufficient memory for this SQL Server instance, consider reducing the configured maximum server memory to avoid this message on instance startup.
2025-10-31 09:03:55.78 Server      Failed to verify Authenticode signature on DLL 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\SQLVDI.DLL'.
2025-10-31 09:03:55.78 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2025-10-31 09:03:55.78 Server      Automatic soft-NUMA was not enabled, because 'NodeConfiguration' key was detected in the registry at path 'Software\Microsoft\Microsoft SQL Server\170'. Disable registry based soft-NUMA configuration in order to activate the automatic soft-NUMA configuration.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 0, processor mask 0x000000000000ffff. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 1, processor mask 0x00000000ffff0000. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 2, processor mask 0x0000ffff00000000. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 3, processor mask 0xffff000000000000. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 4, processor mask 0x000000000000ffff. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 5, processor mask 0x00000000ffff0000. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 6, processor mask 0x0000ffff00000000. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.78 Server      Processor affinity turned on: node 7, processor mask 0xffff000000000000. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2025-10-31 09:03:55.79 Server      Buffer pool extension is already disabled. No action is necessary.
2025-10-31 09:03:55.81 Server      Skipping small memory environment configuration. State 1.
2025-10-31 09:03:55.82 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2 AVX512 (F CD BW DQ VL IFMA VBMI VBMI2 VNNI BITALG VPOQCNTDQ BF16 VP2INTERSECT)
2025-10-31 09:03:55.83 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2025-10-31 09:03:55.83 Server      Query Store settings initialized with enabled = 1, 
2025-10-31 09:03:55.84 Server      The maximum number of dedicated administrator connections for this instance is '1'
2025-10-31 09:03:55.84 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.
2025-10-31 09:03:55.84 Server      Node configuration: node 1: CPU mask: 0x00000000ffff0000:0 Active CPU mask: 0x00000000ffff0000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2025-10-31 09:03:55.84 Server      Node configuration: node 2: CPU mask: 0x0000ffff00000000:0 Active CPU mask: 0x0000ffff00000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2025-10-31 09:03:55.84 Server      Node configuration: node 3: CPU mask: 0xffff000000000000:0 Active CPU mask: 0xffff000000000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2025-10-31 09:03:55.84 Server      Node configuration: node 4: CPU mask: 0x000000000000ffff:1 Active CPU mask: 0x000000000000ffff:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2025-10-31 09:03:55.84 Server      Node configuration: node 5: CPU mask: 0x00000000ffff0000:1 Active CPU mask: 0x00000000ffff0000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2025-10-31 09:03:55.84 Server      Node configuration: node 6: CPU mask: 0x0000ffff00000000:1 Active CPU mask: 0x0000ffff00000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2025-10-31 09:03:55.84 Server      Node configuration: node 7: CPU mask: 0xffff000000000000:1 Active CPU mask: 0xffff000000000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2025-10-31 09:03:55.85 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.
2025-10-31 09:03:55.85 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2025-10-31 09:03:55.86 Server      In-Memory OLTP initialized on highend machine.
2025-10-31 09:03:55.87 Server      [INFO] Created Extended Events session 'hkenginexesession'
2025-10-31 09:03:55.87 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.
2025-10-31 09:03:55.88 Server      Total Log Writer threads: 8. This is an informational message; no user action is required.
2025-10-31 09:03:55.94 Server      CLR version v4.0.30319 loaded.
2025-10-31 09:03:55.99 Server      clwb is selected for pmem flush operation.
2025-10-31 09:03:55.99 Server      Software Usage Metrics is disabled.
2025-10-31 09:03:55.99 Server      Physical cache size is set to 16384 entries for available 2 memory nodes
2025-10-31 09:03:55.99 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\sqlservr.exe'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:55.99 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\SQLOS.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:55.99 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\qds.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:55.99 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\svl.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\sqldk.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\sqlTsEs.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\sqllang.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\secforwarder.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\sqlmin.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\instapi170.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\Resources\1033\sqlevn70.rll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\SQLVDI.DLL'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\hkruntime.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\hkengine.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\hkcompile.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\opends60.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.01 Server      Failed to verify the Authenticode signature of 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\SqlServerSpatial170.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2025-10-31 09:03:56.02 Server      External governance manager initialized
2025-10-31 09:03:56.02 Server      Detected pause instruction latency: 43 cycles.
2025-10-31 09:03:56.10 spid51s     [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.10 spid51s     Starting up database 'master'.
2025-10-31 09:03:56.11 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2025-10-31 09:03:56.12 spid51s     [32762]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.12 spid51s     Starting up database 'model_replicatedmaster'.
2025-10-31 09:03:56.12 spid64s     [32767]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.12 spid64s     Starting up database 'mssqlsystemresource'.
2025-10-31 09:03:56.12 spid64s     The resource database build version is 17.00.4000. This is an informational message only. No user action is required.
2025-10-31 09:03:56.13 spid64s     [3]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.13 spid64s     Starting up database 'model'.
2025-10-31 09:03:56.14 spid51s     [32761]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.14 spid51s     Starting up database 'model_msdb'.
2025-10-31 09:03:56.15 spid51s     Resource governor reconfiguration succeeded.
2025-10-31 09:03:56.15 spid51s     SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2025-10-31 09:03:56.15 spid51s     [AutoStartAuditSessions] Starting audit session task
2025-10-31 09:03:56.15 spid51s     SQL Server Audit has started the audits. This is an informational message. No user action is required.
2025-10-31 09:03:56.25 spid65s     A self-generated certificate was successfully loaded for encryption.
2025-10-31 09:03:56.25 spid65s     Server is listening on [ 'any' <ipv6> 1433] accept sockets 1.
2025-10-31 09:03:56.26 spid65s     Server is listening on [ 'any' <ipv4> 1433] accept sockets 1.
2025-10-31 09:03:56.26 spid65s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2025-10-31 09:03:56.26 spid65s     Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2025-10-31 09:03:56.26 spid51s     SQL Trace ID 1 was started by login "sa".
2025-10-31 09:03:56.26 Server      Server is listening on [ ::1 <ipv6> 1434] accept sockets 1.
2025-10-31 09:03:56.26 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434] accept sockets 1.
2025-10-31 09:03:56.26 Server      Dedicated admin connection support was established for listening locally on port 1434.
2025-10-31 09:03:56.26 spid51s     Server name is '3m1d0m13ch'. This is an informational message only. No user action is required.
2025-10-31 09:03:56.26 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.
2025-10-31 09:03:56.26 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/3m1d0m13ch ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. 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.
2025-10-31 09:03:56.26 spid65s     Server is listening on [ ::1 <ipv6> 57796] accept sockets 1.
2025-10-31 09:03:56.26 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/3m1d0m13ch:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. 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.
2025-10-31 09:03:56.26 spid65s     Server is listening on [ 127.0.0.1 <ipv4> 57796] accept sockets 1.
2025-10-31 09:03:56.26 spid65s     Server local connection provider is ready to accept connection on [ \\.\pipe\sqlsatellitelaunch ].
2025-10-31 09:03:56.26 spid65s     Resource governor reconfiguration encountered an issue (HRESULT code : 0x80070002, reason: Construction of Launchpad Connection failed), while sending active external resource pool ids to launchpad. This will not fail reconfigure.
2025-10-31 09:03:56.26 spid65s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2025-10-31 09:03:56.28 spid51s     Error: 30064, Severity: 17, State: 1.
2025-10-31 09:03:56.28 spid51s     SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation.
2025-10-31 09:03:56.28 spid73s     Error: 9954, Severity: 16, State: 1.
2025-10-31 09:03:56.28 spid73s     SQL Server failed to communicate with filter daemon launch service  (OS error: The specified service does not exist as an installed service.
). Full-Text filter daemon process failed to start. Full-text search functionality will not be available.
2025-10-31 09:03:56.28 spid64s     Clearing tempdb database.
2025-10-31 09:03:56.28 spid75s     Always On Availability Groups: The availability replica manager is starting. This is an informational message only. No user action is required.
2025-10-31 09:03:56.28 spid76s     [4]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.28 spid77s     [5]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.28 spid75s     Always On Availability Groups: 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.
2025-10-31 09:03:56.28 spid76s     Starting up database 'msdb'.
2025-10-31 09:03:56.28 spid77s     Starting up database 'tpch3000gcci'.
2025-10-31 09:03:56.30 spid64s     [2]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 09:03:56.30 spid64s     Starting up database 'tempdb'.
2025-10-31 09:03:56.41 spid77s     Parallel redo is started for database 'tpch3000gcci' with worker pool size [16].
2025-10-31 09:03:56.50 spid51s     Parallel redo is shutdown for database 'tpch3000gcci' with worker pool size [16].
2025-10-31 09:03:57.65 spid64s     The tempdb database has 128 data file(s).
2025-10-31 09:03:57.65 spid62s     The Service Broker endpoint is in disabled or stopped state.
2025-10-31 09:03:57.65 spid62s     The Database Mirroring endpoint is in disabled or stopped state.
2025-10-31 09:03:57.66 spid51s     Recovery is complete. This is an informational message only. No user action is required.
2025-10-31 09:03:57.66 spid62s     Service Broker manager has started.
2025-10-31 09:04:30.05 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:04:30.05 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:09:30.14 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:09:30.14 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:14:30.37 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:14:30.37 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:19:30.44 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:19:30.44 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:24:30.50 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:24:30.50 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:29:30.56 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:29:30.56 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:34:30.61 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:34:30.61 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:38:48.34 spid50s     CImageHelper::Init () Version-specific dbghelp.dll is not used
2025-10-31 09:38:48.35 spid50s     Using 'dbghelp.dll' version '4.0.5'
2025-10-31 09:38:48.43 spid50s     Failed to collect stack frames.
2025-10-31 09:39:30.78 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:39:30.78 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:44:30.89 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:44:30.89 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:49:30.94 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:49:30.94 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:54:31.00 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:54:31.00 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 09:59:31.07 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 09:59:31.07 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:04:31.12 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:04:31.12 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:09:31.18 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:09:31.18 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:14:31.23 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:14:31.23 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:19:31.29 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:19:31.29 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:24:31.35 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:24:31.35 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:29:31.41 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:29:31.41 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:34:31.47 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:34:31.47 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:39:31.52 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:39:31.52 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:44:31.58 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:44:31.58 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:49:31.64 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:49:31.64 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:54:31.70 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:54:31.70 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 10:59:31.76 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 10:59:31.76 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:04:31.81 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:04:31.81 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:09:31.87 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:09:31.87 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:14:31.93 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:14:31.93 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:19:31.99 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:19:31.99 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:24:32.05 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:24:32.05 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:29:32.10 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:29:32.10 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:34:32.16 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:34:32.16 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:39:32.22 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:39:32.22 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:44:32.28 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:44:32.28 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:49:32.33 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:49:32.33 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:54:32.39 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:54:32.39 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 11:59:32.45 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 11:59:32.45 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:04:32.51 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:04:32.51 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:09:32.57 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:09:32.57 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:14:32.62 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:14:32.62 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:19:32.68 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:19:32.68 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:24:32.74 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:24:32.74 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:29:32.80 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:29:32.80 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:34:32.85 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:34:32.85 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:39:32.91 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:39:32.91 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:44:32.97 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:44:32.97 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:49:33.02 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:49:33.02 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:54:33.08 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:54:33.08 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 12:59:33.14 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 12:59:33.14 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:04:33.20 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:04:33.20 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:09:33.26 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:09:33.26 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:14:33.31 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:14:33.31 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:19:33.37 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:19:33.37 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:24:33.43 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:24:33.43 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:29:33.49 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:29:33.49 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:34:33.54 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:34:33.54 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:39:33.60 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:39:33.60 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:44:33.66 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:44:33.66 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:49:33.72 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:49:33.72 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:54:33.78 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:54:33.78 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 13:59:33.83 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 13:59:33.83 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:04:33.89 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:04:33.89 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:09:33.95 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:09:33.95 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:14:34.01 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:14:34.01 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:19:34.07 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:19:34.07 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:24:34.13 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:24:34.13 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:29:34.18 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:29:34.18 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:34:34.24 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:34:34.24 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:39:34.30 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:39:34.30 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:44:34.36 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:44:34.36 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:49:34.41 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:49:34.41 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:54:34.47 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:54:34.47 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 14:59:34.53 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 14:59:34.53 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:01:49.47 spid66      Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2025-10-31 15:01:49.47 spid66      Failed to verify Authenticode signature on DLL 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\xplog70.dll'.
2025-10-31 15:01:49.47 spid66      Using 'xplog70.dll' version '2025.170.4000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2025-10-31 15:01:49.87 spid69      Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2025-10-31 15:01:49.87 spid69      Using 'xpsqlbot.dll' version '2025.170.4000' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2025-10-31 15:02:38.21 spid77      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2025-10-31 15:02:38.21 spid77      Failed to verify Authenticode signature on DLL 'G:\sql25cu1\sql2025_cu1-17-0-4000-2-20251029-1649\sql2025_cu1-17-0-4000-2-20251029-1649\retail\amd64\sqlservr\binn\xpstar.dll'.
2025-10-31 15:02:38.21 spid77      Using 'xpstar.dll' version '2025.170.4000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2025-10-31 15:04:34.59 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:04:34.59 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:05:06.24 spid67      [DBMgr::FindFreeDatabaseID] Next available DbId EX locked: 6
2025-10-31 15:05:44.60 spid67      [DBMgr::FindFreeDatabaseID] Next available DbId EX locked: 6
2025-10-31 15:05:44.70 spid67      [6]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 15:05:44.70 spid67      Starting up database 'TPCH_REFERENCE_DATA'.
2025-10-31 15:05:44.70 spid67      Parallel redo is started for database 'TPCH_REFERENCE_DATA' with worker pool size [16].
2025-10-31 15:05:44.71 spid67      Parallel redo is shutdown for database 'TPCH_REFERENCE_DATA' with worker pool size [16].
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.syspriorities.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysowners.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysdbreg.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysschobjs.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysextsources.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysextfileformats.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.syscolpars.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysxlgns.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysxsrvs.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysnsobjs.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.syscerts.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysrmtlgns.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysxprops.
2025-10-31 15:05:44.88 spid67       index restored for TPCH_REFERENCE_DATA.sysscalartypes.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.sysidxstats.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.sysendpts.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.sysclsobjs.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.sysremsvcbinds.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.sysrts.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.sysasymkeys.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.syssqlguides.
2025-10-31 15:05:44.89 spid67       index restored for TPCH_REFERENCE_DATA.syssoftobjrefs.
2025-10-31 15:06:33.59 spid87      Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2025-10-31 15:09:34.64 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:09:34.64 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:14:34.70 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:14:34.70 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:19:34.76 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:19:34.76 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:24:34.82 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:24:34.82 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:28:01.26 spid68      [DBMgr::FindFreeDatabaseID] Next available DbId EX locked: 7
2025-10-31 15:28:01.27 spid68      Error: 17053, Severity: 16, State: 1.
2025-10-31 15:28:01.27 spid68      g:\Log\tpch1gcci_log.ldf: Operating system error 112(There is not enough space on the disk.) encountered.
2025-10-31 15:28:01.34 spid68      Setting database option FILESTREAM NON_TRANSACTED_ACCESS to OFF for database 'tpch1gcci'.
2025-10-31 15:29:34.88 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:29:34.88 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:34:34.93 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:34:34.93 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:39:34.99 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:39:34.99 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:41:14.43 spid68      [DBMgr::FindFreeDatabaseID] Next available DbId EX locked: 7
2025-10-31 15:41:32.07 spid68      [7]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 15:41:32.07 spid68      Starting up database 'tpch1gcci'.
2025-10-31 15:41:32.08 spid68      Parallel redo is started for database 'tpch1gcci' with worker pool size [16].
2025-10-31 15:41:32.08 spid68      Parallel redo is shutdown for database 'tpch1gcci' with worker pool size [16].
2025-10-31 15:41:32.50 spid68       index restored for tpch1gcci.syspriorities.
2025-10-31 15:41:32.50 spid68       index restored for tpch1gcci.sysowners.
2025-10-31 15:41:32.50 spid68       index restored for tpch1gcci.sysdbreg.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysschobjs.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysextsources.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysextfileformats.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.syscolpars.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysxlgns.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysxsrvs.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysnsobjs.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.syscerts.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysrmtlgns.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysxprops.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysscalartypes.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysidxstats.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysendpts.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysclsobjs.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysremsvcbinds.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysrts.
2025-10-31 15:41:32.51 spid68       index restored for tpch1gcci.sysasymkeys.
2025-10-31 15:41:32.52 spid68       index restored for tpch1gcci.syssqlguides.
2025-10-31 15:41:32.52 spid68       index restored for tpch1gcci.syssoftobjrefs.
2025-10-31 15:41:32.53 spid68      Setting database option ANSI_NULL_DEFAULT to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option ANSI_NULLS to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option ANSI_PADDING to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option ANSI_WARNINGS to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option ARITHABORT to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option AUTO_CLOSE to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option AUTO_SHRINK to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option AUTO_UPDATE_STATISTICS to ON for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.53 spid68      Setting database option CURSOR_DEFAULT to GLOBAL for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option NUMERIC_ROUNDABORT to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option QUOTED_IDENTIFIER to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option RECURSIVE_TRIGGERS to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option ENABLE_BROKER to ON for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option TRUSTWORTHY to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option ALLOW_SNAPSHOT_ISOLATION to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option PARAMETERIZATION to SIMPLE for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option READ_COMMITTED_SNAPSHOT to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option HONOR_BROKER_PRIORITY to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option RECOVERY to FULL for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option MULTI_USER to ON for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option PAGE_VERIFY to NONE for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option DB_CHAINING to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option FILESTREAM NON_TRANSACTED_ACCESS to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option target_recovery_time to 0 for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option delayed_durability to disabled for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option accelerated_database_recovery to OFF for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option query_store to off for database 'tpch1gcci'.
2025-10-31 15:41:32.54 spid68      Setting database option READ_WRITE to ON for database 'tpch1gcci'.
2025-10-31 15:41:44.00 spid97      Couldn't retrieve the external libraries folder, error: 0x800700ea
2025-10-31 15:41:44.00 spid97      Couldn't retrieve the external languages folder, error: 0x800700ea
2025-10-31 15:44:35.05 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:44:35.05 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:44:57.10 Logon       Error: 18456, Severity: 14, State: 38.
2025-10-31 15:44:57.10 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch1gcci'. [CLIENT: 14.14.2.111]
2025-10-31 15:45:02.92 Logon       Error: 18456, Severity: 14, State: 38.
2025-10-31 15:45:02.92 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch1gcci'. [CLIENT: 14.14.2.111]
2025-10-31 15:45:34.36 Logon       Error: 18456, Severity: 14, State: 38.
2025-10-31 15:45:34.36 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch1gcci'. [CLIENT: 14.14.2.111]
2025-10-31 15:45:42.81 Logon       Error: 18456, Severity: 14, State: 38.
2025-10-31 15:45:42.81 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch1gcci'. [CLIENT: 14.14.2.111]
2025-10-31 15:46:09.97 Logon       Error: 18456, Severity: 14, State: 38.
2025-10-31 15:46:09.97 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch1gcci'. [CLIENT: 14.14.2.111]
2025-10-31 15:46:13.20 Logon       Error: 18456, Severity: 14, State: 38.
2025-10-31 15:46:13.20 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch1gcci'. [CLIENT: 14.14.2.111]
2025-10-31 15:46:40.79 spid81      [DBMgr::FindFreeDatabaseID] Next available DbId EX locked: 7
2025-10-31 15:46:58.46 spid81      [7]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0. NestIdBasedHP: 1. m_nestIdBasedHPOnTempDB: 0
2025-10-31 15:46:58.46 spid81      Starting up database 'tpch1gcci'.
2025-10-31 15:46:58.46 spid81      Parallel redo is started for database 'tpch1gcci' with worker pool size [16].
2025-10-31 15:46:58.47 spid81      Parallel redo is shutdown for database 'tpch1gcci' with worker pool size [16].
2025-10-31 15:46:58.89 spid81       index restored for tpch1gcci.syspriorities.
2025-10-31 15:46:58.89 spid81       index restored for tpch1gcci.sysowners.
2025-10-31 15:46:58.89 spid81       index restored for tpch1gcci.sysdbreg.
2025-10-31 15:46:58.89 spid81       index restored for tpch1gcci.sysschobjs.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysextsources.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysextfileformats.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.syscolpars.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysxlgns.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysxsrvs.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysnsobjs.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.syscerts.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysrmtlgns.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysxprops.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysscalartypes.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysidxstats.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysendpts.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysclsobjs.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysremsvcbinds.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysrts.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.sysasymkeys.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.syssqlguides.
2025-10-31 15:46:58.90 spid81       index restored for tpch1gcci.syssoftobjrefs.
2025-10-31 15:46:58.92 spid81      Setting database option ANSI_NULL_DEFAULT to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option ANSI_NULLS to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option ANSI_PADDING to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option ANSI_WARNINGS to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option ARITHABORT to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option AUTO_CLOSE to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option AUTO_SHRINK to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option AUTO_UPDATE_STATISTICS to ON for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option CURSOR_DEFAULT to GLOBAL for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option NUMERIC_ROUNDABORT to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option QUOTED_IDENTIFIER to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option RECURSIVE_TRIGGERS to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option ENABLE_BROKER to ON for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option TRUSTWORTHY to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option ALLOW_SNAPSHOT_ISOLATION to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option PARAMETERIZATION to SIMPLE for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option READ_COMMITTED_SNAPSHOT to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option HONOR_BROKER_PRIORITY to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option RECOVERY to FULL for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option MULTI_USER to ON for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option PAGE_VERIFY to NONE for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option DB_CHAINING to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.92 spid81      Setting database option FILESTREAM NON_TRANSACTED_ACCESS to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.93 spid81      Setting database option target_recovery_time to 0 for database 'tpch1gcci'.
2025-10-31 15:46:58.93 spid81      Setting database option delayed_durability to disabled for database 'tpch1gcci'.
2025-10-31 15:46:58.93 spid81      Setting database option accelerated_database_recovery to OFF for database 'tpch1gcci'.
2025-10-31 15:46:58.93 spid81      Setting database option query_store to off for database 'tpch1gcci'.
2025-10-31 15:46:58.93 spid81      Setting database option READ_WRITE to ON for database 'tpch1gcci'.
2025-10-31 15:46:59.06 spid94      Setting database option RECOVERY to SIMPLE for database 'tpch1gcci'.
2025-10-31 15:46:59.06 spid94      Setting database option AUTO_CREATE_STATISTICS to OFF for database 'tpch1gcci'.
2025-10-31 15:46:59.06 spid94      Setting database option INCREMENTAL to OFF for database 'tpch1gcci'.
2025-10-31 15:46:59.06 spid94      Setting database option AUTO_UPDATE_STATISTICS to OFF for database 'tpch1gcci'.
2025-10-31 15:46:59.06 spid94      Setting database option PAGE_VERIFY to NONE for database 'tpch1gcci'.
2025-10-31 15:48:53.40 spid106     DBCC TRACEON 10204, server process ID (SPID) 106. This is an informational message only; no user action is required.
2025-10-31 15:49:17.27 spid106     DBCC TRACEOFF 10204, server process ID (SPID) 106. This is an informational message only; no user action is required.
2025-10-31 15:49:17.47 spid77      Setting database option RECOVERY to FULL for database 'tpch1gcci'.
2025-10-31 15:49:18.05 spid106     Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2025-10-31 15:49:20.61 spid93      Configuration option 'max degree of parallelism' changed from 120 to 120. Run the RECONFIGURE statement to install.
2025-10-31 15:49:35.11 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:49:35.11 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:54:35.16 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:54:35.16 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 15:59:35.22 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 15:59:35.22 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:04:35.28 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:04:35.28 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:09:35.34 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:09:35.34 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:14:35.39 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:14:35.39 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:19:35.45 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:19:35.45 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:24:35.51 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:24:35.51 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:29:35.57 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:29:35.57 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:34:35.63 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:34:35.63 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:39:35.68 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:39:35.68 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:44:35.74 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:44:35.74 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:49:35.80 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:49:35.80 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:54:35.86 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:54:35.86 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 16:59:35.92 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 16:59:35.92 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:04:35.97 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:04:35.97 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:09:36.03 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:09:36.03 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:14:36.09 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:14:36.09 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:19:36.15 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:19:36.15 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:24:36.21 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:24:36.21 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:29:36.26 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:29:36.26 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:34:36.32 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:34:36.32 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:39:36.38 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:39:36.38 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:42:39.90 Backup      Database backed up. Database: tpch1gcci, creation date(time): 2025/10/31(15:46:40), pages dumped: 78131, first LSN: 44:786950:1, last LSN: 44:786953:1, number of dump devices: 10, device information: (FILE=1, TYPE=DISK: {'G:\Backup\tpch1gcci_10files.bak1', 'G:\Backup\tpch1gcci_10files.bak2', 'G:\Backup\tpch1gcci_10files.bak3', 'G:\Backup\tpch1gcci_10files.bak4', 'G:\Backup\tpch1gcci_10files.bak5', 'G:\Backup\tpch1gcci_10files.bak6', 'G:\Backup\tpch1gcci_10files.bak7', 'G:\Backup\tpch1gcci_10files.bak8', 'G:\Backup\tpch1gcci_10files.bak9', 'G:\Backup\tpch1gcci_10files.bak10'}). This is an informational message only. No user action is required.
2025-10-31 17:42:39.93 Backup      BACKUP DATABASE successfully processed 76585 pages in 0.273 seconds (2191.626 MB/sec).
2025-10-31 17:44:36.44 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:44:36.44 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:49:36.50 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:49:36.50 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:54:36.56 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:54:36.56 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 17:59:36.61 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 17:59:36.61 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:04:36.67 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:04:36.67 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:09:36.73 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:09:36.73 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:14:36.79 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:14:36.79 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:19:36.85 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:19:36.85 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:24:36.90 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:24:36.90 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:29:36.96 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:29:36.96 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:34:37.02 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:34:37.02 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:39:37.08 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:39:37.08 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:44:37.13 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:44:37.13 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:49:37.19 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:49:37.19 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:54:37.25 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:54:37.25 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 18:59:37.30 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 18:59:37.30 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:04:37.36 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:04:37.36 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:09:37.42 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:09:37.42 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:14:37.48 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:14:37.48 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:19:37.54 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:19:37.54 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:24:37.60 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:24:37.60 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:29:37.66 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:29:37.66 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:34:37.71 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:34:37.71 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:39:37.77 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:39:37.77 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:44:37.83 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:44:37.83 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:49:37.88 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:49:37.88 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:54:37.94 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:54:37.94 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 19:59:38.00 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 19:59:38.00 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:04:38.06 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:04:38.06 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:09:38.12 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:09:38.12 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:14:38.18 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:14:38.18 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:19:38.23 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:19:38.23 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:24:38.29 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:24:38.29 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:29:38.35 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:29:38.35 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:34:38.41 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:34:38.41 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:39:38.46 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:39:38.46 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:44:38.52 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:44:38.52 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:49:38.58 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:49:38.58 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:54:38.64 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:54:38.64 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 20:59:38.70 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 20:59:38.70 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:04:38.75 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:04:38.75 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:09:38.81 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:09:38.81 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:14:38.87 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:14:38.87 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:19:38.92 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:19:38.92 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:24:38.98 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:24:38.98 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:29:39.04 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:29:39.04 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:32:22.87 Backup      Database backed up. Database: TPCH_REFERENCE_DATA, creation date(time): 2025/10/31(15:05:44), pages dumped: 5387, first LSN: 44:25424:1, last LSN: 44:25427:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\backup\tpch_reference_data.bak'}). This is an informational message only. No user action is required.
2025-10-31 21:32:22.88 Backup      BACKUP DATABASE successfully processed 5225 pages in 0.201 seconds (203.054 MB/sec).
2025-10-31 21:34:39.10 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:34:39.10 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:39:39.15 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:39:39.15 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:43:47.90 Backup      Database backed up. Database: tpch3000gcci, creation date(time): 2025/10/31(07:41:01), pages dumped: 181703708, first LSN: 45:242419100:1, last LSN: 45:242419103:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Q:\sql\backup\tpch3000gcci.afterPerfruns.bak'}). This is an informational message only. No user action is required.
2025-10-31 21:43:48.02 Backup      BACKUP DATABASE successfully processed 181703617 pages in 611.631 seconds (2320.941 MB/sec).
2025-10-31 21:44:39.21 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:44:39.21 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:49:39.27 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:49:39.27 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:54:39.33 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:54:39.33 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 21:59:39.38 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 21:59:39.38 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:04:39.44 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:04:39.44 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:09:39.50 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:09:39.50 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:14:39.56 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:14:39.56 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:19:39.61 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:19:39.61 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:24:39.67 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:24:39.67 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:29:39.73 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:29:39.73 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:34:39.79 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:34:39.79 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:39:39.85 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:39:39.85 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:44:39.91 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:44:39.91 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:49:39.96 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:49:39.96 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:54:40.02 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:54:40.02 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 22:59:40.08 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 22:59:40.08 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:04:40.14 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:04:40.14 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:09:40.19 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:09:40.19 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:14:40.25 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:14:40.25 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:19:40.31 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:19:40.31 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:24:40.37 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:24:40.37 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:29:40.42 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:29:40.42 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:34:40.48 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:34:40.48 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:39:40.54 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:39:40.54 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:44:40.60 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:44:40.60 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:49:40.66 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:49:40.66 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:54:40.71 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:54:40.71 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-10-31 23:59:40.77 Logon       Error: 18456, Severity: 14, State: 5.
2025-10-31 23:59:40.77 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:00:13.55 spid15s     This instance of SQL Server has been using a process ID of 29860 since 10/31/2025 9:03:56 AM (local) 10/31/2025 4:03:56 PM (UTC). This is an informational message only; no user action is required.
2025-11-01 00:04:40.83 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:04:40.83 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:09:40.89 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:09:40.89 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:14:40.95 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:14:40.95 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:19:41.00 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:19:41.00 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:24:41.06 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:24:41.06 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:29:41.12 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:29:41.12 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:34:41.18 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:34:41.18 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:39:41.23 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:39:41.23 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:44:41.29 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:44:41.29 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:49:41.35 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:49:41.35 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:54:41.41 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:54:41.41 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 00:59:41.47 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 00:59:41.47 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:04:41.52 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:04:41.52 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:09:41.58 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:09:41.58 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:14:41.64 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:14:41.64 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:19:41.70 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:19:41.70 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:24:41.75 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:24:41.75 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:29:41.81 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:29:41.81 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:34:41.87 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:34:41.87 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:39:41.93 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:39:41.93 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:44:41.99 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:44:41.99 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:49:42.05 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:49:42.05 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:54:42.10 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:54:42.10 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 01:59:42.16 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 01:59:42.16 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:04:42.22 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:04:42.22 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:09:42.28 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:09:42.28 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:14:42.33 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:14:42.33 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:19:42.39 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:19:42.39 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:24:42.45 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:24:42.45 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:29:42.51 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:29:42.51 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:34:42.57 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:34:42.57 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:39:42.63 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:39:42.63 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:44:42.68 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:44:42.68 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:49:42.74 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:49:42.74 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:54:42.80 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:54:42.80 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 02:59:42.86 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 02:59:42.86 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:04:42.91 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:04:42.91 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:09:42.97 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:09:42.97 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:14:43.03 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:14:43.03 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:19:43.09 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:19:43.09 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:24:43.15 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:24:43.15 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:29:43.20 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:29:43.20 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:34:43.26 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:34:43.26 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:39:43.32 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:39:43.32 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:44:43.38 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:44:43.38 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:49:43.43 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:49:43.43 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:54:43.49 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:54:43.49 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 03:59:43.55 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 03:59:43.55 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:04:43.61 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:04:43.61 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:09:43.66 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:09:43.66 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:14:43.72 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:14:43.72 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:19:43.78 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:19:43.78 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:24:43.84 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:24:43.84 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:29:43.89 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:29:43.89 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:34:43.95 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:34:43.95 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:39:44.01 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:39:44.01 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:44:44.07 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:44:44.07 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:49:44.13 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:49:44.13 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:54:44.18 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:54:44.18 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 04:59:44.24 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 04:59:44.24 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:04:44.30 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:04:44.30 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:09:44.36 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:09:44.36 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:14:44.42 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:14:44.42 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:19:44.48 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:19:44.48 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:24:44.54 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:24:44.54 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:29:44.60 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:29:44.60 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:34:44.66 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:34:44.66 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:39:44.71 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:39:44.71 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:44:44.77 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:44:44.77 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:49:44.83 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:49:44.83 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:54:44.89 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:54:44.89 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 05:59:44.94 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 05:59:44.94 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:04:45.00 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:04:45.00 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:09:45.06 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:09:45.06 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:14:45.12 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:14:45.12 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:19:45.18 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:19:45.18 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:24:45.23 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:24:45.23 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:29:45.29 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:29:45.29 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:34:45.35 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:34:45.35 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:39:45.41 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:39:45.41 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:44:45.46 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:44:45.46 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:49:45.52 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:49:45.52 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:54:45.58 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:54:45.58 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 06:59:45.64 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 06:59:45.64 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:04:45.69 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:04:45.69 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:09:45.75 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:09:45.75 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:14:45.81 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:14:45.81 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:19:45.87 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:19:45.87 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:24:45.93 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:24:45.93 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:29:45.99 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:29:45.99 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:34:46.04 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:34:46.04 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:39:46.10 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:39:46.10 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:44:46.16 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:44:46.16 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:49:46.22 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:49:46.22 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:54:46.27 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:54:46.27 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 07:59:46.33 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 07:59:46.33 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:04:46.39 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:04:46.39 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:09:46.45 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:09:46.45 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:14:46.51 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:14:46.51 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:19:46.56 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:19:46.56 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:24:46.62 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:24:46.62 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:29:46.68 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:29:46.68 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:34:46.74 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:34:46.74 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:39:46.79 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:39:46.79 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:44:46.85 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:44:46.85 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:49:46.91 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:49:46.91 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:54:46.97 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:54:46.97 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 08:59:47.03 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 08:59:47.03 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:04:47.08 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:04:47.08 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:09:47.14 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:09:47.14 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:14:47.20 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:14:47.20 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:19:47.26 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:19:47.26 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:24:47.31 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:24:47.31 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:29:47.37 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:29:47.37 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:34:47.43 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:34:47.43 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:39:47.49 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:39:47.49 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:43:23.31 spid77      Setting database option SINGLE_USER to ON for database 'TPCH_REFERENCE_DATA'.
2025-11-01 09:43:26.33 spid77      Couldn't retrieve the external libraries folder, error: 0x800700ea
2025-11-01 09:43:26.33 spid77      Couldn't retrieve the external languages folder, error: 0x800700ea
2025-11-01 09:44:22.56 spid75      Setting database option SINGLE_USER to ON for database 'tpch3000gcci'.
2025-11-01 09:44:25.57 spid75      Couldn't retrieve the external libraries folder, error: 0x800700ea
2025-11-01 09:44:25.57 spid75      Couldn't retrieve the external languages folder, error: 0x800700ea
2025-11-01 09:44:47.55 Logon       Error: 18456, Severity: 14, State: 5.
2025-11-01 09:44:47.55 Logon       Login failed for user 'NT Service\SQLTELEMETRY'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2025-11-01 09:44:48.49 Logon       Error: 18456, Severity: 14, State: 73.
2025-11-01 09:44:48.49 Logon       Login failed for user 'sa'. Reason: Failed to open the database 'tpch3000gcci' configured in the session recovery object while recovering the connection. [CLIENT: 14.14.2.111]
2025-11-01 09:44:51.18 Logon       Error: 18456, Severity: 14, State: 38.
2025-11-01 09:44:51.18 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch3000gcci'. [CLIENT: 14.14.2.111]
2025-11-01 09:45:01.28 Logon       Error: 18456, Severity: 14, State: 38.
2025-11-01 09:45:01.28 Logon       Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'tpch3000gcci'. [CLIENT: 14.14.2.111]
2025-11-01 09:45:10.38 spid66      .NET Framework runtime has been stopped.
2025-11-01 09:45:10.48 spid62s     Service Broker manager has shut down.
2025-11-01 09:45:10.66 spid66      Server shut down by request from login sa.
2025-11-01 09:45:10.66 spid66      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
