warehouse faqs docs edits #7888
Open
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
stayseesong
added
the
content-update
| @@ -125,41 +125,41 @@ Users with workspaces in the EU must allowlist `3.251.148.96/29`. | |||
|
|
|||
| ## Will Segment sync my historical data? | |||
|
|
|||
| Segment loads up to two months of your historical data when you connect a warehouse. | |||
| Segment loads up to 2 months of your historical data when you connect a warehouse. | |||
There was a problem hiding this comment.
nit: if we're using Twilio's style guide this would remain as-is
|
|
||
| Amazon's service has some more powerful features and will be more cost-effective for most cases. However, first time users of Amazon Web Services (AWS) will likely need to spend some time with the documentation to get set up properly. | ||
|
|
||
| ## How do I prevent a source from syncing to some or all warehouses? | ||
|
|
||
| When you create a new source, the source syncs to all warehouse(s) in the workspace by default. You can prevent the source from syncing to some or all warehouses in the workspace in two ways: | ||
| When you create a new source, the source syncs to all warehouses in the workspace by default. You can prevent the source from syncing to some or all warehouses in the workspace in 2 ways: |
| 4. Enable **Storage Destination Sync Failed**. | ||
|
|
||
| ## How is the data formatted in my warehouse? | ||
|
|
||
| Data in your warehouse is formatted into **schemas**, which involve a detailed description of database elements (tables, views, indexes, synonyms, etc.) | ||
| Data in your warehouse is formatted into **schemas**, which involve a detailed description of database elements (such as tables, views, indexes, synonyms) |
There was a problem hiding this comment.
Suggested change
| Data in your warehouse is formatted into **schemas**, which involve a detailed description of database elements (such as tables, views, indexes, synonyms) | |
| Data in your warehouse is formatted into **schemas**, which involve a detailed description of database elements (like tables, views, indexes, synonyms) |
| 8. Repeat steps six and seven until you rename all sources that sync data to your warehouse. | ||
| 7. Select **SQL Settings** and update the **Schema Name** field with the new name for your schema and click **Save Changes**. | ||
| > **Note**: This sets the schema name for all existing and future destinations. The new name must be lowercase and may include underscores. | ||
| 8. Repeat steps 6 and 7 until you rename all sources that sync data to your warehouse. |
There was a problem hiding this comment.
same as comment on line 128
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
edits for the Segment docs audit on the warehouse FAQs page
Merge timing
Related issues (optional)