Blog Post
Database compatibility level 170 in Azure SQL Database and SQL database in Microsoft Fabric
Why doesn’t the article cover what’s new in compat level 170? The linked document for IQP makes no mention of 170 either.
Thank you for the feedback. It is appreciated.
We typically provide the additional details regarding "what's new" or what has changed with a new database compatibility level, within the official ALTER DATABASE compatibility level documentation page. The current updates for that page have not been published yet, but that is in progress. We will be updating that page along with the changes for the IQP features over time and they should both be in sync over in the very near future.
We understand that this can be confusing, and we apologize for that as that was not our intent. The purpose of this blog was purposely created to be concise and to communicate that the default database compatibility has changed in Azure SQL Database and SQL database in Microsoft Fabric.
There are several features that are currently in different phases of the preview process, for example, the regular expressions functions, have surpassed their limited preview phase and the documentation for those functions are publicly documented along with the information regarding the use of database compatibility level 170 to take advantage of those functions.
Please free to reach out to us directly at IntelligentQP@microsoft.com, if you have additional questions or concerns.
- DavJarrApr 17, 2025Copper Contributor
I appreciate it’s trying to be concise but this announcement of the new default compatibility level is the perfect place to highlight what such a change tangibly means to users, even if that’s just linking to documents with further detail.
If said documents aren’t yet available then I don’t understand why the switchover has been done. It would be better if the change and the documentation could be released closer together, and I’d say ideally you’d actually want the documentation available first.