0 out of 1 rated this helpful - Rate this topic

Backward Compatibility

This topic contains backward compatibility information for SQL Azure Database components. This content includes information about deprecated features, discontinued features, breaking changes, and behavior changes.

Breaking Changes

This section describes potentially breaking changes in SQL Azure. In this release you might encounter problems with existing applications, scripts, or functionalities that were created for earlier releases of SQL Azure.

SQL Azure 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 Azure and require an update. If you are using SQL Server 2008 R2 SSMS or SMO with SQL Azure, please take the following actions:

noteNote
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 Azure. 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 (SQL Azure 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 (SQL Azure Database).

noteNote
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 (SQL Azure Database) topic.

See Also

Did you find this helpful?
(1500 characters remaining)