I'm trying to deploy my local database to Azure SQL and it fails in SQL Management Studio 18, giving the following error:
One or more unsupported elements were found in the schema used as part of a data package.Error SQL46010: Procedure: [dbo].[netRemoteSiteLoad] contains a statement that is not supported on Microsoft Azure SQL Database v12. The specific error is: Incorrect syntax near Url.Error SQL46010: Procedure: [dbo].[netRemoteSiteList] contains a statement that is not supported on Microsoft Azure SQL Database v12. The specific error is: Incorrect syntax near Url.Error SQL46010: Procedure: [dbo].[netRemoteSiteSave] contains a statement that is not supported on Microsoft Azure SQL Database v12. The specific error is: Incorrect syntax near Url.(Microsoft.SqlServer.Dac)
I noticed it happens also if I simply try to export the database to a .bacpac file. Is there anything in the database structure which is not compatible with the new software? I wouldn't like to downgrade my SQL Server Management Studio version just for this error and I'm wondering if there is any action I cat take to make it work in the meanwhile.
Thanks in advance
I get the same issue with SSMS v18.1, however I'm able to generate the BACPAC file via command line with no problem. I guess the issue is related to new version of SSMS, not database structure.
Hi, just want to add here for future reference for someone. If you are getting error messages like in the first message in this thread then you might also want to check your database option 'Compatibility level' value. For example if it is SQL Server 2008 (100) it will create these kind of error messages when exporting data tier app. So you should increase it to a higher version and everything should just work.
My database compatibility level is on sql 2012, but still no luck.
I have reported this issue to MS, they suggest me upgrade to the newer version to see if the problem fixed. I received an update this morning, but haven’t got chance to test it yet.
To give everybody a small update:
I wrote to Episerver support and they suggested me to solve the compatibility issues.
I opened the stored procedures [dbo].[netRemoteSiteLoad], [dbo].[netRemoteSiteList] and [dbo].[netRemoteSiteSave] and I edited them by replacing every instance of Url with [Url] and verything worked like a charm.