Skip to content

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

Merged
merged 5 commits into from
Mar 13, 2024
Merged

Conversation

stayseesong
Copy link
Contributor

@stayseesong stayseesong commented Mar 6, 2024

Proposed changes

Merge timing

March 13, 2024

Related issues (optional)

@stayseesong stayseesong added the new-integration Added a new source or destination label Mar 6, 2024
@stayseesong stayseesong requested a review from a team as a code owner March 6, 2024 23:32
@stayseesong stayseesong requested review from cmastr and removed request for a team March 6, 2024 23:32
Copy link

netlify bot commented Mar 6, 2024

Deploy Preview for segment-docs ready!

Name Link
🔨 Latest commit 0ffc804
🔍 Latest deploy log https://app.netlify.com/sites/segment-docs/deploys/65f09b200d64030008f20fe1
😎 Deploy Preview https://deploy-preview-6199--segment-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Comment on lines +54 to +57
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.
Copy link
Contributor

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.

Copy link
Contributor Author

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

Copy link
Contributor

@cmastr cmastr Mar 7, 2024

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.

@stayseesong stayseesong changed the title Azure RETL Public Beta Azure RETL Public Beta and RETL Partial Syncs [DOC-782] Mar 12, 2024
@stayseesong stayseesong requested a review from kly-segment March 12, 2024 01:04
@stayseesong stayseesong changed the base branch from develop to master March 13, 2024 15:49
@stayseesong stayseesong merged commit 5475c8b into master Mar 13, 2024
@stayseesong stayseesong deleted the DOC-782 branch March 13, 2024 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-feature new-integration Added a new source or destination
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants