search

microsoft / azuredatastudio

Azure Data Studio is a data management and development tool with connectivity to popular cloud and on-premises databases. Azure Data Studio supports Windows, macOS, and Linux, with immediate capability to connect to Azure SQL and SQL Server. Browse the extension library for more database support options including MySQL, PostgreSQL, and MongoDB.
https://learn.microsoft.com/sql/azure-data-studio
MIT License
7.53k stars 896 forks source link

Schema Compare Extension - no differences found when there should be #9802

Closed Dvnoten closed 4 years ago

Dvnoten commented 4 years ago

Situation:

Comparing two Azure SQL Single Databases using SQL Authentication (Admin account).

Error:

image

It keeps saying that no differences were found while I'm 100% sure there are a lot of differences. I enabled debug logs as well but no logs were created at all.

All help is appreciated!

kisantia commented 4 years ago

Can you try comparing the two databases using the SSDT Schema compare and see if any differences are found?

Dvnoten commented 4 years ago

Hi Kisantia,

Thanks for your reply! Unfortunately, also using the SSDT schema compare it's not working. I receive the following 'strange' error:

image

Any idea to help me troubleshooting this would be great. But I guess it's not really related to the Schema Compare Extension but more to the database itself?

Kinds regards

llali commented 4 years ago

@Dvnoten thanks for reporting the issue. the 'DABO' permission is added to DacFx and will be in next release of DacFx.

kisantia commented 4 years ago

@Dvnoten the DABO permission is now in the DacFx version in ADS. Can you try using schema compare again?

Dvnoten commented 4 years ago

@kisantia thank you for the update. I updated the SSDT extension in VS and the Azure Data Studio client but the issue remains the same. I still get the DABO permission warning in VS as illustrated above and in Azure Data Studio I still don't see any results using schema compare. Could you tell me how I can maybe better troubleshoot the exact issue or did I forgot to update something maybe?

kisantia commented 4 years ago

@Dvnoten The new DacFx bits might not be in the SSDT yet, which is why the DABO permission is still there. Would you be able to share the dacpacs of the databases so we can debug this?

kisantia commented 4 years ago

@Dvnoten any update on this?

Dvnoten commented 4 years ago

@kisantia I'm sorry for the late response. Unfortunately due to copyrighted content of a client I cannot share the dacpac files. This would expose some stored procedures and logging mechanisms that I may not share explicitly. I can try to create a dacpac file by excluding some objects but don't know if this is helpful for you.

kisantia commented 4 years ago

@Dvnoten sure it would be helpful if you can create two dacpacs that repro this behavior so we can debug this.

adsbot[bot] commented 4 years ago

This issue has been closed automatically because it needs more information and has not had recent activity in the last 7 days. If you have more info to help resolve the issue, leave a comment