Puser wrote:
No, 'Length precision scale follow dblength precision scale' is false.
Please have this setting set to true so the model fields are synced with the target fields. Having this setting set to false means the model values aren't synced, which can be what you want in some cases hence the setting.
I sync the relational model data from both SQL server and Access DB (db first), seems wrong, but this is just the way it is (I update both from my metadata versioning manager).
With this I just mean as a remark before the conversation should go to an undisired direction. I'm not using it the way it's 'supposed' or expected to. Ignore it as a question, it's just the way I work for years. it's no problem.
Ok no problem
For my search: Where do the table and field properties from the SQLClient in the Catalog Explorer come from?
what properties in particular are you referring to? Field length etc. ? Please see the SQLServer schema retriever class in the sqlserver driver sourcecode in the sourcecode archive.
sql query:
SELECT INFORMATION_SCHEMA.COLUMNS.*,
(
SELECT COLUMNPROPERTY(OBJECT_ID(@sFullTableName), INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'IsComputed')
) AS IsComputed,
(
SELECT COLUMNPROPERTY(OBJECT_ID(@sFullTableName), INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'IsIdentity')
) AS IsIdentity,
(
SELECT COLUMNPROPERTY(OBJECT_ID(@sFullTableName), INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'IsRowGuidCol')
) AS IsRowGuidColumn,
(
SELECT COLUMNPROPERTY(OBJECT_ID('@sFullTableName'), INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'GeneratedAlwaysType')
) AS GeneratedAlwaysType
FROM INFORMATION_SCHEMA.COLUMNS
WHERE INFORMATION_SCHEMA.COLUMNS.TABLE_NAME=@sTableName
AND INFORMATION_SCHEMA.COLUMNS.TABLE_SCHEMA='<schema>'
ORDER BY INFORMATION_SCHEMA.COLUMNS.ORDINAL_POSITION ASC
where fulltablename / tablename are parameters and <schema> is replaced by e.g. dbo.