Programming Extended Stored Procedures

ms164734.note(ko-kr,SQL.90).gif중요:
Microsoft SQL Server의 이후 버전에서는 이 기능이 제거됩니다. 새 개발 작업에서는 이 기능을 사용하지 말고, 현재 이 기능을 사용하는 응용 프로그램은 가능한 한 빨리 수정하십시오. Use CLR integration instead.

In the past, Open Data Services was used to write server applications, such as gateways to non-SQL Server database environments. Microsoft SQL Server 2005 and SQL Server 2000 do not support the obsolete portions of the Open Data Services API. The only part of the original Open Data Services API still supported by SQL Server are the extended stored procedure functions, so the API has been renamed to the Extended Stored Procedure API.

With the emergence of newer and more powerful technologies, such as distributed queries and CLR Integration, the need for Extended Stored Procedure API applications has largely been replaced.

[!참고] If you have existing gateway applications, you cannot use the opends60.dll that ships with SQL Server 2005 to run the applications. Gateway applications are no longer supported.

Extended Stored Procedures vs. CLR Integration

In earlier releases of SQL Server, extended stored procedures (XPs) provided the only mechanism that was available for database application developers to write server-side logic that was either hard to express or impossible to write in Transact-SQL. CLR Integration provides a more robust alternative to writing such stored procedures. Furthermore, with CLR Integration, logic that used to be written in the form of stored procedures is often better expressed as table-valued functions, which allow the results constructed by the function to be queried in SELECT statements by embedding them in the FROM clause.

참고 항목

관련 자료

데이터베이스 엔진의 향상된 프로그래밍 기능
Introduction to Common Language Runtime (CLR) Integration
CLR Table-Valued Functions

도움말 및 정보

SQL Server 2005 지원 받기