Open kisantia opened 4 years ago
@kisantia Is this something due to options or something on DacFx side - if latter, let me know if you want me to take a look (I will need bit more context from you :) )
@udeeshagautam I think this is coming from DacFx? I thought that ADS was building the sqlproj the same as SSDT, but the dacpacs being built are slightly different. Do you know if there's anything different in how the dacpacs are getting built for ADS vs SSDT?
closing as won't fix as there haven't been any other complaints about this
BTW, I have the same complaint :-)
@ssreerama fyi, reopening this since a user is also running into this
When importing a sql project from AdventureWorks in ADS, then comparing it to the database, it is expected that there would be no differences found. The differences being found in #10612 are due to the IgnoreWhitespace option being set to false in ADS instead of defaulting to true like in SSDT. The quick fix is set the default for IgnoreWhitepace to true, but there's still the additional problem that the dacpac created in ADS is different than the one created in SSDT if there are DML Triggers. The annotation values of offset, header contents, etc have different values, which are the whitespace differences being found.
Steps to Reproduce:
Comparison in SSDT of ADS dacpac with database when IgnoreWhitespace=false:![image](https://user-images.githubusercontent.com/31145923/83926231-2c398700-a73e-11ea-900e-3eede327c2c6.png)
Comparing the model.xmls with the one from ADS on the left and the SSDT one on the right:![image](https://user-images.githubusercontent.com/31145923/83926204-11671280-a73e-11ea-8acf-20e7a25c9f20.png)