[Azure Synapse Destination] provide clarification on dedicated sql pool #1964
Conversation
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
…l pool is necessary to connect
markzegarelli
approved these changes
Oct 6, 2021
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
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.
Proposed changes
In the "Getting Started" steps, I changed number 2 to better reflect that you will need to setup a "dedicated sql pool" in order to connect with Segment properly. For Azure Synapse, there are currently two options in setting this up: serverless sql pool, and dedicated sql pool.
Currently, the only way to know that a dedicated sql pool is necessary to connect with Segment, is if you click into the linked documentation on step 2. I had a customer, who did not do this because he had already provisioned his Synapse Analytics setup with the "serverless sql pool" option. Which resulted in a lot of back in forth before stumbling upon the solution.
Feel free to do with this request as you will, I just thought it might be worth running it you all to see if this would be worth changing. Thanks!
Merge timing
No rush.
Related issues (optional)
N/A