Update sql-agent-extension-automatic-registration-all-vms.md#7717
Merged
Court72 merged 1 commit intoMicrosoftDocs:livefrom Jun 28, 2022
Merged
Update sql-agent-extension-automatic-registration-all-vms.md#7717Court72 merged 1 commit intoMicrosoftDocs:livefrom
Court72 merged 1 commit intoMicrosoftDocs:livefrom
Conversation
Discussing with Abdullah Mamun on this subject - the job doesn't run daily. It runs monthly. With that in mind, the documentation should reflect this, and the line below: Automatic registration can take up to 4 days to detect newly created SQL Server VMs. I doubt we can say that it will only take 4 days to pick up a VM with SQL Server installed. The process could take up to 30 depending on when SQL is installed, and when the job runs. Currently working a case now where this is the focus of the customer's issue, and again - if the job doesn't run daily, we can't have this out in the ether.
Contributor
|
@jasonplante1 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #label:"aq-pr-triaged" |
Contributor
|
We run an Automated job daily to find VM candidates where SQL Server is present, if we don't see SQL Server we will come back and revisit this VM in a month/30 days. Hence daily in this context stands correct. |
Contributor
Author
Contributor
Author
|
Thank you @***@***.***>.
@***@***.***> mentioned at [?docx icon] AutoRegFAQ.docx<https://microsoft.sharepoint.com/:w:/t/SqlIaaSteam/ETTwqMDsuFNKmhPhOzuoyfQBS1spnrTIEcaHFaL6AzLWqQ?e=TtHBzm>
Question: How often are the registration attempts for a single VM?
A VM is added to the registration queue when it is discovered by any of the registration sources, which are aggregated daily. For newly created VMs, it may take at least 1 day to be discovered by our registration sources. If the registration fails, the VMs are retried depending on the type of error:
* For non-retriable errors, like SQL Server instance is not present on VM or any extension installation related error, the VM registration is re-tried after 30 days.
* For retriable errors, like VM is powered off, the VM is added back to the registration queue after 6 hours.
@***@***.***>/ @***@***.***>
Is there a way we can clarify this in our external document? Looks like we are routinely getting questions on this
https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/sql-agent-extension-automatic-registration-all-vms?view=azuresql&tabs=azure-cli#overview
When automatic registration is enabled, a job runs daily to detect whether or not SQL Server is installed on all the unregistered VMs in the subscription. This is done by copying the SQL IaaS agent extension binaries to the VM, then running a one-time utility that checks for the SQL Server registry hive. If the SQL Server hive is detected, the virtual machine is registered with the extension in lightweight mode. If no SQL Server hive exists in the registry, the binaries are removed. Automatic registration can take up to 4 days to detect newly created SQL Server VMs.
From: Jason Plante ***@***.***>
Sent: Wednesday, June 22, 2022 4:57 PM
To: MicrosoftDocs/sql-docs ***@***.***>; MicrosoftDocs/sql-docs ***@***.***>
Cc: Mention ***@***.***>; Abdullah Mamun ***@***.***>
Subject: RE: [MicrosoftDocs/sql-docs] Update sql-agent-extension-automatic-registration-all-vms.md (PR #7717)
Thanks for that clarification - appreciate the explanation. Adding @abdullah ***@***.***> for visibility/context.
From: adbadram ***@***.******@***.***>>
Sent: Wednesday, June 22, 2022 3:43 PM
To: MicrosoftDocs/sql-docs ***@***.******@***.***>>
Cc: Jason Plante ***@***.******@***.***>>; Mention ***@***.******@***.***>>
Subject: Re: [MicrosoftDocs/sql-docs] Update sql-agent-extension-automatic-registration-all-vms.md (PR #7717)
We run an Automated job daily to find VM candidates where SQL Server is present, if we don't see SQL Server we will come back and revisit this VM in a month/30 days. Hence daily in this context stands correct.
-
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fpull%2F7717%23issuecomment-1163531740&data=05%7C01%7Camamun%40microsoft.com%7C57a766b0d8704483367a08da5491b0a9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637915281965113849%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2FMwQOPF3g9F01FXzG6PfnMJHjuhBeZTUHqhtNe1dOw%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAR2E42BKIX23RTINHW236TTVQNUFVANCNFSM5ZQJCXMQ&data=05%7C01%7Camamun%40microsoft.com%7C57a766b0d8704483367a08da5491b0a9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637915281965113849%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gv7HKA%2B1c%2FDzujudv8GZa%2B2oCNS1SLfNXwE9qwZPHNQ%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Contributor
|
#sign-off |
Contributor
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @adbadram |
Contributor
|
@ktoliver fyi #sign-off |
Contributor
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @adbadram |
|
Docs Build status updates of commit e14d9c5: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
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
9 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.
Discussing with Abdullah Mamun on this subject - the job doesn't run daily. It runs monthly.
With that in mind, the documentation should reflect this, and the line below:
Automatic registration can take up to 4 days to detect newly created SQL Server VMs.
I doubt we can say that it will only take 4 days to pick up a VM with SQL Server installed. The process could take up to 30 depending on when SQL is installed, and when the job runs.
Currently working a case now where this is the focus of the customer's issue, and again - if the job doesn't run daily, we can't have this out in the ether.