Minor fixes for 2 pages related to "clr enabled" server config option #2999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix
hierarchyiddatatype name in "clr enabled" config optionIt was "hierarchy", which is not the actual datatype name.
I also added the
FORMATfunction to the list to give a better indication of the scope of what will not work when "lightweight pooling" is enabled.Test:
Removed unnecessary setting "show advanced options" for "clr enabled"
The "clr enabled" server config option is not an advanced option. Having the
sp_configure 'show advanced options', 1;line in the example code has been confusing many people for years.Also:
EXECto the stored procedure line because while it works without it, it only works when it's a single statement. If anyone attempts to execute twosp_configurestatements in the same batch (or any other stored procedure without preceding it withEXEC) they will get an "incorrect syntax" error. Best to always prefix stored procedures withEXEC.GObetweenEXEC sp_configure...andRECONFIGUREas it is entirely unnecessary.Test: