When does Rudderstack load data into the data warehouse(s)?

RudderStack lets you choose how frequently it should sync the data into the data warehouse. The default time is 30 minutes. However, you can choose to extend this value up to 24 hours. You can also configure the time of the day when RudderStack loads the data.

Is there a way to force load my data into the warehouses?

Yes, there is - you can configure the below values in your config.yaml file:

warehouseSyncFreqIgnore = true #if set true this will ignore syncFrequency and syncStartingAt values which are configured in UI. By default this is false
uploadFreqInS=1800 #This field lets you control syncPeriod if above field set to true

Where can I view the status of my data load?

You can view the warehouse upload status in the Live Events section of the destination in the RudderStack dashboard.

Can I change the namespace (schema name) of my data warehouse in RudderStack?

Yes, you can. Although the default namespace will be the source name with some modifications to it, RudderStack also provides an option in the dashboard to explicitly set the namespace of the dataset in the warehouse.

Refer to the warehouse-specific destination settings to configure a namespace in the RudderStack dashboard.

How can I achieve identity resolution with multiple sources connected to one warehouse destination?

The default namespace will be the source name with some modifications. This will cause issues while creating mappings for identity resolution across different sources, leading to multiple RUDDER_ID created for the same user.

To avoid this, you can set the same namespace for each source.


This will ensure that the mappings are on the consistent namespace and only one RUDDER_ID is created for each user - irrespective of the number of sources connected to your warehouse destination.

How can I delete the staging files in my buckets?

RudderStack loads all the events configured with your warehouse into staging buckets. You can set a retention policy to delete these files from the staging bucket after a certain time. If you do not set any retention policy, the files will keep on accumulating.

Make sure that the retention policy duration is longer than the warehouse sync frequency duration so that RudderStack can re-run event uploads for a longer time, if required. It is recommended to set the retention policy duration to 30 days/1 month.

Which RudderStack IPs should I whitelist?

You will need to whitelist the following RudderStack IPs to enable network access:


The EU cluster IPs are listed below:


All the outbound traffic is routed through these RudderStack IPs.

How do I avoid lags in data syncs while heavy loads are running on my data warehouse?

You can use either of the following approaches to avoid data sync lags in your warehouse:

  • Approach 1: In the warehouse destination connection settings, set an exclusion window which lets you set a start and end time when Rudderstack will not sync data to your warehouse. You can run heavy loads during this time interval.
exclusion window
  • Approach 2: In the warehouse destination connection settings, your can increase the sync frequency interval so that there are lesser number of warehouse syncs throughout the day. You can also run the data syncs during the non-peak hours by setting the Sync Starting At time interval.
sync frequency
  • Approach 3: If you are performing only writes/updates on your data warehouse, you can set up a read replica of your database and connect it to your load generation tool. Connect the read/write replica to RudderStack, as shown:
read write database

How can I speed-up my warehouse uploads?

You can speed up your warehouse uploads by configuring the following parameters in the config.yaml file in your RudderStack setup:

ParameterDescriptionTipDefault value
RSERVER_WAREHOUSE_REDSHIFT_MAX_PARALLEL_LOADSDefines the number of concurrent tables that are synced to redshift in a given upload.Increase this as per your infra capability.3
RSERVER_WAREHOUSE_STAGING_FILES_BATCH_SIZEDefines the number of staging files that are batched and synced in a single upload.Increase this to batch more files together and reduce the number of uploads needed for a given volume of data.960
RSERVER_WAREHOUSE_NO_OF_WORKERSNumber of concurrent uploads to a warehouse. For example, 8 uploads to different schemas in Redshift can be done simultaneously.-8
RSERVER_WAREHOUSE_NO_OF_SLAVE_WORKER_ROUTINESNumber of go-routines creating load files in a warehouse slave process.Increase or decrease this as per memory allocated to the warehouse slave pod.4

How is the Namespace field populated for a Warehouse destination?

RudderStack sets the Namespace field depending on the following conditions:

  • If the Namespace and Database fields are present in your warehouse configuration:

    • For ClickHouse destination, the Database field is set as the namespace.
    • For all the other destinations, the Namespace field is populated as it is.
  • If RSERVER_WAREHOUSE_(DEST_TYPE)_CUSTOM_DATA_SET_PREFIX parameter is present, the Namespace is populated as (DEST_TYPE)_(CUSTOM_DATA_SET_PREFIX)_(SOURCE_NAME). For example:

Parameter value:
  • If none of the above fields are specified in the warehouse configuration settings, the source name is populated as the namespace for the first sync and picked up from the cache for all the subsequent syncs. In case the source name is changed, the namespace still remains the same as it is picked from cache.

To update the namespace as the new source name, you need to configure a new source.

How does Rudderstack configure table names?

RudderStack sets the table names by picking up the event names and modifying them to follow the snake case convention (for example, source name -> source_name).

For the following sample snippet, RudderStack sets the table name as product_purchased.

"userId": "user123",
"event": "Product Purchased",
"properties": {
"name": "Rubik's Cube",
"revenue": 4.99
"context": {
"ip": ""
"timestamp": "2020-02-02T00:23:09.544Z"

The table name truncation logic is as follows:

  • For PostgreSQL, the table name is truncated after 63 characters.
  • For Data Lake destinations (S3 Data Lake, GCS Data Lake, Azure Data Lake), there is no set limit.
  • For other destinations, the table name is truncated after 127 characters.

How does Rudderstack configure the column names? / How does RudderStack normalize arrays and complex event properties in the warehouse schema?

RudderStack flattens the event properties and converts them into snake case (for example, source name -> source_name). Further, each of these event properties acts as a warehouse column.

  1. The below example shows how the standard properties are normalized:
product: {
name: "iPhone",
version: 11

Normalized properties (Column names)

product_name : "iPhone"
product_version : 11
  1. The below example shows how the array properties are normalized:
products: [
name: "iPhone",
version: 11
name: "Android",
version: 16

Normalized property (Column name)

products: "[{ \"name\": \"iPhone\", \"version\": 11 }, { \"name\": \"Android\", \"version\": 16 }]"
  1. The below example shows how the complex properties are normalized:
products: {
iPhone: {
version: 11
Android: {
version: 16

Normalized properties (Column names)

products_i_phone_version : 11
products_android_version : 16

While configuring the Snowflake destination, what should I enter in the Account field?

While configuring Snowflake as a destination in RudderStack, you need to enter your Snowflake connection credentials which includes the Account field, as shown below:

Snowflake account ID example

The Account field corresponds to your Snowflake account ID and is a part of the Snowflake URL.

The following examples illustrate the slight differences in the Snowflake account ID for various cloud providers:

Account ID exampleCorresponding Snowflake URLSnowflake cloud provider


rx18795.east-us-2.azurehttps://rx18795.east-us-2.azure.snowflakecomputing.comMicrosoft Azure
ah76025.us-central1.gcphttps://ah76025.us-central1.gcp.snowflakecomputing.comGoogle Cloud Platform

In case of AWS, .aws is present in the account locator of some region accounts and hence must be included in the Account field above.

For more information on the different account locator formats depending on your region or cloud provider, refer to the Snowflake documentation.

Contact us

For any other queries on the RudderStack warehouse integrations, you can contact us or start a conversation in our Slack community.