Skip to main content

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option.

After connecting to SQL Azure portal when operation started to deployment below errors occurs.

Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform.

Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming.

Solution : I suggested him to create those function to locally on local database what he is deploying. He created all those functions in same database.Then tried once again.

Unfortunately New Errors ...Ooops

Error SQL71564: The element Extended Property: [dbo].[xxx].[xx].[MS_DiagramPaneCount] is not supported when used as part of a data package (bacpac).
Error SQL71564: Table Table: [dbo].[Activities] does not have a clustered index. Clustered indexes are required for inserting data in this version of SQL Server.

Reason: The reason of the this error was; SQL Azure does not support deployment without clustered index in table and with extended property on objects. Jamie thomas also wrote on sql blog. So, this error was coming.

Solution I used
  1. Created clustered index on those table where it was not.
  2. Removed extended property from objects. I used below tsql to remove.
EXEC sp_dropextendedproperty @name = 'MS_DiagramPaneCount' ,@level0type = 'schema',@level0name = 'dbo',@level1type = 'view',@level1name = 'vwPatientExport'

After all; Once again Testing …
It worked and Project deployed. Bingoo....

Thanks for reading.


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription