Synchronizing SQL Server and SharePoint list data through the CLR (i)

It's written in front.

This series of articles is divided into four parts:

1. CLR Overview.

2. Perform CLR integration programming in Visual Studio and deploy to SQL Server, including stored procedures, triggers, custom functions, custom types, and aggregations.

3. CLR integrated programming debugging and problems encountered.

4. Use the CLR to synchronize SQL Server tables and SharePoint list (from actual project applications).

This series of articles is based on the following software environments:

Windows Server 2003 Enterprise Edition Service Pack 2

Microsoft Visual Studio Team System 2008

Microsoft SQL Server 2008

Microsoft Office Sharepoint Server 2007

Objective

The CLR (Common Language Runtime) Common language runtime is a concept that Microsoft created after. NET came out. NET architecture, providing an execution environment for all. NET Framework code. Code that runs in the CLR is called managed code. The CLR provides the various functions and services required to execute a program, including Just-in-time (JIT) compilation, allocation and management of memory, mandatory type safety, exception handling, thread management, and security. Believe that the reader has been introduced in any one. NET book, and know how the CLR works. This article is going to introduce more than just. NET architecture, and more about the integration programming of the CLR. In fact, Microsoft has done a lot of preparation for the common language runtime (CLR) integration programming so that users can now use it. NET in any of the languages that put its own written functionality on any one of Microsoft's products (perhaps a bit exaggerated), such as SQL Server, Office products, and so on, this article is about the application of the CLR on SQL Server. As for the application of the CLR on other products, I will introduce it in other articles (such as VSTO, etc.).

Starting with SQL Server 2005, Microsoft has integrated the common language runtime (CLR) components in it, except that it may not have been widely used at the time (perhaps I didn't hear much about it at the time). However, this means that the user is already available. NET in any language, such as vb.net and C #. NET, etc.) to write stored procedures, triggers, user-defined types, user-defined functions, user-defined aggregations, and streaming table functions, and so on database objects for the database. The news sounds really exciting, this has made more choices for DBAs, DEV (database developers) who have been very conservative for many years, while also allowing many simple SDE (software developers) to try database development so that both the program and the backend database are tightly knit, Collaboration between developers is smoother.