Three profile providers are added so that metadata stored against the imported Data Model, Data Class and Data Elements can be retrieved profiled.
In contrast to the similar PR for the PostgreSQL plugin, there is no profile at the Schema level. This is because the only properties which are stored against the schema are SQL Server Extended Properties; the names of these are not known in advance and so cannot be added to the defined profile structure.
Metadata is stored against new namespaces; separate namespaces are used so that the profile structure can be uniquely identified.
The data migration script, intended for manual use, can be used to update the namespaces of metadata on previously imported data.
Three profile providers are added so that metadata stored against the imported Data Model, Data Class and Data Elements can be retrieved profiled.
In contrast to the similar PR for the PostgreSQL plugin, there is no profile at the Schema level. This is because the only properties which are stored against the schema are SQL Server Extended Properties; the names of these are not known in advance and so cannot be added to the defined profile structure.
Metadata is stored against new namespaces; separate namespaces are used so that the profile structure can be uniquely identified.
The data migration script, intended for manual use, can be used to update the namespaces of metadata on previously imported data.