Description of some common DLL Functions of SQLSERVER

Description of some DLL public DLL functions if your SQLSERVER is installed on the C drive, the following path is the storage path of the corresponding SQLSERVER version public DLL SQL2005C: ProgramFilesMicrosoftSQLServer90SDKAssembliesSQL2008C: ProgramFilesMicrosoftSQLServer100SDKAssemb

Some common DLL Functions of SQLSERVER if your SQLSERVER is installed on disk C, the following path is the storage path of the common DLL of the corresponding SQLSERVER version SQL2005 C: \ Program Files \ Microsoft SQL Server \ 90 \ SDK \ Assemblies \ SQL2008 C: \ Program Files \ Microsoft SQL Server \ 100 \ SDK \ Assemb

Description of some common DLL Functions of SQLSERVER

If your SQLSERVER is installed on drive C, the following path is the storage path of the Public DLL of the corresponding SQLSERVER version.

SQL2005

C: \ Program Files \ Microsoft SQL Server \ 90 \ SDK \ Assemblies \

SQL2008

C: \ Program Files \ Microsoft SQL Server \ 100 \ SDK \ Assemblies \

SQL2012

C: \ Program Files \ Microsoft SQL Server \ 110 \ SDK \ Assemblies \

We can see that with the upgrade of the SQL Server version, these public DLL become more and more, because SQL Server has more and more functions.

What are the functions of these DLL ??

These DLL files are called by SQLSERVER, because these public DLL files are useful in many SQLSERVER components, so SQLSERVER

Place the DLL in the X: \ Program Files \ Microsoft SQL Server \ X \ SDK \ Assemblies \ folder for calling by other SQLSERVER components.

For example, SSIS, SSAS, database engine, and other tools

In fact, from the folder path name, we can know the role of these DLL: SDK \ Assemblies \

If you do not know the meaning of the SDK, you can refer to Baidu. However, it may be a lot of effort. I will post it here.

SDK (Software Development Kit) is generally used by Software engineers for specific Software packages, Software frameworks, hardware platforms, operating systems, etc.

Create a collection of development tools for application software.

Senior programmers must know the function of the SDK. It is an interface or API provided to our programmers for development.

In my opinion, the DLL under the X: \ Program Files \ Microsoft SQL Server \ X \ SDK \ Assemblies \ folder is not only provided for SQL Server to call

We can also call these DLL to develop some related software and tools for SQLSERVER database.

Example 1:

Hu Yong in the garden used the following two DLL files to CREATE a database table using. NET, similar to SQL Server's CREATE statement for writing tables.

Microsoft. SqlServer. ConnectionInfo. dll

Microsoft. SqlServer. Management. Sdk. Sfc. dll

Example 2:

Another example is this post: I made a program using c #, which is the same as the event monitor in sqlServer2005. Please check the startup Problem

Use Microsoft. SqlServer. ConnectionInfo. dll as a tool similar to SQL TRACE to view executed scripts and other information in real time.

Example 3:

SQLDoc Sharp (SQLSERVER database document Generation Tool)

This tool can be downloaded from codeproject:

The following DLL is used.

Microsoft. SqlServer. ConnectionInfo. dll

Microsoft. SqlServer. Management. Sdk. Sfc. dll

Microsoft. SqlServer. Smo. dll

Microsoft. SqlServer. SmoExtended. dll

Microsoft. SqlServer. SqlEnum. dll

What language does public DLL use?

We can find that the tools in the above three examples are all written in. NET, and SQLDoc Sharp is the winfrom software written in. NET.

We use the ILSpy software to decompile the DLL of each SQLSERVER version.

Drag all DLL files to ILSpy.

SQL2005

SQL2008

SQL2012

Two DLL files in SQL2008 cannot be decompiled, including Redist_TSqlLanguageService.dll and Redist_DACFramework.dll.

Only one DLL in SQL2012 cannot be decompiled. It is Redist_TSqlLanguageService.dll.

DLL files that cannot be decompiled may be written in C or C ++.

I estimate that these non-decompiled dll files do not provide API functions for users, but are called by SQLSERVER. These DLL files play a vital role in SQLSERVER performance.

Therefore, it is written in C or C ++.

According to the above decompilation of these DLL, a large part of SQL Server Components or code are written in. NET.

In addition to some key functions or performance-related functional components, use C or C ++ to write

Here, we can also see from the other side that Microsoft's reuse of. NET has made a lot of use of. NET to compile some component code since SQLSERVER2005.

From the above three examples, we can also see why they prefer. NET to write these tools, because these public DLL is. net dll (managed code)

DLL

Limited by my limited capabilities, I will only briefly introduce familiar DLL, other unfamiliar people can check MSDN or Baidu

Here I will provide some DLL information and the results of Baidu and MSDN queries.

