Merge pull request #268 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/_data/sidenav/main.yml

@@ -219,6 +219,8 @@ sections:
         title: Redshift Cluster and Redshift Connector Limitations
       - path: /connections/storage/warehouses/redshift-tuning
         title: Speeding Up Redshift Queries
+      - path: /connections/storage/warehouses/redshift-useful-sql
+        title: Useful SQL Queries for Redshift
   - path: /connections/test-connections
     title: Testing Connections
   - path: /connections/data-export-options

src/_includes/content/how-a-sync-works.md

@@ -0,0 +1,3 @@
+When Segment loads data into your warehouse, each sync goes through two steps:
+1. **Ping:** Segment servers connect to your warehouse. For Redshift warehouses, Segment also runs a query to determine how many slices a cluster has. Common reasons a sync might fail at this step include a blocked VPN or IP, a warehouse that isn't set to be publicly accessible, or an issue with user permissions or credentials. 
+2. **Load:** Segment de-duplicates the transformed data and loads it into your warehouse. If you have queries set up in your warehouse, they run after the data is loaded into your warehouse. 

src/connections/storage/warehouses/faq.md

@@ -44,11 +44,9 @@ Your warehouse id appears in the URL when you look at the [warehouse destination
 
 ## How fresh is the data in Segment Warehouses?
 
-Data is available in Warehouses within 24-48 hours. The underlying Redshift datastore has a subtle tradeoff between data freshness, robustness, and query speed. For the best experience, Segment needs to balance all three of these.
+Data is available in Warehouses within 24-48 hours, depending on your tier's sync frequency. For more information about sync frequency by tier, see [Sync Frequency](/docs/connections/storage/warehouses/warehouse-syncs/#sync-frequency).
 
-Real-time loading of the data into Segment Warehouses would cause significant performance degradation at query time because of the way Redshift uses large batches to optimize and compress columns. To optimize for your query speed, reliability, and robustness, Segment guarantees that your data will be available in Redshift within 24 hours.
-
-As Segment improves and updates the ETL processes and optimizes for SQL query performance downstream, the actual load time will vary, but Segment ensures it's always within 24 hours.
+Real-time loading of the data into Segment Warehouses would cause significant performance degradation at query time. To optimize for your query speed, reliability, and robustness, Segment guarantees that your data will be available in your warehouse within 24 hours. The underlying datastore has a subtle tradeoff between data freshness, robustness, and query speed. For the best experience, Segment needs to balance all three of these.
 
 ## What if I want to add custom data to my warehouse?
 
@@ -58,23 +56,23 @@ The only restriction when loading your own data into your connected warehouse is
 
 If you want to insert custom data into your warehouse, create new schemas that are not associated with an existing source, since these may be deleted upon a reload of the Segment data in the cluster.
 
-We highly recommend scripting any sort of additions of data you might have to warehouse, so that you aren't doing one-off tasks that can be hard to recover from in the future in the case of hardware failure.
+Segment recommends scripting any sort of additions of data you might have to warehouse, so that you aren't doing one-off tasks that can be hard to recover from in the future in the case of hardware failure.
 
-## Which IPs should I whitelist?
+## Which IPs should I allowlist?
 
-You can whitelist Segment's custom IP `52.25.130.38/32` while authorizing Segment to write in to your Redshift or Postgres port.
+You can allowlist Segment's custom IP `52.25.130.38/32` while authorizing Segment to write in to your Redshift or Postgres port.
 
 If you're in the EU region, use CIDR `3.251.148.96/29`.
 
 > info ""
 > EU workspace regions are currently in beta. If you would like to learn more about the beta, please contact your account manager.
 
-BigQuery does not require whitelisting an IP address. To learn how to set up BigQuery, check out our [set up guide](https://segment.com/docs/connections/storage/catalog/bigquery/#getting-started)
+BigQuery does not require allowlisting an IP address. To learn how to set up BigQuery, check out Segment's BigQuery [set up guide](/docs/connections/storage/catalog/bigquery/#getting-started)
 
 
 ## Will Segment sync my historical data?
 
-We will automatically load up to 2 months of your historical data when you connect a warehouse.
+Segment loads up to two months of your historical data when you connect a warehouse.
 
 For full historical backfills you'll need to be a Segment Business plan customer. If you'd like to learn more about our Business plan and all the features that come with it, [check out our pricing page](https://segment.com/pricing).
 
@@ -92,3 +90,45 @@ When you create a new source, the source syncs to all warehouse(s) in the worksp
 - **Config API**: Send a [PATCH Connected Warehouse request](https://reference.segmentapis.com/?version=latest#ec12dae0-1a3e-4bd0-bf1c-840f43537ee2) to update the settings for the warehouse(s) you want to prevent from syncing.
 
 After a source is created, you can enable or disable a warehouse sync within the Warehouse Settings page.
+
+## Can I be notified when warehouse syncs fail?
+
+If you enabled activity notifications for your storage destination, you'll receive notifications in the Segment app for the fifth and 20th consecutive warehouse failures.
+
+To sign up for warehouse sync notifications:
+1. Open the Segment app. 
+2. Go to **Settings** > **User Preferences**. 
+3. In the Activity Notifications section, select **Storage Destinations**.
+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.) 
+and the relationships that exist between elements. Segment's schemas use the following template: <br/>`<source>.<collection>.<property>`, for example, 
+`segment_engineering.tracks.user_id`, where Source refers to the source or project name (segment_engineering), collection refers to the event (tracks),
+ and the property refers to the data being collected (user_id). 
+
+> note " "
+> All schema data is always represented in snake case.
+
+For more information about Warehouse Schemas, see the [Warehouse Schemas](/docs/connections/storage/warehouses/schema) page.
+
+## If my syncs fail and get fixed, do I need to ask for a backfill?
+
+If your syncs fail, you do not need to reach out to Segment Support to request a backfill. Once a successful sync takes place, 
+Segment automatically loads all of the data generated since the last successful sync occurred. 
+
+
+## Can I change my schema names once they've been created?
+
+Segment stores the name of your schema in the **SQL Settings** page. Changing the name of your schema in the app without updating the name in your data warehouse causes a new schema to form, one that doesn't contain historical data.  
+
+To change the name of your schema without disruptions: 
+
+1. Open the Segment app, select your warehouse from the Sources tab, and select **Settings.**
+2. Under the "Enable Source" section, disable your warehouse and click **Save Changes.**   
+3. Select the "SQL Settings" tab. 
+4. Update the "Schema Name" field with the new name for your schema and click **Save Changes.**
+5. Rename the schema in your Data Warehouse to match the new name in the Segment app. 
+6. Open the Segment app, select your warehouse from the Sources tab, and select **Settings.** On the source's settings page, select "Basic."
+7. Under the "Enable Source" section, enable your warehouse and click **Save Changes.**

src/connections/storage/warehouses/images/sql-redshift-table-1.jpg

@@ -20,6 +20,8 @@ Relational databases are great when you know and predefine the information colle
 
 Examples of data warehouses include Amazon Redshift, Google BigQuery, and Postgres.
 
+{% include content/how-a-sync-works.md %}
+
 <div data-headings-anchors id="warehouse-schemas"></div>
 > info "Looking for the Warehouse Schemas docs?"
 >  They've moved! Check them out [here](schema/).
@@ -32,7 +34,7 @@ Examples of data warehouses include Amazon Redshift, Google BigQuery, and Postgr
 
 [How do I give users permissions to my warehouse?](/docs/connections/storage/warehouses/add-warehouse-users/)
 
-Check out our [Frequently Asked Questions about Warehouses](/docs/connections/storage/warehouses/faq/) and [a list of helpful queries to get you started](https://help.segment.com/hc/en-us/articles/205577035-Common-Segment-SQL-Queries).
+Check out the [Frequently Asked Questions about Warehouses](/docs/connections/storage/warehouses/faq/) page and [a list of helpful SQL queries to get you started with Redshift ](/docs/connections/storage/warehouses/redshift-useful-sql).
 
 ## FAQs
 
@@ -42,36 +44,36 @@ Check out our [Frequently Asked Questions about Warehouses](/docs/connections/st
 
 [How do I give users permissions?](/docs/connections/storage/warehouses/add-warehouse-users/)
 
-[What are the limitations of Redshift clusters and our warehouses connector?](/docs/connections/storage/warehouses/redshift-faq/)
+[What are the limitations of Redshift clusters and warehouses connectors?](/docs/connections/storage/warehouses/redshift-faq/)
 
 [Where do I find my source slug?](/docs/connections/storage/warehouses/faq/#how-do-i-find-my-source-slug)
 
 ### Setting up a warehouse
 
 [How do I create a user, grant usage on a schema and then grant the privileges that the user will need to interact with that schema?](/docs/connections/storage/warehouses/add-warehouse-users/)
 
-[Which IPs should I whitelist?](/docs/connections/storage/warehouses/faq/#which-ips-should-i-whitelist)
+[Which IPs should I allowlist?](/docs/connections/storage/warehouses/faq/#which-ips-should-i-whitelist)
 
 [Will Segment sync my historical data?](/docs/connections/storage/warehouses/faq/#will-segment-sync-my-historical-data)
 
 [Can I load in my own data into my warehouse?](/docs/connections/storage/warehouses/faq/#what-if-i-want-to-add-custom-data-to-my-warehouse)
 
-[Can I control what data is sent to my warehouse?](/docs/connections/storage/warehouses/faq/)
+[Can I control what data is sent to my warehouse?](/docs/connections/storage/warehouses/faq/#can-i-control-what-data-is-sent-to-my-warehouse)
 
 ### Managing a warehouse
 
-[How fresh is the data in my warehouse?](/docs/connections/storage/warehouses/faq/)
+[How fresh is the data in my warehouse?](/docs/connections/storage/warehouses/faq/#how-fresh-is-the-data-in-segment-warehouses)
 
-[Can I add, tweak, or delete some of the tables?](/docs/connections/storage/warehouses/faq/)
+[Can I add, tweak, or delete some of the tables?](/docs/connections/storage/warehouses/faq/#can-we-add-tweak-or-delete-some-of-the-tables)
 
-[Can I transform or clean up old data to new formats or specs?](/docs/connections/storage/warehouses/faq/)
+[Can I transform or clean up old data to new formats or specs?](/docs/connections/storage/warehouses/faq/#can-we-transform-or-clean-up-old-data-to-new-formats-or-specs)
 
 [What are common errors and how do I debug them?](/docs/connections/storage/warehouses/warehouse-errors/)
 
-[How do I speed up my queries?](/docs/connections/storage/warehouses/redshift-tuning/)
+[How do I speed up my Redshift queries?](/docs/connections/storage/warehouses/redshift-tuning/)
 
 ### Analyzing with SQL
 
 [How do I forecast LTV with SQL and Excel for e-commerce businesses?](/docs/guides/how-to-guides/forecast-with-sql/)
 
-[How do I measure the ROI of my Marketing Campaigns?](/docs/guides/how-to-guides/measure-marketing-roi/)
+[How do I measure the ROI of my Marketing Campaigns?](/docs/guides/how-to-guides/measure-marketing-roi/)