Backward Compatibility in Windows Azure SQL Database (formerly SQL Azure)
This topic contains backward compatibility information for Windows Azure SQL Database components. This content includes information about deprecated features, discontinued features, breaking changes, and behavior changes.
This section describes potentially breaking changes in SQL Database. In this release you might encounter problems with existing applications, scripts, or functionalities that were created for earlier releases of SQL Database.
SQL Database Version Change
In this release, the value returned by @@Version and SERVERPROPERTY(‘ProductVersion’) has been changed to 11.mm.bbbb.rr. This change will also be reflected in client-side APIs such as SQLGetInfo(SQL_DBMS_VER) and SqlConnection.ServerVersion. If you have existing processes that depend on the previous version number of 10.25.bbbb.rr, these will need to be updated. Additionally, the SQL Server 2008 R2 version of SQL Server Management Studio (SSMS) and Server Management Objects (SMO) will encounter problems when used against this version of SQL Database and require an update. If you are using SQL Server 2008 R2 SSMS or SMO with SQL Database, please take the following actions:
If you use SQL Server 2008 R2 Management Studio Express (SSMSE), download and install the latest version from http://go.microsoft.com/fwlink/p/?LinkId=220170.
If you use an edition of SQL Server 2008 R2 other than Express, either install Cumulative Update Package 7 for SQL Server 2008 R2 (http://support.microsoft.com/kb/2507770) or install Microsoft SQL Server 2008 R2 Service Pack 1 (Link TBD).
|You should not base application logic on the server version, as this will change between service releases. It is OK to use the server version for logging purposes.|
Increased Spatial Data Type Precision
If you have indexes that use persisted computed columns that depend on spatial data types, these may need be rebuilt after this release of SQL Database. Similarly, constraints that use persisted computed columns that depend on spatial data types must be revalidated. You can use the sys.dm_db_objects_impacted_on_version_change (Windows Azure SQL Database) system view to determine if your application is impacted by this change. For more information, see sys.dm_db_objects_impacted_on_version_change (Windows Azure SQL Database).
|While effected indexes are not disabled, and appear to cause no problems, the increase in precision may result in sub-optimal performance. It is recommended that you rebuild the index using the information provided in the sys.dm_db_objects_impacted_on_version_change (Windows Azure SQL Database) topic.|
Output clause INTO table with identity honors SET IDENTITY_INSERT setting
The Database Engine enforces checking of the IDENTITY_INSERT setting when a table is the target of the OUTPUT clause in a DML query. Previously queries could explicitly insert an identity value when inserting into a table as part of the OUTPUT clause, even when the IDENTITY_INSERT setting was OFF. This incorrect behavior is now fixed and the OUTPUT statement now raises an error in queries that used to succeed. To work around this problem, set IDENTITY_INSERT to ON.
Applies to: Windows Azure SQL Database (March 2014 release through current release).