Transforming Published Data
This feature is deprecated and will be removed in a future release. This feature should not be used in new development work. Transforming published data requires the Microsoft SQL Server 2000 Data Transformation Services (DTS) runtime and only supports packages created in SQL Server 2000. The runtime is available if you upgrade from SQL Server 2000 or if you select to install it during setup. For more information, see How to: Ensure Support for Data Transformation Services Packages.
Transformable subscriptions leverage the data movement, transformation mapping, and filtering capabilities of Data Transformation Services (DTS). Using transformable subscriptions in your replication topology allows you to customize and send published data based on the requirements of individual Subscribers.
Examples of how you can use transformable subscriptions include:
- Creating column and row partitions of published data on a per-Subscriber basis.
- Creating data transformations such as data-type mappings (for example, integer to real data type), column manipulations (for example, concatenating first name and last name columns), string manipulations, and use of functions.
The option to allow transformations is set at the time you create a publication. After the option is set, and a replication DTS package is built, Subscribers to the publication can attach a DTS package and incorporate it as part of the replication data flow.
The following procedures and parameters are relevant for transformable subscriptions:
- The **@allow\_dts** parameter of sp_addpublication (Transact-SQL)
- The **@dts\_package\_name**, **@dts\_package\_password**, and **@dts\_package\_location** parameters of sp_addsubscription (Transact-SQL), sp_addpushsubscription_agent (Transact-SQL), and sp_addpullsubscription_agent (Transact-SQL)
For more information about creating DTS packages for replication and associating them with subscriptions, see the SQL Server 2000 documentation.