To answer your question about the options for Raw Table Schema Name in the SQL Server connector, I'll refer to the relevant documentation. According to the [MS SQL Server Migration Guide](https://docs.airbyte.com/integrations/destinations/mssql-migrations#ms-sql-server-migration-guide), you have the following option for the Raw Table Schema Name: 1. You can change the "raw" schema from the default

airbyte_internal

by supplying a value for

Raw Table Schema Name

. The guide provides an example: - If you set the Schema to "default" and the Stream Name to "my_stream", it will write to

airbyte_internal.default_raw__stream_my_stream

- However, if you set the Schema to "default", the Stream Name to "my_stream", and the Raw Table Schema Name to "raw_data", it will write to

raw_data.default_raw__stream_my_stream

This allows you to customize where your raw data tables are stored within your SQL Server database. It's important to note that the Raw Table Schema Name is an optional field. If you don't provide a value, it will use the default

airbyte_internal

schema for raw tables. Remember that changing this setting will affect where your raw data is stored, so make sure to update any processes or queries that might be relying on the default schema location.

To achieve your goal of having tables from different sources in their respective schemas (e.g., Mixpanel data in a "mixpanel" schema), you can use the Custom namespace option in Airbyte. This allows you to set up a schema name based on the source for each connection. Here's how you can do this: 1. When setting up or editing your connection in Airbyte, go to the "Namespace" configuration. 2. Select the "Custom format" option for the namespace. 3. In the custom format field, you can enter the name of your source (e.g., "mixpanel") or use a dynamic parameter. [Namespaces documentation](https://docs.airbyte.com/using-airbyte/core-concepts/namespaces#what-is-a-namespace) provides an example of how this works: "You can enter plain text (most common) or additionally add a dynamic parameter

${SOURCE_NAMESPACE}

, which uses the namespace provided by the source if available." For your specific case with Mixpanel, you would simply enter "mixpanel" as the custom namespace. This approach allows you to have different schemas for different sources. So, your Mixpanel data would indeed end up in tables like

mixpanel.table_name

. Keep in mind that this configuration is done at the connection level, so you'll need to set it up for each source connection individually. This gives you the flexibility to organize your data from various sources into their respective schemas. Remember to update any downstream processes or queries to reflect these new schema names after making this change.

To answer your question about what to put in the Destination itself, I'll refer to the relevant documentation for configuring the destination namespace. According to the [Namespaces documentation](https://docs.airbyte.com/using-airbyte/core-concepts/namespaces), when setting up your destination, you have three main options for configuring the namespace: 1. Custom 2. Destination-defined 3. Source-defined For your specific case, where you want different schemas based on the source (e.g., "mixpanel" for Mixpanel data), you should choose the "Custom" option in the destination configuration. Here's what you should do: 1. In the Airbyte UI, go to the destination configuration. 2. Look for the "Namespace" or "Default Schema" setting (the exact name might vary depending on the destination type). 3. Select the "Custom" option. 4. In the custom format field, you can use a placeholder that will be replaced with the actual value you set in each connection. A common placeholder is

${SOURCE_NAMESPACE}

. By setting it up this way in the destination, you're allowing each connection to define its own schema name. Then, in each individual connection configuration (as we discussed in the previous answer), you'll set the actual schema name (like "mixpanel") that you want to use for that specific source. This approach gives you the flexibility to have different schemas for different sources while setting it up once in the destination configuration. Remember to save your changes in the destination configuration after making this adjustment.

I apologize for the confusion in my previous answer. It seems that the

${SOURCE_NAMESPACE}

placeholder didn't work as expected in your case. Let's clarify this issue based on the available information. The behavior you're experiencing, where you got

_source_namespace.typeform_raw_streams_form_

instead of the actual source name, suggests that the placeholder wasn't properly replaced. This could be due to a few reasons: 1. The source (in this case, Typeform) might not be providing a namespace value. 2. There might be an issue with how the placeholder is being interpreted or processed. To address this, you have a couple of options: 1. Manual Configuration: Instead of using the

${SOURCE_NAMESPACE}

placeholder, you can manually set the namespace for each connection. In the connection settings, under the "Namespace" configuration, choose "Custom format" and directly enter the desired schema name (e.g., "typeform" for your Typeform source). 2. Stream Prefix: If you can't set the schema name directly, you might be able to use the "Stream Prefix" option to achieve a similar result. According to the [Configuring Schemas documentation](https://docs.airbyte.com/using-airbyte/configuring-schema#modify-stream-names): "To modify the stream name in the destination, use the connection-wide setting Stream prefix. Entering text here prepends the same text to each stream name in the destination, allowing for you to easily differentiate between streams of the same name in your destination." You could set the Stream Prefix to "typeform_" for your Typeform connection, which would result in table names like

typeform_form

in your destination. Remember that the exact options available might depend on your specific destination connector and Airbyte version. If these solutions don't work, you might need to check your connector's documentation or reach out to Airbyte support for more specific guidance. For future reference, when dealing with namespace and schema configurations, it's always a good idea to test the setup with a small dataset first to ensure it's working as expected before running a full sync. [Link title](URL)