Update add-sensitivity-classification-transact-sql.md#9661
Update add-sensitivity-classification-transact-sql.md#9661MaxMeng1985 wants to merge 1 commit intoMicrosoftDocs:livefrom
Conversation
"SQL Server does not maintain a list of the mapping between LABEL and LABEL_ID. Also, it seems most of the parameter of this T-SQL command are optional, e.g., when we create a classification using this T-SQL command, we can provide both LABEL and LABEL_ID. Or we can provide only one of them. Also, we can set LABEL A with LABEL_ID 1 for object A, but also set LABEL A with LABEL_ID 2 for object B. if you want to ensure a one-to-one relationship between the LABEL and LABEL_ID, you need to specify both the LABEL and LABEL_ID correctly when you create a classification. " My change is to trying to clarify the above.
|
@MaxMeng1985 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 87b4d93: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? When the changes are ready for publication, add a #label:"aq-pr-triaged" |
|
Thanks @MaxMeng1985. At present the ADD CLASSIFICATION command works if any one of the parameters are supplied. If user supplies only LABEL or only INFORMATION_TYPE without corresponding IDs, the command will succeed. However, it is recommended to have one to one mapping between LABEL_ID and LABEL name. Additionally RANK parameter is not used anywhere in SQL today, so just having a rank value against a column without a LABEL or INFORMATION_TYPE will not add any value and should be avoided. TSQL will succeed if only RANK parameter is provided which has been identified as a bug and this will be addressed in future. |
@Madhumitatripathy, thanks for your comments and confirmation. That is the reason I proposed the changes. Could you please help to review it? Thanks. |
|
@MaxMeng1985 We're going to do an internal PR which takes these suggestions into account, but we will not be approving this PR directly. When the internal PR is merged, this PR will automatically close, and then the updated article will be published in the next business day. |
@rwestMSFT , thanks for the update, that works for me. |
"SQL Server does not maintain a list of the mapping between LABEL and LABEL_ID.
Also, it seems most of the parameter of this T-SQL command are optional, e.g., when we create a classification using this T-SQL command, we can provide both LABEL and LABEL_ID. Or we can provide only one of them. Also, we can set LABEL A with LABEL_ID 1 for object A, but also set LABEL A with LABEL_ID 2 for object B.
if you want to ensure a one-to-one relationship between the LABEL and LABEL_ID, you need to specify both the LABEL and LABEL_ID correctly when you create a classification. "
My change is to trying to clarify the above.