Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This topic describes breaking changes in SQL Server. You might encounter these changes when you upgrade, and they might break applications, scripts, or functionalities that are based on earlier versions of SQL Server. For more information, see Use Upgrade Advisor to Prepare for Upgrades.
If you are upgrading from SQL Server 2005, we recommend that you also review the content in the SQL Server 2008, and SQL Server 2008 R2 sections.
If you are upgrading from SQL Server 2008, we recommend that you also review the content in the SQL Server 2008 R2 section.
Breaking Changes in SQL Server 2012
XEvent changes
resource_monitor_ring_buffer_record:
Fields removed: single_pages_kb, multiple_pages_kb
Fields added: target_kb, pages_kb
memory_node_oom_ring_buffer_recorded:
Fields removed: single_pages_kb, multiple_pages_kb
Fields added: target_kb, pages_kb
Sync Framework changes
Sync Framework is not included in the SQL Server 2012 installation package. You can download and install the appropriate version of Sync Framework from Microsoft Download Center.
Breaking Changes in SQL Server 2008 R2
New Installation parameter required for un-attended installations in SQL Server 2008 R2
Unattended installations using the /Q or /QS parameters must include the /IAcceptSQLServerLicenseTerms parameter. This parameter confirms acceptance of SQL Server license terms. For more information, see Install SQL Server 2012 from the Command Prompt.
Breaking Changes in SQL Server 2008
SMO has been reversioned in SQL Server 2008
Code developed for SQL Server 2005 SMO might not build against SQL Server 2008 without minor modifications. For more information, see Backward Compatibility in SMO.