-
Notifications
You must be signed in to change notification settings - Fork 367
Azure RETL Public Beta and RETL Partial Syncs [DOC-782] #6199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
src/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup.md
Outdated
Show resolved
Hide resolved
src/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup.md
Outdated
Show resolved
Hide resolved
To set up Azure as your Reverse ETL source: | ||
1. Log in to your Azure account. | ||
2. Navigate to your **dedicated SQL pool**. Segment supports both dedicated SQL pool (formerly SQL DW) and dedicated SQL pool in Synapse workspace. | ||
3. Navigate to **Settings > Connection strings** and select the **JDBC** tab to find the server, port, and database name. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why wouldn't we just point them to the Azure guide on this info? If it changes in their product, we won't know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's best to do it this way as it allows users to just follow one set of instructions instead of jumping around reading one set of docs and then coming back to this. There's also no clear Azure guide in guiding them to get the information that they need for this. This is also how we've done the other RETL source setup docs, and it makes it much easier for users in terms of setup
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's also no clear Azure guide in guiding them to get the information that they need for this.
Ok, if there’s no instructions in the Azure guide on this, then I agree it’s best to document it ourselves. There’s still a risk it could become incorrect if Azure changes their product and that we should have ways to find those types of changes when we document others' products.
src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Casie Oxford <[email protected]>
Proposed changes
Merge timing
March 13, 2024
Related issues (optional)