Schema compare between 2 databases with external tables doesn't work

Azure Data Studio Version: 1.43
OS Version: WIndows 11

Steps to Reproduce:

open schema compare window via project plugin
select a synapse dedicated pool with external tables as source
select a 2nd synapse dedicated pool with same external tables as target
click on compare

actual result:
All external tables are mentioned as changed
expected result:
Only external tables with different DDL/structure are listed

Both external tables have the exact same definitions. The external location bronze_datalake_dfs_core_windows_net is pointing to other physical locations.

Does this issue occur when all extensions are disabled?: N/A

Microsoft schema compare tool (part of DB projects extension

Transferred issue to the DacFx repo for easier tracking for this sqlpackage issue. @SeenaAugusty can you please help investigate this issue?

Oh nice I tested with version 161.6374.0 and that worked perfect. No external table recreation and fast.
for your information I also give my experience with:

161.8089.0. recreates all external tables
162.0.52 recreates all external table + super slow + needs 20 GB RAM

@thomas-svrts Is it possible for you to share the dacpac that I could investigate further, also to confirm, is the external data source or external file format in the external table definition different?

Yes the external data source is pointing to a different azure storage account.
you can email me at<EMAIL_ADDRESS>I will reply with some dacpacs.

There has been change in the external data source, so the external table is also detecting that change

. Also could you confirm that it drops the existing external data source and creates the external data source in the deployment script? Are the deployment steps in order like, drop the external data source, drop the external table, create the external data source and then create the external table.

There can be a scenario where we have not excluded external data sources or external file formats and it would find a difference(names can be same in source and target) and would try to drop the existing external data source or external file format then it would through this deployment error "Cannot drop the external data source 'bronze_datalake_dfs_core_windows_net' because it is used by an external table" as it is linked in the external table.(https://github.com/microsoft/DacFx/issues/120) Here it never caused a deployment error because external data source was excluded.

But renaming external data sources is less occurring then just comparing dacpacs with external tables.
We have 350+ external tables, I don't want to drop and recreate them each time.
Can you not foresee a check  that raises an error if the are still external tables linked to an external data source. Like you do for checking if a table is empty:
/*
The column [SAP].[STG_ECC_**************].[TS_**********] is being dropped, data loss could occur.
*/

IF EXISTS (select top 1 1 from [SAP].[STG_ECC_**************])
    RAISERROR (N'Rows were detected. The schema update is terminating because data loss might occur.', 16, 127) WITH NOWAIT

GO

@thomas-svrts There is an option when we do not want the external tables to be recreated, we could exclude in /Properties:"ExcludeObjectTypes=ExternalTables, but for the DacFx to have a safe deployment, it needs to compare all the dependent objects

Okay excluding all externalTables isn't an option for us.
But we have adapted our build pipelines so we use powershell to replace the values of the datalake before we build the project. Now our pipeline generates 3 dacpacs (test, acceptance and production), if we compare the correct dacpac with the correct synapse DB it works fine.
But the issue of the huge RAM consumption and slowness stays in the last version. So we need to use version 161.8089.
Is this being investigated?
powershell:
((Get-Content -path ./ExternalResources/bronze_datalake_dfs_core_windows_net.sql -Raw) -replace 'datalakeplaceholder','${{parameters.adls}}') | Set-Content -Path ./pipelines/sql/ExternalResources/bronze_datalake_dfs_core_windows_net.sql

I was experiencing the same issue with 161.8089.0 and updating to 162.0.52 fixed it, but I'm also experiencing the extreme slowness.
Deploy Report on 161.8089.0: ~60 seconds
Deploy Report on 162.0.52: >40 minutes
My setup includes ~1100 external tables in an Azure Synapse SQL DB.

Is it possible to share the dacpac to investigate the extreme slowness in publish operation?

I tried the shared dacpac's (https://github.com/microsoft/DacFx/files/11485035/dacpacs.zip) before in version ADS 1.43 with SQL Database projects 1.0.1:
It took 7 seconds to compare .
@abrikmanis Could you try to do the same compare on your device with a your version of ADS / SQL DB projects?

@SeenaAugusty I can't share the our corporate dacpacs but I enable perf logs, hopefuly you can find something that way.
some context of my tests:

using Tool 'microsoft.sqlpackage' (version '162.0.52')
perf log activated by setting env variable DACFX_PERF_TRACE=true
used command:  sqlpackage Action:Script

You can see the 99% (+10minutes) of the time goes to the compare of the SqlSchema:
2023-06-14T20:44:30.7623775Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSchema,649076
full perf log here:
2023-06-14T20:33:21.9645314Z Compare source and target dacpac
2023-06-14T20:33:21.9647097Z Generating publish script for database '***'.
2023-06-14T20:33:21.9892819Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 1 : 2023-06-14T20:33:21 : Operation started (name, details): LoadTypes,
2023-06-14T20:33:22.0348094Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 1 : 2023-06-14T20:33:22 : Operation ended (name, details, elapsed in ms): LoadTypes,,45
2023-06-14T20:33:22.2692956Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 1 : 2023-06-14T20:33:22 : Operation started (name, details): DeserializeXml,
2023-06-14T20:33:30.5157957Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 1 : 2023-06-14T20:33:30 : Operation ended (name, details, elapsed in ms): DeserializeXml,,8246
2023-06-14T20:33:30.9781398Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 1 : 2023-06-14T20:33:30 : Operation started (name, details): DeserializeXml,
2023-06-14T20:33:39.2348093Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 1 : 2023-06-14T20:33:39 : Operation ended (name, details, elapsed in ms): DeserializeXml,,8255
2023-06-14T20:33:40.6349205Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 200 : 2023-06-14T20:33:40 : Operation started (name, details): CompareStore,
2023-06-14T20:33:41.6391444Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlApplicationRole
2023-06-14T20:33:41.6494597Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlApplicationRole,9
2023-06-14T20:33:41.6496474Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlAssembly
2023-06-14T20:33:41.6497954Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAssembly,0
2023-06-14T20:33:41.6499434Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlAsymmetricKey
2023-06-14T20:33:41.6500845Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAsymmetricKey,0
2023-06-14T20:33:41.6502247Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlBrokerPriority
2023-06-14T20:33:41.6503648Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlBrokerPriority,0
2023-06-14T20:33:41.6505229Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlBuiltInServerRole
2023-06-14T20:33:41.6506981Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlBuiltInServerRole,0
2023-06-14T20:33:41.6508396Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlBuiltInType
2023-06-14T20:33:41.6618478Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlBuiltInType,11
2023-06-14T20:33:41.6620134Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlCertificate
2023-06-14T20:33:41.6621582Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlCertificate,0
2023-06-14T20:33:41.6623041Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlColumnEncryptionKey
2023-06-14T20:33:41.6624935Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlColumnEncryptionKey,0
2023-06-14T20:33:41.6626377Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlColumnMasterKey
2023-06-14T20:33:41.6627819Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlColumnMasterKey,0
2023-06-14T20:33:41.6629210Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlContract
2023-06-14T20:33:41.6630613Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlContract,0
2023-06-14T20:33:41.6632028Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlCredential
2023-06-14T20:33:41.6633431Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlCredential,0
2023-06-14T20:33:41.6634949Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlCryptographicProvider
2023-06-14T20:33:41.6636465Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlCryptographicProvider,0
2023-06-14T20:33:41.6637919Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseAuditSpecification
2023-06-14T20:33:41.6639397Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseAuditSpecification,0
2023-06-14T20:33:41.6670764Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseCredential
2023-06-14T20:33:41.6672481Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseCredential,4
2023-06-14T20:33:41.6673927Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseDdlTrigger
2023-06-14T20:33:41.6675805Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseDdlTrigger,0
2023-06-14T20:33:41.6677271Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseEncryptionKey
2023-06-14T20:33:41.6678730Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseEncryptionKey,0
2023-06-14T20:33:41.6680182Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseEventNotification
2023-06-14T20:33:41.6681653Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseEventNotification,0
2023-06-14T20:33:41.6683118Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseEventSession
2023-06-14T20:33:41.6684832Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseEventSession,0
2023-06-14T20:33:41.6686357Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseOptions
2023-06-14T20:33:41.6687786Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseOptions,0
2023-06-14T20:33:41.6689167Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlEndpoint
2023-06-14T20:33:41.6690594Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEndpoint,0
2023-06-14T20:33:41.6691992Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlErrorMessage
2023-06-14T20:33:41.6757070Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlErrorMessage,0
2023-06-14T20:33:41.6766375Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlEventSession
2023-06-14T20:33:41.6767937Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEventSession,0
2023-06-14T20:33:41.6769399Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalDataSource
2023-06-14T20:33:41.6770974Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalDataSource,4
2023-06-14T20:33:41.6772427Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalFileFormat
2023-06-14T20:33:41.6773867Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalFileFormat,0
2023-06-14T20:33:41.6776144Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalLanguage
2023-06-14T20:33:41.6777585Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalLanguage,0
2023-06-14T20:33:41.6779207Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalLibrary
2023-06-14T20:33:41.6780628Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalLibrary,0
2023-06-14T20:33:41.6782018Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalStream
2023-06-14T20:33:41.6783428Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalStream,0
2023-06-14T20:33:41.6785027Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalStreamingJob
2023-06-14T20:33:41.6786650Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalStreamingJob,0
2023-06-14T20:33:41.6788044Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlFilegroup
2023-06-14T20:33:41.6789490Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFilegroup,0
2023-06-14T20:33:41.6790903Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlFullTextCatalog
2023-06-14T20:33:41.6792324Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFullTextCatalog,0
2023-06-14T20:33:41.6793754Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlFullTextStopList
2023-06-14T20:33:41.6795466Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFullTextStopList,0
2023-06-14T20:33:41.6796943Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlGenericDatabaseScopedConfigurationOptions
2023-06-14T20:33:41.6798500Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlGenericDatabaseScopedConfigurationOptions,0
2023-06-14T20:33:41.6799949Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlLinkedServer
2023-06-14T20:33:41.6801364Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlLinkedServer,0
2023-06-14T20:33:41.6802747Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlMasterKey
2023-06-14T20:33:41.6804205Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlMasterKey,0
2023-06-14T20:33:41.6805745Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlMessageType
2023-06-14T20:33:41.6807166Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlMessageType,0
2023-06-14T20:33:41.6808853Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlPartitionFunction
2023-06-14T20:33:41.6810966Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlPartitionFunction,0
2023-06-14T20:33:41.6812395Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlPartitionScheme
2023-06-14T20:33:41.6813821Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlPartitionScheme,0
2023-06-14T20:33:41.6815366Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlQueueEventNotification
2023-06-14T20:33:41.6816834Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlQueueEventNotification,0
2023-06-14T20:33:41.6818450Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlRemoteServiceBinding
2023-06-14T20:33:41.6819885Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlRemoteServiceBinding,0
2023-06-14T20:33:41.6821307Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlResourceGovernor
2023-06-14T20:33:41.6822728Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlResourceGovernor,0
2023-06-14T20:33:41.6824216Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlResourcePool
2023-06-14T20:33:41.6825644Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlResourcePool,0
2023-06-14T20:33:41.6827023Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlRole
2023-06-14T20:33:41.6828392Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlRole,0
2023-06-14T20:33:41.6829746Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlRoute
2023-06-14T20:33:41.6831132Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlRoute,0
2023-06-14T20:33:41.6832498Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:33:41 : Operation started (name, details): CompareAllElementsForOneType,SqlSchema
**2023-06-14T20:44:30.7623775Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSchema,649076**
2023-06-14T20:44:30.7626958Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlScript
2023-06-14T20:44:30.7628446Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlScript,0
2023-06-14T20:44:30.7629898Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSearchPropertyList
2023-06-14T20:44:30.7631782Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSearchPropertyList,0
2023-06-14T20:44:30.7633204Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlServerAudit
2023-06-14T20:44:30.7634975Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlServerAudit,0
2023-06-14T20:44:30.7637488Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlServerAuditSpecification
2023-06-14T20:44:30.7639019Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlServerAuditSpecification,0
2023-06-14T20:44:30.7640698Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlServerDdlTrigger
2023-06-14T20:44:30.7642138Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlServerDdlTrigger,0
2023-06-14T20:44:30.7643586Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlServerEventNotification
2023-06-14T20:44:30.7645239Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlServerEventNotification,0
2023-06-14T20:44:30.7646667Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlServerOptions
2023-06-14T20:44:30.7648105Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlServerOptions,0
2023-06-14T20:44:30.7649485Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlService
2023-06-14T20:44:30.7678909Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlService,0
2023-06-14T20:44:30.7680656Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSymmetricKey
2023-06-14T20:44:30.7682117Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSymmetricKey,0
2023-06-14T20:44:30.7683579Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlUserDefinedServerRole
2023-06-14T20:44:30.7685193Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlUserDefinedServerRole,0
2023-06-14T20:44:30.7686642Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlWorkloadGroup
2023-06-14T20:44:30.7688055Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlWorkloadGroup,0
2023-06-14T20:44:30.7689611Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlExtendedProperty
2023-06-14T20:44:30.7691282Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExtendedProperty,0
2023-06-14T20:44:30.7692715Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlAssemblySource
2023-06-14T20:44:30.7694231Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAssemblySource,0
2023-06-14T20:44:30.7695669Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlAssemblyFile
2023-06-14T20:44:30.7697078Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAssemblyFile,0
2023-06-14T20:44:30.7698468Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSignature
2023-06-14T20:44:30.7700080Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSignature,0
2023-06-14T20:44:30.7701502Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlServerRoleMembership
2023-06-14T20:44:30.7702943Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlServerRoleMembership,0
2023-06-14T20:44:30.7704487Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlColumnEncryptionKeyValue
2023-06-14T20:44:30.7705986Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlColumnEncryptionKeyValue,0
2023-06-14T20:44:30.7707445Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlContractMessageSpecifier
2023-06-14T20:44:30.7708915Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlContractMessageSpecifier,0
2023-06-14T20:44:30.7710367Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlAuditActionGroup
2023-06-14T20:44:30.7711822Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAuditActionGroup,0
2023-06-14T20:44:30.7713268Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlAuditActionSpecification
2023-06-14T20:44:30.7714807Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAuditActionSpecification,0
2023-06-14T20:44:30.7719984Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlDynamicColumnSource
2023-06-14T20:44:30.7722630Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDynamicColumnSource,0
2023-06-14T20:44:30.7724380Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEventGroupSpecifier
2023-06-14T20:44:30.7726259Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEventGroupSpecifier,0
2023-06-14T20:44:30.7727744Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTriggerEventTypeSpecifier
2023-06-14T20:44:30.7729213Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTriggerEventTypeSpecifier,0
2023-06-14T20:44:30.7730736Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEventTypeSpecifier
2023-06-14T20:44:30.7732170Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEventTypeSpecifier,0
2023-06-14T20:44:30.7733646Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEventSessionDefinitions
2023-06-14T20:44:30.7735374Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEventSessionDefinitions,0
2023-06-14T20:44:30.7736820Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEventSessionTarget
2023-06-14T20:44:30.7738255Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEventSessionTarget,0
2023-06-14T20:44:30.7739688Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSoapLanguageSpecifier
2023-06-14T20:44:30.7741165Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSoapLanguageSpecifier,0
2023-06-14T20:44:30.7742624Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlServiceBrokerLanguageSpecifier
2023-06-14T20:44:30.7744214Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlServiceBrokerLanguageSpecifier,0
2023-06-14T20:44:30.7745732Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlDatabaseMirroringLanguageSpecifier
2023-06-14T20:44:30.7747235Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDatabaseMirroringLanguageSpecifier,0
2023-06-14T20:44:30.7748713Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlHttpProtocolSpecifier
2023-06-14T20:44:30.7750166Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlHttpProtocolSpecifier,0
2023-06-14T20:44:30.7751596Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTcpProtocolSpecifier
2023-06-14T20:44:30.7753038Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTcpProtocolSpecifier,0
2023-06-14T20:44:30.7754557Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalLanguageFile
2023-06-14T20:44:30.7756165Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalLanguageFile,0
2023-06-14T20:44:30.7757596Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalLibraryFile
2023-06-14T20:44:30.7759037Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalLibraryFile,0
2023-06-14T20:44:30.7760470Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlFile
2023-06-14T20:44:30.7761850Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFile,0
2023-06-14T20:44:30.7763367Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlLinkedServerLogin
2023-06-14T20:44:30.7765012Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlLinkedServerLogin,0
2023-06-14T20:44:30.7766428Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlPartitionValue
2023-06-14T20:44:30.7767842Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlPartitionValue,0
2023-06-14T20:44:30.7769244Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTypeSpecifier
2023-06-14T20:44:30.7770664Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTypeSpecifier,12
2023-06-14T20:44:30.7772097Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlXmlTypeSpecifier
2023-06-14T20:44:30.7773516Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlXmlTypeSpecifier,0
2023-06-14T20:44:30.7775058Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlFilegroupSpecifier
2023-06-14T20:44:30.7776490Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFilegroupSpecifier,0
2023-06-14T20:44:30.7777892Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlAggregate
2023-06-14T20:44:30.7779283Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAggregate,0
2023-06-14T20:44:30.7780685Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlDefault
2023-06-14T20:44:30.7782066Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDefault,0
2023-06-14T20:44:30.7783446Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlExternalTable
2023-06-14T20:44:30.7785110Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlExternalTable,0
2023-06-14T20:44:30.7786501Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlFileTable
2023-06-14T20:44:30.7787892Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFileTable,0
2023-06-14T20:44:30.7789312Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlInlineTableValuedFunction
2023-06-14T20:44:30.7790822Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlInlineTableValuedFunction,0
2023-06-14T20:44:30.7792303Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlMultiStatementTableValuedFunction
2023-06-14T20:44:30.7793927Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlMultiStatementTableValuedFunction,0
2023-06-14T20:44:30.7795455Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlProcedure
2023-06-14T20:44:30.7796839Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlProcedure,0
2023-06-14T20:44:30.7798206Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlQueue
2023-06-14T20:44:30.7799663Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlQueue,0
2023-06-14T20:44:30.7801055Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlRule
2023-06-14T20:44:30.7802418Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlRule,0
2023-06-14T20:44:30.7803796Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlScalarFunction
2023-06-14T20:44:30.7805299Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlScalarFunction,0
2023-06-14T20:44:30.7806698Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSecurityPolicy
2023-06-14T20:44:30.7808112Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSecurityPolicy,0
2023-06-14T20:44:30.7809502Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSequence
2023-06-14T20:44:30.7810893Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSequence,0
2023-06-14T20:44:30.7812261Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSynonym
2023-06-14T20:44:30.7813640Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSynonym,0
2023-06-14T20:44:30.7815269Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTable
2023-06-14T20:44:30.7816640Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTable,0
2023-06-14T20:44:30.7818017Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableType
2023-06-14T20:44:30.7819420Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableType,0
2023-06-14T20:44:30.7820820Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlUserDefinedDataType
2023-06-14T20:44:30.7822265Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlUserDefinedDataType,0
2023-06-14T20:44:30.7823799Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlUserDefinedType
2023-06-14T20:44:30.7825303Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlUserDefinedType,0
2023-06-14T20:44:30.7828374Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlView
2023-06-14T20:44:30.7829735Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlView,4
2023-06-14T20:44:30.7831153Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlXmlSchemaCollection
2023-06-14T20:44:30.7832616Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlXmlSchemaCollection,0
2023-06-14T20:44:30.7834121Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSearchProperty
2023-06-14T20:44:30.7835631Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSearchProperty,0
2023-06-14T20:44:30.7837083Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSymmetricKeyEncryptionPassword
2023-06-14T20:44:30.7838569Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSymmetricKeyEncryptionPassword,0
2023-06-14T20:44:30.7840070Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSignatureEncryptionMechanism
2023-06-14T20:44:30.7841561Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSignatureEncryptionMechanism,0
2023-06-14T20:44:30.7842980Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlAuditAction
2023-06-14T20:44:30.7844457Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlAuditAction,0
2023-06-14T20:44:30.7846029Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlColumnStoreIndex
2023-06-14T20:44:30.7847462Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlColumnStoreIndex,0
2023-06-14T20:44:30.7848869Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlDmlTrigger
2023-06-14T20:44:30.7850275Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDmlTrigger,0
2023-06-14T20:44:30.7851773Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlColumnSet
2023-06-14T20:44:30.7853167Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlColumnSet,0
2023-06-14T20:44:30.7854799Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlComputedColumn
2023-06-14T20:44:30.8063240Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlComputedColumn,33
2023-06-14T20:44:30.8065117Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSimpleColumn
2023-06-14T20:44:30.8301878Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSimpleColumn,11
2023-06-14T20:44:30.8351067Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlIndex
2023-06-14T20:44:30.8352691Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlIndex,0
2023-06-14T20:44:30.8354196Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEventSessionAction
2023-06-14T20:44:30.8355662Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEventSessionAction,0
2023-06-14T20:44:30.8357019Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEventSessionSetting
2023-06-14T20:44:30.8358408Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEventSessionSetting,0
2023-06-14T20:44:30.8359792Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSoapMethodSpecification
2023-06-14T20:44:30.8361170Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSoapMethodSpecification,0
2023-06-14T20:44:30.8362524Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSubroutineParameter
2023-06-14T20:44:30.8363893Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSubroutineParameter,0
2023-06-14T20:44:30.8365402Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlCheckConstraint
2023-06-14T20:44:30.8367010Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlCheckConstraint,0
2023-06-14T20:44:30.8368338Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlDefaultConstraint
2023-06-14T20:44:30.8369676Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDefaultConstraint,0
2023-06-14T20:44:30.8370986Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEdgeConstraint
2023-06-14T20:44:30.8372312Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEdgeConstraint,0
2023-06-14T20:44:30.8374340Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlDataCompressionOption
2023-06-14T20:44:30.8376583Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDataCompressionOption,0
2023-06-14T20:44:30.8377943Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlXmlCompressionOption
2023-06-14T20:44:30.8379288Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlXmlCompressionOption,0
2023-06-14T20:44:30.8380628Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlForeignKeyConstraint
2023-06-14T20:44:30.8382008Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlForeignKeyConstraint,0
2023-06-14T20:44:30.8383454Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlFullTextIndex
2023-06-14T20:44:30.8384888Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFullTextIndex,0
2023-06-14T20:44:30.8386270Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlPrimaryKeyConstraint
2023-06-14T20:44:30.8387615Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlPrimaryKeyConstraint,0
2023-06-14T20:44:30.8388937Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlStatistic
2023-06-14T20:44:30.8390254Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlStatistic,0
2023-06-14T20:44:30.8391562Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlUniqueConstraint
2023-06-14T20:44:30.8392884Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlUniqueConstraint,0
2023-06-14T20:44:30.8394318Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlScriptFunctionImplementation
2023-06-14T20:44:30.8395932Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlScriptFunctionImplementation,0
2023-06-14T20:44:30.8397299Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlClrFunctionImplementation
2023-06-14T20:44:30.8398673Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlClrFunctionImplementation,0
2023-06-14T20:44:30.8400039Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSecurityPredicate
2023-06-14T20:44:30.8401373Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSecurityPredicate,0
2023-06-14T20:44:30.8402803Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSelectiveXmlIndex
2023-06-14T20:44:30.8404216Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSelectiveXmlIndex,0
2023-06-14T20:44:30.8405605Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlSpatialIndex
2023-06-14T20:44:30.8406913Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlSpatialIndex,0
2023-06-14T20:44:30.8408256Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlDataRetention
2023-06-14T20:44:30.8409582Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlDataRetention,0
2023-06-14T20:44:30.8410928Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTablePartitionSpecification
2023-06-14T20:44:30.8412300Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTablePartitionSpecification,0
2023-06-14T20:44:30.8413605Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlXmlIndex
2023-06-14T20:44:30.8415010Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlXmlIndex,0
2023-06-14T20:44:30.8416413Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypeSimpleColumn
2023-06-14T20:44:30.8417785Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypeSimpleColumn,0
2023-06-14T20:44:30.8419128Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypeComputedColumn
2023-06-14T20:44:30.8420485Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypeComputedColumn,0
2023-06-14T20:44:30.8421840Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypeUniqueConstraint
2023-06-14T20:44:30.8423348Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypeUniqueConstraint,0
2023-06-14T20:44:30.8424817Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypePrimaryKeyConstraint
2023-06-14T20:44:30.8426275Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypePrimaryKeyConstraint,0
2023-06-14T20:44:30.8427642Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypeDefaultConstraint
2023-06-14T20:44:30.8429005Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypeDefaultConstraint,0
2023-06-14T20:44:30.8430492Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypeCheckConstraint
2023-06-14T20:44:30.8431854Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypeCheckConstraint,0
2023-06-14T20:44:30.8433183Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypeIndex
2023-06-14T20:44:30.8434618Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypeIndex,0
2023-06-14T20:44:30.8435916Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlClrMethod
2023-06-14T20:44:30.8437214Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlClrMethod,0
2023-06-14T20:44:30.8438511Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlClrProperty
2023-06-14T20:44:30.8439814Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlClrProperty,0
2023-06-14T20:44:30.8441142Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlIndexedColumnSpecification
2023-06-14T20:44:30.8442507Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlIndexedColumnSpecification,2
2023-06-14T20:44:30.8443884Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlEdgeConstraintClause
2023-06-14T20:44:30.8445298Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlEdgeConstraintClause,0
2023-06-14T20:44:30.8446637Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlFullTextIndexColumnSpecifier
2023-06-14T20:44:30.8448091Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlFullTextIndexColumnSpecifier,0
2023-06-14T20:44:30.8449487Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlClrFunctionOrderedColumnSpecification
2023-06-14T20:44:30.8451045Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlClrFunctionOrderedColumnSpecification,0
2023-06-14T20:44:30.8452456Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlPromotedNodePathForXQueryType
2023-06-14T20:44:30.8453875Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlPromotedNodePathForXQueryType,0
2023-06-14T20:44:30.8455372Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlPromotedNodePathForSqlType
2023-06-14T20:44:30.8456748Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlPromotedNodePathForSqlType,0
2023-06-14T20:44:30.8458186Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlXmlNamespace
2023-06-14T20:44:30.8459498Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlXmlNamespace,0
2023-06-14T20:44:30.8460870Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlTableTypeIndexedColumnSpecification
2023-06-14T20:44:30.8462286Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlTableTypeIndexedColumnSpecification,0
2023-06-14T20:44:30.8463638Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation started (name, details): CompareAllElementsForOneType,SqlClrMethodParameter
2023-06-14T20:44:30.8465136Z Microsoft.Data.Tools.Diagnostics.PerfTracer Verbose: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareAllElementsForOneType,SqlClrMethodParameter,0
2023-06-14T20:44:30.8466435Z Microsoft.Data.Tools.Diagnostics.PerfTracer Information: 200 : 2023-06-14T20:44:30 : Operation ended (name, details, elapsed in ms): CompareStore,,650189
2023-06-14T20:44:31.7383490Z Successfully generated script to file /home/************/selfhosted/_work/12/a/scmp-acc.sql.
2023-06-14T20:44:31.7385259Z Changes to connection setting default values were incorporated in a recent release.  More information is available at https://aka.ms/dacfx-connection
2023-06-14T20:44:31.7386255Z Time elapsed 0:11:09.96

I have a SQL Server 2019 database with external (Oracle) tables. The bug fix here has worked for this scenario.
Prior to version 162.0.52, all external tables would get recreated with every deployment - which took hours.
After upgrading to 162.0.52, the schema comparison works: only changed external tables are recreated.
The issue raised 12th May by @thomas-svrts may well be Synapse-specific, and possibly related to the code change done to fix the original issue here? This sounds like the same bug: https://github.com/actions/runner-images/issues/7795

Hi @thomas-svrts, could you try it with the preview version NuGet Gallery | Microsoft.SqlServer.DacFx 162.1.80-preview


config for different datasets

Hello, thank you for your innovative work.
I would like to ask how the config of different datasets is determined?

The config for different datasets is mostly the same, only some data related parameters should change. There are numbers of issues where I already talked about config parameters. You can search in these previous issues for more details.
A few example:
https://github.com/HuguesTHOMAS/KPConv-PyTorch/issues/90
https://github.com/HuguesTHOMAS/KPConv-PyTorch/issues/72
https://github.com/HuguesTHOMAS/KPConv-PyTorch/issues/5

Thanks. I have another question: which variable represents each point feature or the extracted point feature.

The point features are in the outputs of the network:
https://github.com/HuguesTHOMAS/KPConv-PyTorch/blob/73e444d486cd6cb56122c3dd410e51c734064cfe/utils/trainer.py#L188
You can see them used in the validation function:
https://github.com/HuguesTHOMAS/KPConv-PyTorch/blob/73e444d486cd6cb56122c3dd410e51c734064cfe/utils/trainer.py#L480-L484


logging.disable(logging.INFO) conflicts with Shiny's logging and also prevents it from launching browser on start ("--launch-browser")

I am currently using the logging package in my code, and Shiny also depends on it for message logging. So how can I disable logging only in my code? logging.disable(logging.INFO) not only disables Shiny logs but also prevents it from launching the browser on start ("--launch-browser" doesn't work).
The answer is not to use the root logger, create a new one instead. However, blocking "--launch-browser" while disabling the root logger is weird.

Yeah, it's very surprising, but we use log interception to know when uvicorn's child process (that actually runs the Shiny app) is ready to handle requests. It's weird and fragile but the other approaches all had worse downsides. That said, we could detect that the root logger is disabled and use a fallback strategy (like spawning a thread that repeatedly tries to establish a socket connection).


Data from Italy

Italian data in Excel format is here
Little more than half of that data is in 6.1 database, but needs to be improved to go through FHIR validation.
See 6.1 import/transformation logic and ask Francesco about challenges they've already overcome.
Prefer SPOR codes (or provide appropriate code system).
Focus on the selection of 4 substances  (amlodipine, carbamazepine, ibuprofen, simvastatine), which should be 242 medicinal product packages:
•	amlodipine 91
•	carbamazepine 7
•	ibuprofen  39
•	simvastatine 105.
(issue created/assigned according to what was agreed in the meeting, please react if I got something wrong)
Linked to #69.

DataWizard is starting new import from Italian data.

The Italian data are on the server, maybe a few things need to be fixed, but we can use them for testing.
Later I will update the repo with the uploaded data file.


ignore

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 12 committers have signed the CLA.:white_check_mark: jkuklis:white_check_mark: alesapin:white_check_mark: CurtizJ:white_check_mark: rschu1ze:white_check_mark: kssenii:x: danieljurek:x: azure-sdk:x: LarryOsterman:x: jsquire:x: Jinming-Hu:x: RickWinter:x: vhvb1989You have signed the CLA already but the status is still pending? Let us recheck it.


Publish

Docs Build status updates of commit 84b25d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.vscode/settings.json
:white_check_mark:Succeeded

docs/develop/common-coding-issues.md
:white_check_mark:Succeeded
View

docs/excel/co-authoring-in-excel-add-ins.md
:white_check_mark:Succeeded
View

docs/outlook/authenticate-a-user-with-an-sso-token.md
:white_check_mark:Succeeded
View

docs/outlook/delegate-access.md
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart.md
:white_check_mark:Succeeded
View

docs/reference/objectmodel/preview-requirement-set/outlook-requirement-set-preview.md
:white_check_mark:Succeeded
View

docs/testing/clear-cache.md
:white_check_mark:Succeeded
View

docs/testing/debug-with-vs-extension.md
:white_check_mark:Succeeded
View

docs/testing/testing-and-troubleshooting.md
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Crowd SSO Support Enabler/Disabler

Request by someone to enable crowd SSO support.
Described here Integrating Crowd with Atlassian JIRA
Todo:
Environment variable to enable the following entry:
file:  JIRA/atlassian-jira/WEB-INF/classes/seraph-config.xml
Comment-Out: <!--<authenticator class="com.atlassian.jira.security.login.JiraSeraphAuthenticator"/>-->
Un-Comment: <authenticator class="com.atlassian.jira.security.login.SSOSeraphAuthenticator"/>
And vice versa.

Very similar for most of the products.
Bitbucket: bitbucket.properties add plugin.auth-crowd.sso.enabled=true
Confluence: seraph-config.xml uncomment.
JIRA / ServiceDesk: seraph-config.xml uncomment.

We should make a ticket in each repository separately in order to be able to track its readiness.

Implemented, released and ready to be tested!


bugfix: add visual feedback for clicked button

Clicking on a button does not currently give any feedback to the user that their click was registered or that any action will take place.
Darkening by 15% seems to be a clear and reasonable indicator.

Thanks! Added to v1.8: https://github.com/andybrewer/mvp/releases/tag/v1.8

Is it just me or does this effect not work any more?
I can't see a color difference after click on button. :hover filter not overridden.


[UIKit] error when sending mark as delivered

Need to verify this is plugin or android chat sdk issue
10-12 15:11:08.977 24353-24378/io.skygear.chatexample E/Volley: [2944] BasicNetwork.performRequest: Unexpected response code 400 for https://carmenlau.staging.skygeario.com/chat/mark_as_delivered

Cannot reproduce other updated plugin, close it for now

@carmenlau please write down the steps to reproduce the issue.

It will apply just after I send out a message

@carmenlau  are you using the latest chat plugin ?
It cannot be reproduced in master branch


Incompatible with remix.js due to module resolution

Reproduction: https://stackblitz.com/edit/remix-run-remix-wm8xuf?file=app%2Froutes%2F_index.tsx

If you try with useNextCalendarApp, nothing shows up.

Notice, if you try to remove module type from package.json, vite reports The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.

I just tried it out in a local Remix app now, and got the calendar to render through making sure the calendar component only renders in the browser, and through removing "type": "module" in package.json of @schedule-x/react
https://github.com/tomosterlund/remix-test
Need to look into this a bit further, but it seems that in Remix you basically need to do what ClientOnly does in Nextjs, i.e. excluding the calendar from the server bundle

OK, I got it now I think. The setup with remix and vite for some reason requires the commonjs file to be named index.cjs instead of index.cjs.js. Then everything works out of the box.
Seems like vite might not support commonjs files without the cjs extension (though I've seen the {filename}.cjs.js naming pattern in numerous libraries out there). I posted in the Vite Discord: https://discord.com/channels/804011606160703521/1235103401742962698/1235103401742962698

Tried it out in the repo linked above now too with the version I just released, and works fine now :)
Let me know if this does the trick for you too

Yeah, maybe I should have said something about the *.cjs.js, it seemed odd but my knowledge in this area is a bit weak.
Wow, great work on getting a fix in so quickly 🎉

I just tried it out in a local Remix app now, and got the calendar to render through making sure the calendar component only renders in the browser, and through removing "type": "module" in package.json of @schedule-x/react
https://github.com/tomosterlund/remix-test
Need to look into this a bit further, but it seems that in Remix you basically need to do what ClientOnly does in Nextjs, i.e. excluding the calendar from the server bundle

There's a <NoSsr> tag in MUI I use for this. I was curious about a remix-only solution. The file convention component.clent.tsx will prevent that code from being included in the server bundle, see this.


Added "/" to avoid the following warning when using namespaces:

Added "/" to avoid the following warning when using namespaces:
Ignoring initial pose in frame "map"; initial poses must be in the global frame, "/map"
It allows multi_robot configurations

This seems like a hack that makes this work for your particular scenario, but likely breaks some other behavior.
Can you do the same thing by setting your fixed frame to /map when using rviz, instead of making a code change?

Thanks for the suggestion and the pull request.
The correct thing to put there would be /map; implicitly adding a / is not feasible in my opinion, because it would allow a user to intentionally pass a relative frame name and have it unintentionally interpreted as a global frame, potentially not producing an error message or warning message, but instead a logical error, which is hard to notice and track down.
If you think that this is really needed, then please expand more on why you think that, including arguments about how it would be used by different users and rational on how your fix addresses the different use cases. For example, what would happen with your current pull request if context_->getFixedFrame().toStdString() already had a leading /?
I'm going to close this, if you update it with more information I'm happy to reopen the pull request.


page has headers and body text as one big hyperlink

In sections "Background Thread Example" and "Async/Await example", the section headers and paragraph text are displayed as a hyperlink.
I think the problem is that the page has each of those section inside an anchor element.  Usually sections have an h2 element that contains an anchor element.  Seems like these two problematic sections got that kind of switched up.
Good section header on the page:

    UI Thread Execution

First bad section:

Background Thread Example

 ...

 ...

...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ce237171-03a8-e451-1396-392666317a1d
Version Independent ID: f77537a3-fea5-706a-6df4-b9f608e210b5
Content: Working with the UI Thread in Xamarin.iOS - Xamarin
Content Source: docs/ios/user-interface/ios-ui/ui-thread.md
Product: xamarin
Technology: xamarin-ios
GitHub Login: @davidortinau
Microsoft Alias: daortin

Same issue on another page.

Hi @jmegner
Thanks for opening this issue. The issue was caused by an updated version of markdig that's used by the docs build system. It handles HTML that's embedded in markdown more strictly. I've updated all the affected pages, and so the issue is now fixed.


Add support for JDBC client for queries

Currently Pinot provides a Java client and a Golang client for querying the database. However, some of the UI tools don't support the custom clients. JDBC is the default API for querying in a lot of databases and so a Client needs to be written to support  it.

We had an issue for this: https://github.com/apache/incubator-pinot/issues/4978
Will close that one. Copying over the description from that on to this issue:
Provide a jdbc driver implementation for accessing Pinot from Java.
This can go in a module of its own pinot-jdbc-client
The existing pinot-client is not a jdbc client. It has many custom APIs in its ResultSet interface. The query execution has very specific switches between pql and sql.
The jdbc-client should be as simple as
PinotConnection connection = ....
Statement statement = connection.createStatement();
ResultSet rs = statement.executeQuery(sql);
while(rs.next()) {
  rs.get(
}


Cope with the removal of sys/sysctl.h in recent glibc/kernel.

Hi,
We had this small patch since couple of years on our Amadeus fork. Since I am rebasing our Amadeus fork on yours, I am contributing this in your repository ;)
I tried to compile this (and re-generate the autotools files using autoreconf --install) in a fedora 36 docker mage, where sys/sysctl.h has already disappeared.
Cheers,
Romain

Thanks!


Does the script joins automatically my game?

hi, i want to join a public agar server and use the scripts..
the config asks for server ip, isnt this updated automatically via the user script?

yes, ip is set automatically - please do not use on public server

well on my "own" server
[root@agar agario-feeder-bot-master]# npm install package.json
npm ERR! not a package /root/tmp/npm-30184/1453936351786-0.9111451699864119/tmp.tgz
npm http GET https://registry.npmjs.org/package.json
npm http 304 https://registry.npmjs.org/package.json

@davidmann4  dude, what am i supposed to do with the config then? idk what i should put, it asks for ip.... .

and what are "install all the modules"..

ip setting is not used at all - it is a bug
npm install package.json


Registry issue with Aliyun OSS storage driver

I setup a private registry with Aliyun OSS as the backend storage, and to save cost, I use internal Aliyun OSS endpoint instead of public endpoint, because it does not cost money to read/write object from/to oss in internal network.
The private registry works fine when pushing an image (through internet or internal network), because registry helps pushing image data to OSS.
However, when pulling an image (through internet), it does not work, because registry just tells docker client the URL of the objects in OSS, so that the docker client can directly pull the image object from Aliyun OSS. Since the URL given by registry is an internal URL, it is unreachable from internet, so the pull will fail.
The problem can be solved if we configure public OSS endpoint as storage driver for registry. However, this will bring additional cost, because Aliyun OSS costs money for in/out data through internet, and does not cost any if the data in/out through internal network.
So I think this is a bug of registry v2.6. when pulling, registry should also act like a delegator, who should pull image data from OSS to registry, and then pass through the data to docker client.

This is configurable, please look at this page and disable the redirect:
https://docs.docker.com/registry/configuration/#redirect

Closing as answered and outdated.