hey.
https://docs.microsoft.com/en-us/sql/tools/sqlservr-application?view=sql-server-2017
Is the -g option supported by the latest SQL Server?
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
(This Issue 2596 seems closely related to #2601
https://github.com/MicrosoftDocs/sql-docs/issues/2596
)
@MikeRayMSFT Should this be forwarded to engineering?
Running sqlservr.exe /? lists the -g startup option and allows its use, but nowhere is it mentioned in the startup messaging.
@yang-jiayi - I believe it doesn't apply to 64-bit applications, but I'm double checking. It appears there are several related places to update. I will confirm. Thanks for raising the issue.
@yang-jiayi - thank you for submitting this. We're submitting an update to remove this inoperable parameter from the options. We'll explain that it was supported through 2014.
@MikeRayMSFT
Thanks for help!
I use a translation service. I am sorry if my English is not correct.
I am the author of https://github.com/MicrosoftDocs/sql-docs/issues/2601
Thank you for correcting the document. Japanese documents do not seem to be fixed yet, but I believe that they will be fixed in the future.
The 2017 version of the following documents have descriptions based on -g (memory_to_reserve).
https://docs.microsoft.com/en-us/sql/relational-databases/memory-management-architecture-guide?view=sql-server-2017#changes-to-memory_to_reserve-starting-with-
It should be clear how these contents should be considered in SQL Server 2017.
Most helpful comment
@yang-jiayi - I believe it doesn't apply to 64-bit applications, but I'm double checking. It appears there are several related places to update. I will confirm. Thanks for raising the issue.