SQL Server database schema validation, deployment, and upgrade runtime. Enables declarative database development and database portability across SQL Server versions and environments.
Doing a schema comparison in Azure Data Studio doesn't reveal any difference. However, doing a schema comparison in visual studio between the project and the database reveals that the isPersistedNullable properties on the computed columns are different.
Did this occur in prior versions? If not - which version(s) did it work in?
This issue was happening back in version 16.1.6374.0
(DacFx/SqlPackage/SSMS/Azure Data Studio)
162.2.111.2
Both
Microsoft SQL Server 2019 (RTM-CU12) (KB5004524) - 15.0.4153.1 (X64) Jul 19 2021 15:37:34 Copyright (C) 2019 Microsoft Corporation Express Edition (64-bit) on Windows 10 Enterprise 10.0 <X64> (Build 22631: ) (Hypervisor)
Steps to Reproduce:
Example project is attached here: MyTestDatabase.zip
Doing a schema comparison in Azure Data Studio doesn't reveal any difference. However, doing a schema comparison in visual studio between the project and the database reveals that the![image](https://github.com/microsoft/DacFx/assets/51305664/42dc6edf-8469-4310-bf23-c526d398823d)
isPersistedNullable
properties on the computed columns are different.Did this occur in prior versions? If not - which version(s) did it work in? This issue was happening back in version 16.1.6374.0 (DacFx/SqlPackage/SSMS/Azure Data Studio)