[source-mssql] improving discovery of large mssql database #46515
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
theyueli
added
the
team/db-dw-sources
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
area/connectors
|
/bump-version type=patch changelog="Improving discovery of large SQL server database."
|
octavia-squidington-iii
added
the
area/documentation
postamar
approved these changes
Oct 7, 2024
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.
What
Partially fixes #42491
This is a cherry-pick of the change from this community PR
#43421
The purpose of this PR is to get this merged sooner due to an internal priority change. (There is a lack of response in the original PR)
How
From the original PR:
"If the connector is configured to synchronize only particular schemas the schema discovery step will download only columns of tables of each schema rather than downloading all columns for the whole database and then filtering down to necessary schemas."
Review guide
User Impact
Can this PR be safely reverted and rolled back?