search

microsoft / DacFx

DacFx, SqlPackage, and other SQL development libraries enable declarative database development and database portability across SQL versions and environments. Share feedback here on dacpacs, bacpacs, and SQL projects.
https://aka.ms/sqlpackage-ref
MIT License
340 stars 20 forks source link

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

Closed thomas-svrts closed 11 months ago

thomas-svrts commented 1 year ago

Steps to Reproduce:

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

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

image 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

thomas-svrts commented 1 year ago

more info: https://learn.microsoft.com/en-us/sql/azure-data-studio/extensions/schema-compare-extension?view=azure-sqldw-latest also related or similar as this defect: https://learn.microsoft.com/en-us/answers/questions/197495/dacpac-deploy-always-drops-and-recreates-external

kisantia commented 1 year ago

@thomas-svrts can you please check if this also happens in SSDT? This will help us narrow down where in the code path the bug is.

thomas-svrts commented 1 year ago

Does it help if I say I have the same behaviour when I use CLI tool microsoft.sqlpackage (version 16.1.8089.0 on linux build server) with the script option?

sqlpackage \
        /Action:Script \
        /SourceFile:"$(System.ArtifactsDirectory)/*******Synapse.dacpac" \
        /TargetFile:"$(System.ArtifactsDirectory)/target-acc.dacpac" \
        /TargetDatabaseName:"$(SQL-ACC-DatabaseName)" \
        /OutputPath:"$(System.ArtifactsDirectory)/scmp-acc.sql" \
        /Properties:DropObjectsNotInSource=True \
        /Properties:DropIndexesNotInSource=True \
        /Diagnostics:false \
        /DiagnosticsFile:"$(System.ArtifactsDirectory)/scmp-acc.log" \
        /Properties:"ExcludeObjectTypes=logins;Users;RoleMembership;ExternalDataSources;DatabaseWorkloadGroups;WorkloadClassifiers"

The output contains all external tables to be dropped and recreated.

kisantia commented 1 year ago

A new sqlpackage was released today that should have the fix for external tables being dropped and recreated. Can you please try it and see if that is working as expected? After that's confirmed, I can get the DacFx version used in ADS updated in insiders to a version that includes that fix.

thomas-svrts commented 1 year ago

our pipeline indeed found the new version of sqlpackage: image

but before it only takes 30 seconds to compare the entire db: image

and now it goes in some kind of memory issue after 8+ minutes: image

137 = killed by SIGKILL Exit code 137 is Linux-specific and means that your process was killed by a signal, namely SIGKILL. The main reason for a process getting killed by SIGKILL on Linux (unless you do it yourself) is running out of memory.

Our build agent has this in it's logs:

[1179114.734416] Out of memory: Killed process 2075081 (sqlpackage) total-vm:17627608kB, anon-rss:14078008kB, file-rss:0kB, shmem-rss:0kB, UID:1000
[1179115.089807] oom_reaper: reaped process 2075081 (sqlpackage), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

image

Shouldn't 16GB of RAM be enough?

thomas-svrts commented 1 year ago

We scaled our server to 32 GB and now it finishes again after 16 minutes (before it was 30 seconds), but it ate 25GB or RAM: image

AND

### the schema compare still contains all external tables as drop and recreate statements:

GO
PRINT N'Dropping SqlExternalTable [EXT].[STG_AMPM_AM_KPI]...';

GO
DROP EXTERNAL TABLE [EXT].[STG_AMPM_AM_KPI];
GO
PRINT N'Creating SqlExternalTable [EXT].[STG_AMPM_AM_KPI]...';

GO
CREATE EXTERNAL TABLE [EXT].[STG_AMPM_AM_KPI] (
    [Etex Div] NVARCHAR (200) NULL,
    [Activity] NVARCHAR (200) NULL,
    [Plant] NVARCHAR (200) NULL,
    [Machine] NVARCHAR (200) NULL,
    [Area] NVARCHAR (200) NULL,
    [Month] NVARCHAR (200) NULL,
    [CILT actual] NVARCHAR (200) NULL,
    [CILT Goal] NVARCHAR (200) NULL,
    [Tags CO actual] NVARCHAR (200) NULL,
    [Tags CO goal] NVARCHAR (200) NULL,
    [Number of tags actual] NVARCHAR (200) NULL,
    [Number of tags goal] NVARCHAR (200) NULL,
    [Breakdowns AM actual] NVARCHAR (200) NULL,
    [Breakdowns AM goal] NVARCHAR (200) NULL
)
    WITH (
    DATA_SOURCE = [bronze_datalake_dfs_core_windows_net],
    LOCATION = N'LandingZone/SharePoint/AMPM_AMKPI',
    FILE_FORMAT = [SynapseParquetFormat],
    REJECT_TYPE = VALUE,
    REJECT_VALUE = 0
    );
thomas-svrts commented 1 year ago

the diagnostics file that also has been written says that it completed fast:

