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.


  1. I guess this is a very informative and useful blog post about the happenings of Postgre SQL and many other related concepts as well.Its functionalities and usages are well justified.

    SSIS PostgreSql Write

  2. Thank you so much for providing information about SQL and SSIS and other similar aspects.

    SSIS postgresql read


Post a Comment

Plz dont forget to like Facebook Page..

Popular posts from this blog

How to encrypt and decrypt Table data in postgres

For encrypting and decrypting , we must use the bytea data type on the column which we implement. Bcoz bytea will use the pgcrypto method by default. However, you will need to create the pgcrypto extension to enable these functions as they are not pre-defined in PostgreSQL/PPAS. Example CREATE EXTENSION pgcrypto; CREATE TABLE userinfo (username varchar(20), password bytea); >>    Inserting the data in an encrypted format INSERT INTO userinfo VALUES(' suman ',encrypt('111222','password','aes')); select * from userinfo ; >>    Retrieving the data as decrypted format SELECT decrypt(password,decode('password','escape'::text),'aes'::text) FROM userinfo; Thanks for reading Plz dont forget to like Facebook Page..

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..