SQL Compare not aware of *.sql files when using VS sqlproj file
dariohru
Posts: 1 New member
in SQL Compare
In VS project, within sqlproj file we have definitions which includes *.sql files for Build part in xml
e.g. <ItemGroup><Build Include="cpaas\Views\*.sql" />...
Problem is that SQLCompare is not aware of "*.sql" specified in Build part so when comparing with database with scripts folder, all of the files with *.sql are not seen by SQLCompare so it "thinks" that it needs to deploy new file even if files do exist. After deploy, SQLCompare adds each file to Build xml part even tho we do have *.sql specified in .sqlproj file.
VS is working normally with *.sql setting and is aware of this.
Is there some setting in SQLCompare where this can be included or will there be some future plans to support this?
e.g. <ItemGroup><Build Include="cpaas\Views\*.sql" />...
Problem is that SQLCompare is not aware of "*.sql" specified in Build part so when comparing with database with scripts folder, all of the files with *.sql are not seen by SQLCompare so it "thinks" that it needs to deploy new file even if files do exist. After deploy, SQLCompare adds each file to Build xml part even tho we do have *.sql specified in .sqlproj file.
VS is working normally with *.sql setting and is aware of this.
Is there some setting in SQLCompare where this can be included or will there be some future plans to support this?
Tagged:
Answers
Unfortunately, SSDT projects aren't supported in SQL Compare.
If you wish for this to be supported, please post here for suggestions: https://redgate.uservoice.com/forums/141379-sql-compare
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?