Sql setup error

ardaboran 21 Reputation points
2023-01-03T16:27:25.737+00:00

2023-01-03 18:48:23.84 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)
Sep 24 2019 13:48:23
Copyright (C) 2019 Microsoft Corporation
Express Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-01-03 18:48:23.84 Server UTC adjustment: 3:00
2023-01-03 18:48:23.84 Server (c) Microsoft Corporation.
2023-01-03 18:48:23.84 Server All rights reserved.
2023-01-03 18:48:23.85 Server Server process ID is 6884.
2023-01-03 18:48:23.85 Server System Manufacturer: 'LENOVO', System Model: '21A4'.
2023-01-03 18:48:23.85 Server Authentication mode is WINDOWS-ONLY.
2023-01-03 18:48:23.85 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\Log\ERRORLOG'.
2023-01-03 18:48:23.85 Server The service account is 'NT Service\MSSQL$SQLEXPRESS03'. This is an informational message; no user action is required.
2023-01-03 18:48:23.85 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\DATA\mastlog.ldf
2023-01-03 18:48:23.85 Server Command Line Startup Parameters:
-s "SQLEXPRESS03"
-m "SqlSetup"
-Q
-q "Turkish_CI_AS"
-T 4022
-T 4010
-T 3659
-T 3610
-T 8015
-d "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\Template Data\master.mdf"
-l "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\Template Data\mastlog.ldf"
2023-01-03 18:48:23.85 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2023-01-03 18:48:23.85 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-01-03 18:48:23.85 Server Detected 5966 MB of RAM. This is an informational message; no user action is required.
2023-01-03 18:48:23.85 Server Using conventional memory in the memory manager.
2023-01-03 18:48:23.86 Server Page exclusion bitmap is enabled.
2023-01-03 18:48:23.94 Server Buffer Pool: Allocating 1048576 bytes for 942080 hashPages.
2023-01-03 18:48:23.94 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2023-01-03 18:48:23.97 Server Buffer pool extension is already disabled. No action is necessary.
2023-01-03 18:48:24.00 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2023-01-03 18:48:24.02 Server Query Store settings initialized with enabled = 1,
2023-01-03 18:48:24.02 Server The maximum number of dedicated administrator connections for this instance is '1'
2023-01-03 18:48:24.03 Server This instance of SQL Server last reported using a process ID of 13400 at 3.01.2023 18:48:19 (local) 3.01.2023 15:48:19 (UTC). This is an informational message only; no user action is required.
2023-01-03 18:48:24.03 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.
2023-01-03 18:48:24.03 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.
2023-01-03 18:48:24.03 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2023-01-03 18:48:24.04 Server In-Memory OLTP initialized on lowend machine.
2023-01-03 18:48:24.06 Server [INFO] Created Extended Events session 'hkenginexesession'

2023-01-03 18:48:24.06 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.
2023-01-03 18:48:24.07 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
2023-01-03 18:48:24.07 Server Database Mirroring Transport is disabled in the endpoint configuration.
2023-01-03 18:48:24.08 Server clwb is selected for pmem flush operation.
2023-01-03 18:48:24.08 Server Software Usage Metrics is disabled.
2023-01-03 18:48:24.08 spid10s Warning ******************
2023-01-03 18:48:24.08 spid10s SQL Server started in single-user mode. This an informational message only. No user action is required.
2023-01-03 18:48:24.08 spid10s Starting up database 'master'.
2023-01-03 18:48:24.09 spid10s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\Template Data\master.mdf.
2023-01-03 18:48:24.15 Server CLR version v4.0.30319 loaded.
2023-01-03 18:48:24.25 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework6

275786-screenshot-1.png

Azure SQL Database
SQL Server | Other
0 comments No comments
{count} votes

Answer accepted by question author
  1. Erland Sommarskog 132.4K Reputation points MVP Volunteer Moderator
    2023-01-03T22:04:35.64+00:00

    2023-01-03 18:48:24.09 spid10s There have been 256 misaligned log IOs which required falling back to synchronous IO.

    This is a known issue with Windows 11 reporting disk-sector sizes that SQL Server cannot cope with. See this article from Microsoft for workarounds.


1 additional answer

Sort by: Most helpful
  1. LiHongMSFT-4306 31,616 Reputation points
    2023-01-04T03:22:23.53+00:00

    Hi @ardaboran
    Windows 11 systems tend to have system disk sector size greater than 5Kb. The article above in Erland's answer has commands that allow you to change disk sector size reading, which helps.

    Best regards,
    Li Hong


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.