Update known-issues-and-errors-change-data-capture.md #9939
+6
−0
Conversation
This file contains 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
|
@valecanto : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 8159ad3: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
MashaMSFT
reviewed
Nov 20, 2024
docs/relational-databases/track-changes/known-issues-and-errors-change-data-capture.md
Outdated
Show resolved
Hide resolved
…s-change-data-capture.md Co-authored-by: Masha Thomas (MSFT) <32783170+MashaMSFT@users.noreply.github.com>
|
Learn Build status updates of commit 7f6ee42:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/relational-databases/track-changes/known-issues-and-errors-change-data-capture.md | Details |
docs/relational-databases/track-changes/known-issues-and-errors-change-data-capture.md
- Line 162, Column 75: [Warning: disallowed-html-tag - See documentation]
HTML tag 'database' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
MashaMSFT
reviewed
Nov 20, 2024
| @@ -159,6 +159,12 @@ These are the different troubleshooting categories included in this section: | |||
|
|
|||
| * **Recommendation**: Ensure the `cdc` user has the `db_owner` role assigned. To create the `cdc` user, see the example [Create cdc user and assign role](#create-user-and-assign-role). | |||
|
|
|||
| #### Error 22830 - Could not update the metadata that indicates database <database name> is enabled for Change Data Capture. The failure occurred when executing the command 'sp_cdc_create_functions'. | |||
There was a problem hiding this comment.
Suggested change
| #### Error 22830 - Could not update the metadata that indicates database <database name> is enabled for Change Data Capture. The failure occurred when executing the command 'sp_cdc_create_functions'. | |
| #### Error 22830 - Could not update the metadata that indicates database `<database name>` is enabled for Change Data Capture. The failure occurred when executing the command 'sp_cdc_create_functions'. |
MashaMSFT
reviewed
Nov 20, 2024
| @@ -159,6 +159,12 @@ These are the different troubleshooting categories included in this section: | |||
|
|
|||
| * **Recommendation**: Ensure the `cdc` user has the `db_owner` role assigned. To create the `cdc` user, see the example [Create cdc user and assign role](#create-user-and-assign-role). | |||
|
|
|||
| #### Error 22830 - Could not update the metadata that indicates database <database name> is enabled for Change Data Capture. The failure occurred when executing the command 'sp_cdc_create_functions'. | |||
|
|
|||
| * **Cause**: presence of a trigger that is inserting data in master database on objects creation. Enabling cdc is done by a temporary cdc user, so sp_cdc_create_functions will be executed under this cdc user, the trigger will go off and try to insert data in master database (under the same cdc user) and then this error appears because cdc user does not have required permissions on master database. | |||
There was a problem hiding this comment.
Suggested change
| * **Cause**: presence of a trigger that is inserting data in master database on objects creation. Enabling cdc is done by a temporary cdc user, so sp_cdc_create_functions will be executed under this cdc user, the trigger will go off and try to insert data in master database (under the same cdc user) and then this error appears because cdc user does not have required permissions on master database. | |
| * **Cause**: This error occurs when a 'CREATE OBJECT' trigger exists in the database and a user that does not have permission to write data to the `master` database tries to enable change data capture (CDC). The `sp_cdc_create_functions` stored procedure is automatically executed by the user when trying to enable CDC, which fires the trigger. Since the user doesn't have permission to write to the `master` database, the trigger fails, which causes the CDC stored procedure to fail with error 22830. |
MashaMSFT
reviewed
Nov 20, 2024
| #### Error 22830 - Could not update the metadata that indicates database <database name> is enabled for Change Data Capture. The failure occurred when executing the command 'sp_cdc_create_functions'. | ||
|
|
||
| * **Cause**: presence of a trigger that is inserting data in master database on objects creation. Enabling cdc is done by a temporary cdc user, so sp_cdc_create_functions will be executed under this cdc user, the trigger will go off and try to insert data in master database (under the same cdc user) and then this error appears because cdc user does not have required permissions on master database. | ||
| * **Recommendation**: Before enabling cdc on a database, disable the trigger. Enable the trigger again, once cdc is configured. |
There was a problem hiding this comment.
Suggested change
| * **Recommendation**: Before enabling cdc on a database, disable the trigger. Enable the trigger again, once cdc is configured. | |
| * **Recommendation**: To resolve this error, if you don't have write permission to the `master` database, disable the CREATE trigger before you try to enable CDC on a database. Reenable the trigger after CDC is successfully enabled. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@MashaMSFT as previously discussed, I added an error in modifying metadata when a trigger is enabled on the db