MSSQL database service Introduction

A service is an application running in the system background. Services generally provide some core operating system functions. MSSQL provides the following services. Service type service description SQLServer provides data storage, processing, and controlled access, and provides fast transaction processing. AnalysisServer provides Online Analytical Processing (OLAP) for business intelligence applications.

A service is an application running in the system background. Services usually provide some core operating system functions, ms SQL has the following services. Service Description SQL Server provides data storage, processing, and controlled access, and provides fast transaction processing. Analysis Server provides Online Analytical Processing (OLAP) for business intelligence applications.

Service Type

A service is an application running in the system background. Services usually provide some core operating system functions, ms SQL has the following services.

Service Type

Service Description

SQL Server

Provides data storage, processing, and controlled access, and provides fast transaction processing.

Analysis Server

Provides Online Analytical Processing (OLAP) and data mining functions for business intelligence applications.

SQL Browser

Provide SQL Server connection information to the Client Computer

FullText Search

Quickly create content and attributes of structured and semi-structured data

ReportServer

Manage, execute, present, plan, and deliver reports.

SQL Agent

Execute jobs, monitor SQL Server, trigger alarms, and allow automatic execution of certain management tasks.

SSIS Server

Provides management support for the storage and execution of SSIS packages.

Start and Stop the service

You can use the following tools to Configure Microsoft SQL Server services and start, pause, or stop these services. Of course, SQL Server Management Studio cannot start the SQL Server service,

SQL Server proxy and other services can be started.

· SQL Server Management Studio

· SQL Server Configuration Manager

· Net command

· Service

SQL Server Management Studio and SQL Server Configuration Manager do not introduce the startup service, which is very simple and commonly used. The following describes how to use the net command to start the service.

Net command

Start the default instance of SQL Server

Net start "SQL Server (MSSQLSERVER )"

Or net start MSSQLSERVER

Start a named SQL Server instance

Net start "SQL Server (GSP )"

Net start MSSQL $ GSP

Start SQL Server with startup options

Net start "SQL Server (MSSQLSERVER)"/f/m

Or

Net start MSSQLSERVER/f/m

Default start Option

Description

-D master_file_path

The full path of the master database file (usually C: \ Program Files \ Microsoft SQL Server \ MSSQL. n \ MSSQL \ Data \ master. mdf ). If this option is not provided, the existing registry parameters are used.

-E error_log_path

Full path of the Error LOG File (usually C: \ Program Files \ Microsoft SQL Server \ MSSQL. n \ MSSQL \ LOG \ ERRORLOG ). If this option is not provided, the existing registry parameters are used.

-L master_log_path

The fully qualified path of the log file of the master database (usually C: \ Program Files \ Microsoft SQL Server \ MSSQL. n \ MSSQL \ Data \ mastlog. ldf ). If this option is not specified, the existing registry parameters are used.

Some other startup options temporarily overwrite the default startup options and start the SQL Server instance.

Other startup options

Description

-C

Shorten the time to start SQL Server from a command prompt. Generally, the SQL Server database engine is started as a service by calling the Service Control Manager. Because the SQL Server database engine is not started as a service when starting from a command prompt, skip this step using-c.

-F

Start the SQL Server instance with the minimum configuration. This is useful when setting configuration values (such as excessive memory allocation) prevents server startup.

-G memory_to_reserve

Specify the total number (MB) of memory reserved when the SQL Server instance is in the process but is allocated outside the memory pool of the SQL Server instance ). Memory outside the memory pool refers to the area where SQL Server is used to load projects such as the following: expansion process. dll files, ole db access interfaces referenced by distributed queries, and automated objects referenced in Transact-SQL statements. The default value of the file size is 256 MB.

This option can be used to optimize memory allocation, but only when the physical memory exceeds the virtual memory configuration limit set by the operating system. If the memory usage requirements of SQL Server are extraordinary and the virtual address space of the SQL Server process is used, this option is suitable for such a large memory configuration. Improper use of this option will cause the SQL Server instance to fail to start or encounter runtime errors.

Unless any of the following warnings are displayed in the SQL Server Error Log, the default value of the-g parameter should be used:

"Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE "

"Failed Virtual Allocate Bytes: FAIL_VIRTUAL_COMMIT "

These messages may instruct SQL Server to try to release some of the memory pool space of SQL Server, so as to leave room for projects such as extended stored procedures. dll files or automated objects. In this case, the Hong Kong server may consider increasing the memory reserved by the-g switch.

Using a value smaller than the default value will increase the amount of available memory in the buffer pool and thread stack. in systems that do not use many extended stored procedures, distributed queries, or automated objects, this method can improve the performance of workloads that require a large amount of memory.

-H

When AWE is enabled for 32-bit SQL Server, the virtual address space is reserved for hot-added memory metadata. 32-bit AWE Requires hot memory addition, but this will occupy approximately 500 MB of virtual address space and make memory optimization more difficult. 64-bit SQL Server is not required. Hot memory addition only applies to Windows Server 2003 Enterprise Edition and Datacenter Edition. It also requires special hardware support from hardware vendors.

-M