I will only introduce SQLSERVER2012 here, because SQLSERVER2012 is relatively complete, but some functions will change in different SQLSERVER versions.

For example, in the second example above: I made a program using c #, which is the same as the event monitor in sqlServer2005. For startup problems, please refer

The TMO class is changed in the SQL2005 SDK and the SQL2008 SDK, which leads to an error during running.

Use Trace Management Object to monitor and diagnose SQL Server (1)

In SQL Server 2005, TMO objects are implemented in Microsoft. SqlServer. ConnectionInfo. dll,

In SQL Server 2008, the TMO object is moved to Microsoft. SqlServer. ConnectionInfoExtended. dll,

But it is still in the Microsoft. SqlServer. Management. Trace namespace.

I will not talk about the changed APIs above. You must check MSDN and Baidu during development. Don't make a mistake, because these sdks have fewer documents.

Most of them are E-files, which may be a headache for development.

Don't talk nonsense, start ~

Microsoft. AnalysisServices. DLL

Microsoft. DataWarehouse. Interfaces. DLL

SSAS, data warehouse related interfaces

Kpi type:

Microsoft. ExceptionMessageBox. DLL

The DLL is called in the exception dialog box of SQLSERVER.

? Forum = sqltools

Microsoft. ReportingServices. Interfaces. DLL

SSRS related interfaces

Microsoft. SqlServer. Smo. DLL

Microsoft. SqlServer. SmoExtended. DLL

Microsoft. SqlServer. Management. Sdk. Sfc. DLL

Microsoft. SqlServer. ConnectionInfo. DLL

Microsoft. SqlServer. ConnectionInfoExtended. DLL

SMO: SQLSERVER management object

Used to monitor SQLSERVER or connect to SQLSERVER

The SMO object function is short for SqlServer Management Ojbects. It is a Management object provided by SQL2005.

As long as SQL Server Management Studio can implement things, it can be implemented with smo, because SQL Server Management Studio is developed with smo.

If you have enough strength, you can develop a tool that can despise SQL Server Management Studio, such as adding smart sensing functions.

To support SQL Server management, Integration Services provides an enumerator that can traverse SQL management objects (SMO.

For example, you can use the SMO enumerator to perform the same management function for each job in the Jobs set of an SQL Server installation.

Microsoft. SqlServer. Dts. Design. DLL

Microsoft. SqlServer. DTSPipelineWrap. DLL

Microsoft. SQLServer. DTSRuntimeWrap. DLL

Microsoft. SQLServer. ManagedDTS. DLL

Data Transformation Services (DTS) Data transmission service-related DLL

? Forum = sqlintegrationservices

? Forum = sqlintegrationservices

Microsoft. SqlServer. Management. RegisteredServers. DLL

DLL used by the registration server

? Forum = sqlsmoanddmo

Microsoft. SqlServer. Management. Utility. DLL

Microsoft. SqlServer. Management. UtilityEnum. DLL

Utility: A Utility Class represents an SQL Server defined by a control point (UCP) to manage methods and attributes of one or more remote SQL Server instances.

UtilityEnum: the microsoft. sqlserver. management. utility namespace contains classes that display SQLSERVER utility objects.

(V = SQL .110). aspx

(SQL .105). aspx

Microsoft. SqlServer. Management. XEvent. DLL

Microsoft. SqlServer. Management. XEventEnum. DLL

DLL related to extended events

XEvent: create and use SQLSERVER Extension events in SQLSERVER client components and server components through the Common Object Model

Extended event infrastructure supports SQL Server event data relevance

In some cases, the infrastructure can also be used to obtain relevant data from the data view applications and operating systems.

Microsoft. SqlServer. OlapEnum. DLL

Olap system related DLL

Microsoft. SqlServer. Rmo. DLL

Microsoft. SqlServer. Replication. DLL

Copy-related DLL

RMO: Copy management object

? Forum = sqlreplication

? Forum = sqlreplication

IIS exceptions caused by Microsoft. SqlServer. Replication. dll

? Forum = sqlreplication

Microsoft. SqlServer. ServiceBrokerEnum. DLL

ServiceBroker related technology DLL

Microsoft. SqlServer. SqlWmiManagement. DLL

Microsoft. SqlServer. WmiEnum. DLL

DLL related to WMI (Windows Management Instrumentation, Windows Management specifications)

Open [SQL Server Configuration Manager] and prompt: you cannot connect to the WMI provider. You do not have permission or the server cannot be accessed.

Note that you can only use the SQL Server Configuration Manager to manage SQL Server 2005 servers.

How to add WMI alert to SQL Server

Microsoft. SqlServer. SString. DLL

The SecureString class contains many string-related C # functions.

Code in this class

Class: SqlSecureString