- 精华
- 阅读权限
- 40
- 好友
- 相册
- 分享
- 听众
- 收听
- 注册时间
- 2021-12-22
- 在线时间
- 小时
- 最后登录
- 1970-1-1
|

楼主 |
发表于 2024-1-13 14:59:25
|
显示全部楼层
2024-01-13 14:50:28.79 Server Microsoft SQL Server 2014 (SP3-CU4-GDR) (KB5029185) - 12.0.6449.1 (X64)
Jul 27 2023 21:55:46
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 19045: )
2024-01-13 14:50:28.79 Server UTC adjustment: 8:00
2024-01-13 14:50:28.79 Server (c) Microsoft Corporation.
2024-01-13 14:50:28.79 Server All rights reserved.Service Master Key could not be
2024-01-13 14:50:28.79 Server Server process ID is 15884.
2024-01-13 14:50:28.79 Server System Manufacturer: 'ASUS', System Model: 'All Series'.
2024-01-13 14:50:28.79 Server Authentication mode is MIXED.
2024-01-13 14:50:28.79 Server Logging SQL Server messages in file 'D:\Users\admin_temp\Desktop\LiteSQL_Release\MSSQL\Log\errorlog'.
2024-01-13 14:50:28.79 Server The service account is 'pc-001\admin_temp'. This is an informational message; no user action is required.
2024-01-13 14:50:28.79 Server Registry startup parameters:
-d D:\Users\admin_temp\Desktop\LiteSQL_Release\MSSQL\Data\master.mdf
-l D:\Users\admin_temp\Desktop\LiteSQL_Release\MSSQL\Data\mastlog.ldf
-e D:\Users\admin_temp\Desktop\LiteSQL_Release\MSSQL\Log\errorlog
2024-01-13 14:50:28.79 Server Command Line Startup Parameters:
-c
-s "mssql"
2024-01-13 14:50:28.95 Server Failed to verify the Authenticode signature of 'D:\Users\admin_temp\Desktop\LiteSQL_Release\MSSQL\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.
2024-01-13 14:50:28.98 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2024-01-13 14:50:28.99 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-01-13 14:50:28.99 Server Detected 16324 MB of RAM. This is an informational message; no user action is required.
2024-01-13 14:50:28.99 Server Using locked pages in the memory manager.
2024-01-13 14:50:29.06 Server Large Page Allocated: 32MB
2024-01-13 14:50:29.40 Server Default collation: Chinese_PRC_CI_AS (简体中文 2052)
2024-01-13 14:50:29.98 Server The maximum number of dedicated administrator connections for this instance is '1'
2024-01-13 14:50:30.09 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2024-01-13 14:50:30.17 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.
2024-01-13 14:50:30.20 Server Database Instant File Initialization: 已启用. 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.
2024-01-13 14:50:30.31 Server CLR version v4.0.30319 loaded.
2024-01-13 14:50:30.96 spid7s Starting up database 'master'.
2024-01-13 14:50:31.00 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2024-01-13 14:50:31.21 spid7s 18 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2024-01-13 14:50:31.21 spid7s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 3584 bytes at offset 82432 in file D:\Users\admin_temp\Desktop\LiteSQL_Release\MSSQL\Data\mastlog.ldf will be written.
2024-01-13 14:50:31.35 spid7s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2024-01-13 14:50:31.35 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2024-01-13 14:50:31.81 spid7s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2024-01-13 14:50:31.85 spid7s An error occurred during Service Master Key initialization. SQLErrorCode=x_cse_CannotDecryptSMK, State=8, LastWindowsError=-2146893813.
2024-01-13 14:50:31.93 Server Software Usage Metrics is disabled.
2024-01-13 14:50:32.36 spid7s Resource governor reconfiguration succeeded.
2024-01-13 14:50:32.40 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2024-01-13 14:50:32.42 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2024-01-13 14:50:33.00 spid7s SQL Trace ID 1 was started by login "sa".
2024-01-13 14:50:33.16 spid7s Server name is 'pc-001\mssql'. This is an informational message only. No user action is required.
2024-01-13 14:50:33.31 spid7s Starting up database 'msdb'.
2024-01-13 14:50:33.34 spid10s The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at 'D:\Users\admin_temp\Desktop\LiteSQL_Release\MSSQL\Binn\sqlservr.exe' instead of the currently attached resource database at 'Z:\MSSQL_14\MSSQL\Binn\mssqlsystemresource.mdf'.
2024-01-13 14:50:33.42 spid10s Starting up database 'mssqlsystemresource'.
2024-01-13 14:50:33.55 spid10s The resource database build version is 12.00.6449. This is an informational message only. No user action is required.
2024-01-13 14:50:33.61 spid7s 3 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2024-01-13 14:50:33.61 spid7s The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes. 2048 bytes at offset 43008 in file .\..\DATA\MSDBLog.ldf will be written.
2024-01-13 14:50:33.81 spid7s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2024-01-13 14:50:33.81 spid7s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2024-01-13 14:50:34.02 spid10s Starting up database 'model'.
2024-01-13 14:50:34.12 spid10s 3 transactions rolled forward in database 'model' (3:0). This is an informational message only. No user action is required.
2024-01-13 14:50:34.12 spid10s 0 transactions rolled back in database 'model' (3:0). This is an informational message only. No user action is required.
2024-01-13 14:50:34.13 spid10s Recovery is writing a checkpoint in database 'model' (3). This is an informational message only. No user action is required.
2024-01-13 14:50:34.29 spid10s Clearing tempdb database.
2024-01-13 14:50:34.41 spid19s A self-generated certificate was successfully loaded for encryption.
2024-01-13 14:50:34.48 spid19s Server is listening on [ 'any' <ipv6> 2434].
2024-01-13 14:50:34.48 spid19s Server is listening on [ 'any' <ipv4> 2434].
2024-01-13 14:50:34.53 spid19s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\mssql ].
2024-01-13 14:50:34.53 spid19s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$mssql\sql\query ].
2024-01-13 14:50:34.53 spid19s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2024-01-13 14:50:34.57 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2024-01-13 14:50:34.60 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.
2024-01-13 14:50:34.63 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/pc-001:mssql ] 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.
2024-01-13 14:50:34.64 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/pc-001:2434 ] 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.
2024-01-13 14:50:34.66 spid10s Starting up database 'tempdb'.
2024-01-13 14:50:34.98 spid10s The tempdb database has 1 data file(s).
2024-01-13 14:50:35.09 spid22s The Service Broker endpoint is in disabled or stopped state.
2024-01-13 14:50:35.13 spid22s The Database Mirroring endpoint is in disabled or stopped state.
2024-01-13 14:50:35.39 spid22s Service Broker manager has started.
2024-01-13 14:50:35.40 spid7s Recovery is complete. This is an informational message only. No user action is required.
|
|