이제 sql 서버와 ssms를 설치하고 시작하려는 초보인데용.
설치 했을 때 아래와 같이 계속 에러가 발생해서 몇일간 고생했는데 해결방법은 없을까요?
포맷하고 다시 설치할 까 진지하게 고민중입니당..ㅠ
---
에러로그를 찾았는데 이렇게
2019-08-29 20:03:10.18 Server Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)
Aug 22 2017 17:04:49
Copyright (C) 2017 Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 17763: )
2019-08-29 20:03:10.18 Server UTC adjustment: 9:00
2019-08-29 20:03:10.18 Server (c) Microsoft Corporation.
2019-08-29 20:03:10.19 Server All rights reserved.
2019-08-29 20:03:10.19 Server Server process ID is 5512.
2019-08-29 20:03:10.19 Server System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model: 'X470 AORUS ULTRA GAMING'.
2019-08-29 20:03:10.19 Server Authentication mode is WINDOWS-ONLY.
2019-08-29 20:03:10.19 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2019-08-29 20:03:10.19 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2019-08-29 20:03:10.19 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2019-08-29 20:03:10.19 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2019-08-29 20:03:11.61 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-08-29 20:03:11.61 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-08-29 20:03:11.61 Server Detected 16329 MB of RAM. This is an informational message; no user action is required.
2019-08-29 20:03:11.62 Server Using conventional memory in the memory manager.
2019-08-29 20:03:11.87 Server Default collation: Korean_Wansung_CI_AS (한국어 1042)
2019-08-29 20:03:12.32 Server Buffer pool extension is already disabled. No action is necessary.
2019-08-29 20:03:12.60 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-08-29 20:03:12.60 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-08-29 20:03:12.75 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-08-29 20:03:12.76 Server This instance of SQL Server last reported using a process ID of 8268 at 2019-08-29 오전 2:36:50 (local) 2019-08-28 오후 5:36:50 (UTC). This is an informational message only; no user action is required.
2019-08-29 20:03:12.77 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.
2019-08-29 20:03:12.78 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2019-08-29 20:03:12.78 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2019-08-29 20:03:12.79 Server In-Memory OLTP initialized on standard machine.
2019-08-29 20:03:12.87 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.
2019-08-29 20:03:12.90 Server Query Store settings initialized with enabled = 1,
2019-08-29 20:03:12.90 Server Software Usage Metrics is disabled.
2019-08-29 20:03:12.96 spid5s Starting up database 'master'.
2019-08-29 20:03:12.98 Server CLR version v4.0.30319 loaded.
2019-08-29 20:03:13.22 spid5s Resource governor reconfiguration succeeded.
2019-08-29 20:03:13.22 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-08-29 20:03:13.23 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-08-29 20:03:13.25 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2019-08-29 20:03:13.30 spid5s SQL Trace ID 1 was started by login "sa".
2019-08-29 20:03:13.30 spid5s Server name is 'DESKTOP-FVNJOAJ'. This is an informational message only. No user action is required.
2019-08-29 20:03:13.45 spid17s A self-generated certificate was successfully loaded for encryption.
2019-08-29 20:03:13.45 spid17s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2019-08-29 20:03:13.45 spid17s Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2019-08-29 20:03:13.47 Server Server is listening on [ ::1 <ipv6> 1434].
2019-08-29 20:03:13.47 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2019-08-29 20:03:13.47 Server Dedicated admin connection support was established for listening locally on port 1434.
2019-08-29 20:03:13.49 spid17s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-08-29 20:03:13.49 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2019-08-29 20:03:13.49 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DESKTOP-FVNJOAJ ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-08-29 20:03:13.68 spid18s A new instance of the full-text filter daemon host process has been successfully started.
2019-08-29 20:03:13.77 spid21s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-08-29 20:03:13.78 spid21s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2019-08-29 20:03:13.78 spid5s Starting up database 'msdb'.
2019-08-29 20:03:13.78 spid12s Starting up database 'mssqlsystemresource'.
2019-08-29 20:03:13.80 spid12s The resource database build version is 14.00.1000. This is an informational message only. No user action is required.
2019-08-29 20:03:13.84 spid12s Starting up database 'model'.
2019-08-29 20:03:13.89 spid12s Polybase feature disabled.
2019-08-29 20:03:13.89 spid12s Clearing tempdb database.
2019-08-29 20:03:16.77 spid12s Starting up database 'tempdb'.
2019-08-29 20:03:19.47 spid12s Recovery completed for database tempdb (database ID 2) in 2 second(s) (analysis 476 ms, redo 0 ms, undo 100 ms.) This is an informational message only. No user action is required.
2019-08-29 20:03:29.45 spid12s The tempdb database has 8 data file(s).
2019-08-29 20:03:29.46 spid21s The Service Broker endpoint is in disabled or stopped state.
2019-08-29 20:03:29.46 spid21s The Database Mirroring endpoint is in disabled or stopped state.
2019-08-29 20:03:29.47 spid21s Service Broker manager has started.
2019-08-29 20:03:29.48 spid5s Recovery is complete. This is an informational message only. No user action is required.
2019-08-29 20:04:23.55 spid9s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 136248, committed (KB): 292268, memory utilization: 46%.
2019-08-29 20:06:15.87 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2019-08-29 20:06:15.88 spid51 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2019-08-29 20:06:15.88 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2019-08-29 20:06:15.98 spid51 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2019-08-29 20:06:15.98 spid51 Using 'xpsqlbot.dll' version '2017.140.1000' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2019-08-29 20:06:16.00 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2019-08-29 20:06:16.03 spid51 Using 'xpstar.dll' version '2017.140.1000' to execute extended stored procedure 'xp_sqlagent_notify'. This is an informational message only; no user action is required.
2019-08-29 20:08:32.90 spid54 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-08-29 20:08:32.91 spid54 Using 'xplog70.dll' version '2017.140.1000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
Comment 3
-
jevida(강성욱)
2019.08.29 13:52
-
니나니노니
2019.08.29 20:10
답변 감사합니다.
다시 설치해도 동일하네요. ㅠㅠ
포맷이 답인가요?..?
-
jevida(강성욱)
2019.08.30 01:04
다른 프로그램과의 충돌로 인한 문제면..저도 그 방법 밖에 답이 없다는 생각이 드네요..
힘내세요!
SQL 은 정상적으로 설치가 되었나요??
SSMS 문제이면 제어판에서 SSMS삭제 후 다시 설치해보시겠어요??