Skip to content

Fix some numbers and Add some internal configurations#6779

Closed
taroarai wants to merge 1 commit intoMicrosoftDocs:livefrom
taroarai:patch-18
Closed

Fix some numbers and Add some internal configurations#6779
taroarai wants to merge 1 commit intoMicrosoftDocs:livefrom
taroarai:patch-18

Conversation

@taroarai
Copy link
Copy Markdown
Contributor

@taroarai taroarai commented Sep 4, 2021

Here are my research result for each configuration that is different from SQL Server 2019.

  • access check cache bucket count
    From the code, it use 16384 for x86 and 65536 for x64, but as all supported versions are x64 only now, I change it to 65536.

  • ADR cleaner retry timeout (min)
    Actual default values is 0 when first started after clean setup, but I'm still investigating if 0 is ok or not.

  • ADR Preallocation Factor
    Actual default values is 0 when first started after clean setup, but when 0 is set, it will use 4 from the code.

  • allow filesystem enumeration
    I think it is internal, but customers can see from sp_configure or sys.configurations, we should document this, so some customers happen to changed, they can change back to default.

  • column encryption enclave type
    Max values is 2 from sp_configure or sys.configurations, but 1 is supported value as VSM.
    I guess 2 is used for Azure SQL Database with SGX.

  • min server memory (MB)
    Run_value will use 16 MB if Configure_values is lower, so I added a comment.

  • version high part of SQL Server / version low part of SQL Server
    It is also internal, and used for replicated master, but the same as "allow filesystem enumeration", customers can see it, so it is better to have default values on here.

Here are my research result for each configuration that is different from SQL Server 2019.

- access check cache bucket count
From the code, it use 16384 for x86 and 65536 for x64, but as all supported versions are x64 only now, I change it to 65536.

- ADR cleaner retry timeout (min)
Actual default values is 0 when first started after clean setup, but I'm still investigating if 0 is ok or not.

- ADR Preallocation Factor
Actual default values is 0 when first started after clean setup, but when 0 is set, it will use 4 from the code.

- allow filesystem enumeration
I think it is internal, but customers can see from sp_configure or sys.configurations, we should document this, so some customers happen to changed, they can change back to default.

- column encryption enclave type
Max values is 2 from sp_configure or sys.configurations, but 1 is supported value as VSM.
I guess 2 is used for Azure SQL Database with SGX.

- min server memory (MB)
Run_value will use 16 MB if Configure_values is lower, so I added a comment.

- version high part of SQL Server / version low part of SQL Server
It is also internal, and used for replicated master, but the same as "allow filesystem enumeration", customers can see it, so it is better to have default values on here.
@PRMerger8
Copy link
Copy Markdown
Contributor

@taroarai : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@rothja
Copy link
Copy Markdown
Collaborator

rothja commented Sep 21, 2021

@taroarai Taro, thanks for the suggestions! @MikeRayMSFT Mike, could you take a look at this while Mark is out of the office? Thank you! #reassign:mikeraymsft

@MikeRayMSFT MikeRayMSFT requested a review from pmasl October 12, 2021 17:36
@MikeRayMSFT
Copy link
Copy Markdown
Contributor

Requesting review or reviewer recommendation from @pmasl

@MikeRayMSFT MikeRayMSFT requested review from dplessMSFT and kfarlee and removed request for pmasl October 12, 2021 18:02
@markingmyname markingmyname requested review from pmasl and removed request for markingmyname November 9, 2021 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants