This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 52%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYB%3C/text%3E%3C/svg%3E)
Our online SQL Server to Azure SQL Database migration (using DMS and BACPAC both) failed to achieve Compatibility Level 170 (SQL 2025). We suspect the obsolete metadata for TEXTIMAGE_ON [PRIMARY] is blocking the compatibility upgrade due to conflicts with modern LOB handling. Please provide Microsoft documentation confirming this specific blocking issue and the recommended T-SQL solution to clean this metadata without full table recreation.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 60%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
Hi Yash Bhatia,
Could you please confirm whether the issue is occurring in the source SQL Server or after importing the BACPAC into Azure SQL Database? This will help us identify whether the problem originates from the SQL Server metadata or from the Azure SQL Database.
Facing issue on Azure SQL Database after importing from BACPAC or through DMS
If you run ALTER DATABASE CURRENT SET COMPATIBILITY_LEVEL = 170 what error message do you get?
What compatibility level are you currently on?
This command runs successfully and the COMPATIBILITY_LEVEL has been set to 170 but in the properties=>Options window it is showing blank instead of SQL Server 2025 (170).
Hi Yash Bhatia,
Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
It seems that everything has gone OK then.
I would guess that you are using an old version of SSMS which does not recognise compatibility level 170.
Go to https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms to download the most recent version of SSMS 21.
Hi Yash Bhatia,
Just checking in to see if the above answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
No Mahesh, I'm still facing same issue after updating SSMS to latest version
Hi Yash Bhatia,
Sorry for causing inconvenience.
Could you please share the exact error you’re encountering? This will help us assist you more effectively.
Thank you!
No Mahesh, I'm still facing same issue after updating SSMS to latest version
Please share a screenshot of what you see under Help->About in SSMS.
This is what I see for one of my Azure databases:
Hi Erland, I updated SSMS to latest version & now I am to see the option of SQL Server (2025). Attaching file for reference. Thanks for the suggestion
I'm glad to hear that there is a happy ending!