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
Copy file name to clipboardExpand all lines: src/connections/storage/catalog/snowflake/index.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ To set up the Snowflake storage destination in Segment, you must have either a [
35
35
36
36
Segment's Snowflake destination requires you to first create a Snowflake [virtual warehouse](https://docs.snowflake.com/en/user-guide/warehouses){:target="_blank"}.
37
37
38
-
To avoid conflicts with other operations in your cluster, Segment recommends that you create a new warehouse just for Segment loads, but this is not mandatory. An X-Small warehouse works for most Segment customers when they first create their Snowflake destination.
38
+
To avoid conflicts with other operations in your cluster, Segment recommends that you create a new warehouse just for Segment loads. An X-Small warehouse is large enough for most Segment customers when they first create their Snowflake destination.
39
39
40
40
To create a new virtual warehouse, navigate to **Warehouses** > **Create** in Snowflake's Classic Console or execute the following SQL command:
> Set `AUTO_SUSPEND` to ~10 minutes in the UI (or 600 if using SQL) and enable `AUTO_RESUME` to avoid extra costs, as Snowflake uses [per-second billing](https://docs.snowflake.com/en/user-guide/warehouses-considerations#automating-warehouse-suspension){:target="_blank"}.
52
52
53
-
### Step 2: Create Database
53
+
### Step 2: Create a database
54
54
55
55
Segment recommends creating a new database just for Segment information, as the Segment Snowflake destination creates its own schemas and tables and could create name conflicts with your existing data.
56
56
@@ -60,14 +60,14 @@ To create a new database, execute the following SQL command:
60
60
CREATEDATABASE "SEGMENT_EVENTS";
61
61
```
62
62
63
-
### Step 3: Create role for Segment
63
+
### Step 3: Create a role for Segment
64
64
65
65
You need to run these SQL commands rather than creating a role with the "Create Role" dialog in the Classic Console UI.
66
66
67
67
This role gives Segment just enough permission to load data into your database. Segment recommends that you don't reuse this role for other operations.
68
68
1. Click on **Worksheets**
69
69
2. Select SEGMENT_EVENTS under database objects
70
-
3. Change role to `ACCOUNTADMIN`
70
+
3. Change the role to `ACCOUNTADMIN`
71
71
4. Create a new role by executing the following command:
72
72
```sql
73
73
CREATE ROLE "SEGMENT";
@@ -84,9 +84,9 @@ GRANT USAGE ON DATABASE "SEGMENT_EVENTS" TO ROLE "SEGMENT";
84
84
GRANT CREATE SCHEMA ON DATABASE "SEGMENT_EVENTS" TO ROLE "SEGMENT";
85
85
```
86
86
87
-
### Step 4: Create user for Segment
87
+
### Step 4: Create a user for Segment
88
88
89
-
You need to create the user that Segment uses to connect to your warehouse. Be sure to use a strong, unique password.
89
+
Create the user that Segment uses to connect to your warehouse. Be sure to use a strong, unique password.
90
90
91
91
```sql
92
92
CREATEUSER "SEGMENT_USER"
@@ -105,7 +105,7 @@ To install SnowSQL and verify your accounts:
3.Once the installation is complete, run the following command, replacing "account" and "user" with your Snowflake Account ID and username:
108
+
3.When the installation is complete, run the following command, replacing "account" and "user" with your Snowflake Account ID and username:
109
109
110
110
```
111
111
snowsql -a <account> -u <user>
@@ -168,8 +168,8 @@ After configuring your Snowflake resources, connect them to Segment.
168
168
1. In the Segment App, select Add Destination.
169
169
2. Search for and select "Snowflake".
170
170
3. Add your credentials as follows:
171
-
-**User**: The user name that you created in [Step 4: Create user for Segment](#step-4-create-user-for-segment)
172
-
-**Password**: The password that you set in [Step 4: Create user for Segment](#step-4-create-user-for-segment)
171
+
-**User**: The user name that you created in [Step 4: Create a user for Segment](#step-4-create-user-for-segment)
172
+
-**Password**: The password that you set in [Step 4: Create a user for Segment](#step-4-create-user-for-segment)
173
173
-**Account**: The account id of your cluster, not the url (for example, url: `my-business.snowflakecomputing.com`, account-id: `my-business`. **Note:** If you are using Snowflake on AWS, the account id includes the region. For example, your url might be: `my-business.us-east-1.snowflakecomputing.com/` and your account-id would be: `my-business.us-east-1`)
174
174
-**Database**: The database name that you created in [Step 2: Create database](#step-2-create-database)
175
175
-**Warehouse**: The name of the warehouse that you created in [Step 1: Create a virtual warehouse](#step-1-create-a-virtual-warehouse)
@@ -196,7 +196,7 @@ If you enable the `AUTO_SUSPEND` feature, Segment recommends that you also enabl
196
196
197
197
### Unique Warehouse, Database, and Role
198
198
199
-
Segment recommends creating a unique Warehouse, Database and Role for the Segment Snowflake connection to your Snowflake instance to avoid conflicts with other operations happening in your cluster.
199
+
Segment recommends creating a unique Warehouse, Database, and Role for the Segment Snowflake connection to your Snowflake instance to avoid conflicts with other operations happening in your cluster.
0 commit comments