CLR Stored Procedure

The Common Language Runtime (CLR) stored procedure is a .Net integration tool that enables you to better access AVEVA™ Production Management data when you use web services. The stored procedure utilizes web services to expose data through a standardized and highly-interoperable interface, which is designed to be as simple as possible for common tasks, such as reports. A common use for CLR Stored Procedure is when data is supplied to third-party reporting software.

The CLR Stored Procedure offers these benefits:

• More features and ease-of-use when AVEVA Production Management databases are queried through web services.

• More flexibility to access and supply this data to third-party reporting software.

• Maintains backwards compatibility.

Current version

For compatibility reasons, each release of the CLR Stored Procedure is carefully versioned. The version number denotes the year and the month when the procedure is released.

The following versions of the CLR Stored Procedure are available:

• About CLR Stored Procedure 2008/06

Description of parameters for current version

• GetAuditDataByLocation 2008/06

• GetDataByLocation 2008/06

Deprecated version

The following version of the CLR Stored Procedure is deprecated:

• CLR Stored Procedure 2007/06

Web Services

The CLR Stored Procedure works with, and is dependent on, a specific version of Web services.

SQL Database

The CLR Stored Procedure requires a SQL Server database that has CLR support.

Usually, you put the Stored Procedure into a separate database, other than the two AVEVA Production Management databases (configuration and data). You can install the Stored Procedure database on the same computer as Server, or on a different computer. For more information, see the specific operating requirements for each version.

Multiple stored procedures

One or many CLR stored procedures may be deployed to different SQL Server databases.

Communication Interfaces

The hosting database requires communication access to wherever the web services are located.

Related topics

• Modify the default CLR Stored Procedure parameters

• Add and configure a CLR Stored Procedure Host connection

• Generate an install script package

• Install the CLR Stored Procedure

• Register the script files in SQL Server