Sorry, I am new for cloud technology. so external here means we only store metadata of tables in our Azure SQL database that exist in other Azure SQL database....

One more issue arose. I cannot edit my C# Scripts... I hit the button and C# won't launch... I ran the repair on VS 17 and restarted my machine...

Possibly something to do with ProtectionLevel,...

I would add an ORDER BY Id clause to your SELECT, to help ensure consistency between the two versions of the query.

Out of interest, could you explain the background to this requirement?

Have you thought about tracking down all missing schema references in the master (I assume 'dbo') schema and adding them?...

I would have expected it to report a failure in that case, but to be brutal you could add a Script Task to your OnError handler which does this:

            
May 20, 2021 at 8:11 am
            
#3885711

            
            
                                                
        

Sensitive data like passwords are usually not stored inside packages, for security reasons.

Instead, they can be stored in SSISDB environments and marked as 'sensitive'. Once you have the password stored...

What do you mean by 'external' exactly?

Assuming you have full VS Pro, yes.

I suggest you run this: https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-ver15#ssdt-for-vs-2017-standalone-installer

making sure you select 'SQL Server Integration Services' during installation. I'm not sure whether you have to uninstall your existing SSDT first.

Which version of VS are you using?

Did you install the SSIS extensions after installing SSDT? Take a look

Try right-clicking on the Payroll.dtsx package. You should see the option 'View Designer' – select that.

Is the package part of an SSIS project? It needs to be. Open the project in SSDT and then open the package.

Temp tables: instead of

declare @table table (id int)

use

create table #table (id int)

Unfortunately, that error file does not shed much light on the problem!

I can suggest some things to try:

1. Try deploying to a local database instance
2. Make sure that all packages...