Deprecated SQL Server Features in SQL Server 2014
This topic describes the deprecated features that are still available in SQL Server 2014. These features are scheduled to be removed in a future release of SQL Server. Deprecated features should not be used in new applications.
Features Not Supported in the Next Version of SQL Server
The following SQL Server Database Engine features will not be supported in the next version of SQL Server. Do not use these features in new development work, and modify applications that currently use these features as soon as possible. The Feature name column appears in trace events as the ObjectName, in performance counters and sys.dm_os_performance_counters as the instance_name. The Feature ID appears in trace events as the ObjectId.
| Category | Deprecated feature | Replacement | Feature name | Feature ID |
|---|---|---|---|---|
| Data Programmability | sys.soap_endpoints (Transact-SQL) | Windows Communications Foundation (WCF) or ASP.NET | Native XML Web Services | 22 |
| Data Programmability | sys.endpoint_webmethods (Transact-SQL) | Windows Communications Foundation (WCF) or ASP.NET | Native XML Web Services | 23 |
Slipstream Functionality
The Product Update feature was introduced in SQL Server 2012 as an extension to the Slipstream functionality that was available in SQL Server 2008 PCU1. In SQL Server 2014, the Product Update feature is the recommended method to use for slipstreaming SQL Server. Therefore the command-line parameters, /PCUSource and /CUSource, associated with original Slipstream functionality, should no longer be used. These parameters will continue to work, but may be removed in a future release of SQL Server Setup. The recommended parameter to use is /UpdateSource which combines the functionality of the original Slipstream parameters, /PCUSource and /CUSource.
For more information about Slipstream functionality that was available in SQL Server 2008 PCU1, see Slipstream a SQL Server Update (https://go.microsoft.com/fwlink/?LinkId=219945).
For information on how to use /UpdateSource to slipstream SQL Server builds, refer to the following: