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 xx.xxx.xx:function .dbo.xxx 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.


Labels:

Comments

  1. James Zicrov28 May 2021 at 00:29

    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

    ReplyDelete
  2. James Zicrov9 August 2021 at 23:19

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

    SSIS postgresql read

    ReplyDelete

Post a Comment

Plz dont forget to like Facebook Page..
https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...
34 comments
Read more

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..
5 comments
Read more

How to setup automated export on google cloud sql

We can do backup and restore on instance and DB level both. on-demand backup and automatic backup are possible at instance level only which we can configure Google Cloud Console. Database level there is no options and features available for full and differential backup like SQL server in cloud SQL database. We can do this task with Export feature this is similar to full backup and this we can do from console or portal. If we want to do automated DB export (full backup) then we should design ourselves with the help of services . Google provide some services like Google Function and Scheduler which we can use for this purpose as look like following architecture. Here is following steps which we can use to setup Create a bucket in Google Cloud Storage. Create Cloud Function to export a Cloud SQL database Grant Permission for the Cloud Function to access Cloud SQL export Test out the Cloud Function Create Cloud Scheduler Job to trigger the Cloud Function once a week  For detail or step...
4 comments
Read more