Unable to commit tables with extended properties from SQL Data Catalog

robertenglehorn

We have used SQL Data Catalog to define columns with sensitive data.  The cataloging was done on Prod tables, and when doing so generated several extended properties ... on the Prod table object.  Now when using SQL Source Control those tables show as needing committed.  However, once committed the refreshed screen shows the same tables needing committed again.  The tables are NOT getting committed.  Manually committing from Git Bash says theres nothing to commit.  Short of removing the extended properties and losing the cataloging is there another option?

Victoria W

Hi @robertenglehorn

We recently fixed a bug with extended properties similar to the issue you are describing. As a first action, if you haven't already, please can you update to the latest version SQL Source Control to see if this resolves the issue you are seeing? The latest version (7.2.16) can be downloaded here: https://download.red-gate.com/checkforupdates/SQLSourceControl/SQLSourceControl_7.2.16.11965.exe 

robertenglehorn

A support ticket was created with the same suggestions as you have made.  v7.2.16.11965 was successful in resolving the issue.  Thanks...

Victoria W

Adding to your post for other users who might have the same issue.