You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The previous instructions were unclear and didn't provide detailed instructions on which tabs to select to get to the options that needed modification.
Please confirm my understanding of the impact of making these changes. It appears as if I disable a source, I lose all data from that source until I re-enable it, is that correct?
Copy file name to clipboardExpand all lines: src/connections/storage/warehouses/faq.md
+20-10Lines changed: 20 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,8 +64,7 @@ You can allowlist Segment's custom IP `52.25.130.38/32` while authorizing Segmen
64
64
65
65
If you're in the EU region, use CIDR `3.251.148.96/29`.
66
66
67
-
> info ""
68
-
> EU workspace regions are currently in beta. If you would like to learn more about the beta, please contact your account manager.
67
+
> **Note**: EU workspace regions are currently in beta. If you would like to learn more about the beta, please contact your account manager.
69
68
70
69
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)
71
70
@@ -108,8 +107,7 @@ and the relationships that exist between elements. Segment's schemas use the fol
108
107
`segment_engineering.tracks.user_id`, where Source refers to the source or project name (segment_engineering), collection refers to the event (tracks),
109
108
and the property refers to the data being collected (user_id).
110
109
111
-
> note " "
112
-
> All schema data is always represented in snake case.
110
+
> **Note**: All schema data is always represented in snake case.
113
111
114
112
For more information about Warehouse Schemas, see the [Warehouse Schemas](/docs/connections/storage/warehouses/schema) page.
115
113
@@ -125,10 +123,22 @@ Segment stores the name of your schema in the **SQL Settings** page. Changing th
125
123
126
124
To change the name of your schema without disruptions:
127
125
128
-
1. Open the Segment app, select your warehouse from the Sources tab, and select **Settings.**
129
-
2. Under the "Enable Source" section, disable your warehouse and click **Save Changes.**
130
-
3. Select the "SQL Settings" tab.
126
+
1. Open the Segment app
127
+
1. Select the "Connections" tab on the left
128
+
1. Select the "Sources" tab
129
+
1. Select the source from the list of "My Sources" that is sending data to the schema you want to change
130
+
1. Select the "Settings" tab from the top (just below your source name)
131
+
1. On the source's settings page, select "Basic."
132
+
2. Under the "Enable Source" section, disable your source and click **Save Changes.**
133
+
> **Note**: This will pause all data from the selected source to all destinations.
134
+
8. Select the "SQL Settings" tab.
131
135
4. Update the "Schema Name" field with the new name for your schema and click **Save Changes.**
132
-
5. Rename the schema in your Data Warehouse to match the new name in the Segment app.
133
-
6. Open the Segment app, select your warehouse from the Sources tab, and select **Settings.** On the source's settings page, select "Basic."
134
-
7. Under the "Enable Source" section, enable your warehouse and click **Save Changes.**
136
+
> **Note**: This will set the schema name for all existing and future SQL destinations. It is important that you understand how many warehouse destination(s) exist for this source, and that you understand how to rename the schema in each database.
137
+
10. Rename the schema(s) in your warehouse destination(s) to match the newly modified schema name from the previous step.
138
+
1. Open the Segment app
139
+
1. Select the "Connections" tab on the left
140
+
1. Select the "Sources" tab
141
+
1. Select the source from the list of My Sources that is sending data to the schema that was changed
142
+
1. Select the "Settings" tab from the top (just below your source name)
143
+
1. On the source's settings page, select "Basic."
144
+
7. Under the "Enable Source" section, enable your warehouse and click **Save Changes.**
0 commit comments