Out-of-process configuration

You can load PI SQL Client OLEDB in an out-of-process configuration. In this case, PI SQL Client OLEDB is instantiated outside the SQL Server process, which protects the SQL Server process from errors in PI SQL Client OLEDB. If you use the out-of-process configuration, updates or inserts referencing long columns (text, ntext, or image) are not allowed.

When PI SQL Client OLEDB is instantiated out-of-process, SQL Server does not load it directly within its memory address space, instead, it creates a surrogate process that loads PI SQL Client OLEDB and uses proxy/stub pairs to marshal the requested interface transparently back to the SQL Server process. The default surrogate executable used by the DCOM Service Control Manager (Rpcss.exe) is named DllHost.exe.

You have to complete additional configuration to run PI SQL Client OLEDB out-of-process. Review all related configuration topics that follow before setting PI SQL Client OLEDB to run out-of-process. You also need to complete the linked server configuration using one of the methods outlined in Configuration methods.

You can find additional information about using an out-of-process provider in the Microsoft Developer blog, Permissions needed to set up linked server with out-of process provider.