search

MauroDataMapper-Plugins / mdm-plugin-database-sqlserver

Apache License 2.0
2 stars 1 forks source link

MS SQL Server Scanner: Extended property (description) not scanned by the scanner #10

Open jelenadreskai opened 2 years ago

jelenadreskai commented 2 years ago
  1. Create a table in MS SQL Server, and add extended property "description" to on column
  2. Run SQL Server scanner on the DB updated in step 1.

Expected result:

  1. Scanned data model has description imported in the data model.
jamesrwelch commented 2 years ago

Can I just check which version of the Plugin you're using? I think this feature was only added to the most recent release. Assigning to Aaron since he worked on that

jelenadreskai commented 2 years ago

Great to hear that. May be Ok to close it then. I have MDM 4.10/6.6.0.

Where is description imported, imported as description, or a property for those elements?

aaronforshaw commented 2 years ago

@jelenadreskai in your example of adding an extended property to a column, this should be added as metadata to the Data Element.

Extended properties on schema or tables are added to the relevant Data Class metadata, and extended properties on the database are added to the Data Model. If you have a case where this is not working then please let me know.

jelenadreskai commented 2 years ago

Hi @aaronforshaw sorry I missed responding earlier. Yes, there is a MS SQL Server extended property, like a column description that is at the column level. Some teams use this to document, keep track the use of their columns. It would be good if it can be imported automatically.