Description of os_thread_id to match PAL#2064
Merged
Jak-MS merged 2 commits intoMicrosoftDocs:livefrom May 13, 2019
Merged
Conversation
On linux, the os_thread_id (also the errorlog) not show the thread id nor process id assigned by Linux OS, and it is another internal number, generated due to SQLPAL. Bob dorr explain me in the comment in his blog post https://blogs.msdn.microsoft.com/bobsql/2018/07/18/sql-server-on-linux-why-do-i-have-two-sql-server-processes/
Contributor
|
@rrg92 : Thanks for your contribution! The author, @stevestein, has been notified to review your proposed change. |
Contributor
|
@stevestein : Thanks for your contribution! The author, @stevestein, has been notified to review your proposed change. |
|
@rrg92 - Thanks for updating the article! I made a couple minor edits but overall looks good. #sign-off |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
On linux, the os_thread_id (also, in the error log, when loggin message "Server process ID is") not show the thread id nor process id assigned by Linux OS, and it is another internal number, generated due to SQLPAL. Bob Dorr explain me in the comment in his blog post https://blogs.msdn.microsoft.com/bobsql/2018/07/18/sql-server-on-linux-why-do-i-have-two-sql-server-processes/
Additional considerations
If there are a way to match os_thread_id with linux thread, then I guess it is very important add to the documentation also. For advanced analysis, it can be useful to help troubleshooting and validating some theories!