Microsoft.Data.Tools.Diagnostics.Tracer Verbose: 25 : 2023-05-12T07:15:27 : Perf: Operation started (name, details): Top Level Populator,Sql90LoginPopulator
Microsoft.Data.Tools.Diagnostics.Tracer Verbose: 25 : 2023-05-12T07:15:28 : Perf: Operation ended (name, details, elapsed in ms): Top Level Populator,Sql90LoginPopulator,8
Microsoft.Data.Tools.Diagnostics.Tracer Information: 25 : 2023-05-12T07:15:29 : Perf: Operation started (name, details): CreateResolveOperation,
Microsoft.Data.Tools.Diagnostics.Tracer Information: 25 : 2023-05-12T07:15:37 : Perf: Operation ended (name, details, elapsed in ms): CreateResolveOperation,,7750
Microsoft.Data.Tools.Diagnostics.Tracer Information: 25 : 2023-05-12T07:15:37 : Perf: Operation ended (name, details, elapsed in ms): Extracting schema,,41009
Microsoft.Data.Tools.Diagnostics.Tracer Information: 25 : 2023-05-12T07:15:37 : Perf: Operation started (name, details): Validating schema,
Microsoft.Data.Tools.Diagnostics.Tracer Information: 25 : 2023-05-12T07:15:37 : Perf: Operation ended (name, details, elapsed in ms): Validating schema,,7
Microsoft.Data.Tools.Diagnostics.Tracer Information: 0 : 2023-05-12T07:15:37 : Initialized ModelSchema - elements 159
Microsoft.Data.Tools.Diagnostics.Tracer Information: 18 : 2023-05-12T07:15:44 : Time elapsed: 0:00:50.16.
Microsoft.Data.Tools.Diagnostics.Tracer Information: 0 : 2023-05-12T07:15:44 : SqlPackage completed

but after this it still takes 15+ minutes to finaly finish...


Compare source and target dacpac
Generating publish script for database '***'.
Successfully generated script to file /home/*******/selfhosted/_work/12/a/scmp-acc.sql.
Changes to connection setting default values were incorporated in a recent release.  More information is available at https://aka.ms/dacfx-connection
Time elapsed 0:16:09.00
thomas-svrts commented 1 year ago

schema compare between 2 DB's also takes fore ever in the latest ADS insiders build:

image

kisantia commented 1 year ago

@thomas-svrts can you please confirm that the external tables still be dropped and recreated is when using sqlpackage /a:script with version 162.0.52? @zijchen has tested this and has not been able to repro this behavior with the latest release.

note: ADS schema compare has not yet been updated with the latest release of DacFx bits, so it's expected that the bug is not yet fixed there.

thomas-svrts commented 1 year ago

Yes it is still appearing in sqlpackage 162.0.52

thomas-svrts commented 1 year ago

I also see in the release notes that this a slightly different issue. What has been fixed:

Deployment Fixes an issue where external tables would be dropped and redeployed despite no changes when the table definition contained SQLCMD variables. [GitHub issue](https://github.com/microsoft/DacFx/issues/249)

But our tables definition doesn't contain SQLCMD variables, Or are DATA_SOURCE and FILE_FORMAT also considered as such variables? DATA_SOURCE = [bronze_datalake_dfs_core_windows_net] FILE_FORMAT = [SynapseParquetFormat]

kisantia commented 1 year ago

@thomas-svrts can you also confirm that this happens in sqlpackage 161.6374.0 (2 releases ago)? There was a recent change in that area that caused the SQLCMD bug, so it's possible that something else was missed.

Another question - is there any difference in FileFormat? That can cause recreating external data tables.

kisantia commented 1 year ago

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

thomas-svrts commented 1 year ago

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:

SeenaAugusty commented 1 year ago

@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? If bronze_datalake_dfs_core_windows_net is pointing to other physical locations, then external tables are different even though names are same. We had an old issue where external tables where compared, differences were not shown when the external file format or external data sources were different(with same names) https://github.com/microsoft/DacFx/issues/120

thomas-svrts commented 1 year ago

Yes the external data source is pointing to a different azure storage account.

here are some demo pacpacs: dacpacs.zip

image

image

SeenaAugusty commented 1 year ago

There has been change in the external data source, so the external table is also detecting that change image image. 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.

thomas-svrts commented 1 year ago

we ignore external datasource in our production scripts: /Properties:"ExcludeObjectTypes=logins;Users;RoleMembership;ExternalDataSources;DatabaseWorkloadGroups;WorkloadClassifiers"

But isn't that the purpose of those parameters? We want to deploy from acceptance to production databases, so the physical location will always be different. Schema compare does also not compare the data inside a table.

SeenaAugusty commented 1 year ago

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.

thomas-svrts commented 1 year ago

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
SeenaAugusty commented 1 year ago

@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

thomas-svrts commented 1 year ago

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 ./ExternalResources/bronze_datalake_dfs_core_windows_net.sql

JohannesMoersch commented 1 year ago

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.

SeenaAugusty commented 1 year ago

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

abrikmanis commented 1 year ago

Since the last update as well has had terrible times and huge resource consumption when running schema compare. Same environment ar @thomas-svrts

Schema compares running for 3h+, consumes all available RAM, and then keeps churning. image

Running on stable, Version: 1.44.1 (user setup) Commit: 8f53a316fa00a98264f1ab119641cd540b5af25c Date: 2023-06-01T02:12:48.765Z VS Code: 1.70.0 Electron: 19.1.8 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0.22621

Extensions: SQL Database Projects v.1.1 SQL Server Schema Compare v1.19.0 SQL Server Dacoac v1.13.0

thomas-svrts commented 1 year ago

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?

abrikmanis commented 1 year ago

@thomas-svrts Takes sub 10sec

While schema comparing exported dacpacs - dacpac to dacpac it does same as when comparing project to database - consumes all availablable RAM and keeps churning

thomas-svrts commented 1 year ago

@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:

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
dafad-dew commented 1 year ago

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

SeenaAugusty commented 1 year ago

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