\nIn looking at the what's new for SQL Azure (May 2011) page, I came across the following: "Upcoming Increased Precision of Spatial Types: For the next major service release, some intrinsic functions will change and SQL Azure will support increased precision of Spatial Types."\n<\/p>\n
\nThere's a few interesting things about this announcement.\n<\/p>\n
\nFirstly, the increased precision for spatial types is not a SQL Server 2008 R2 feature. It's a Denali CTP1 feature. Although the article doesn't indicate whether they've made up a special "pre-Denali" version of this feature, or when exactly "the next major service release" will be (and when SQL Server Denali will be released is unknown), it would be interesting if updated SQL Server spatial functionality made its appearance in SQL Azure *before* making its appearence in an on-premise release of SQL Server. As far as I know, this will be the first time a new, non-deprecation feature is deployed in the cloud before on-premise (non-deprecation because, for example, the COMPUTE BY clause fails in SQL Azure but not in any on-premise RTM release of SQL Server). Note that usage of SQL Server "opaque" features (for example, are instances managed internally be a variant of the Utility Control Point concept?) cannot be determined.\n<\/p>\n
\nIn addition, this may be the first "impactful change" (BOL doesn't say breaking change, but change with a possible impact, but one never knows what the impact would be in other folks' applications) in SQL Azure Database. The BOL entry continues "This will have an impact on persisted computed columns as well as any index or constraint defined in terms of the persisted computed column. With this service release SQL Azure provides a view to help determine objects that will be impacted by the change. Query sys.dm_db_objects_impacted_on_version_change (SQL Azure Database) in each database to determine impacted objects for that database."\n<\/p>\n
\nHere's a couple of object definitions that will populate this DMV:\n<\/p>\n
\ncreate table spatial_test (
\n id int identity primary key,
\n geog geography,
\n area as geog.STArea() PERSISTED,
\n);\n<\/p>\n
\n— one row, class_desc INDEX, for the clusted index
\nselect * from sys.dm_db_objects_impacted_on_version_change\n<\/p>\n
\nALTER TABLE spatial_test
\nADD CONSTRAINT check_area CHECK (area > 50);\n<\/p>\n
\n— two more rows, class_desc OBJECT_OR_COLUMN, for the constraint object
\nselect * from sys.dm_db_objects_impacted_on_version_change\n<\/p>\n
\n
\nBefore this, the SQL Azure Database koan was "Changes are always backward-compatible". There is now the sys.dm_db_objects_impacted_on_version_change DMV and the BOL page for it even provides sample DDL to handle the impacted objects. But this begs the question: I can run the DMV to determine objects that would be impacted and fix them when the change occurs, but if I don't know when the SU will be released, how can I plan\/stage my app change to corespond? Interesting times ahead…\n<\/p>\n
\n@bobbeauch<\/p>\n","protected":false},"excerpt":{"rendered":"
In looking at the what's new for SQL Azure (May 2011) page, I came across the following: "Upcoming Increased Precision of Spatial Types: For the next major service release, some intrinsic functions will change and SQL Azure will support increased precision of Spatial Types." There's a few interesting things about this announcement. Firstly, the increased […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27,36],"tags":[],"class_list":["post-553","post","type-post","status-publish","format-standard","hentry","category-sql-azure-database","category-sql-server-spatial"],"yoast_head":"\n