Microsoft SQL Server destination

Renta delivers data from its sources into a Microsoft SQL Server database: a self-managed server, Azure SQL Database, or a managed service such as Amazon RDS for SQL Server.

Each pipeline manages a single table. Renta creates it on the first run with columns matching the fields you selected, and refreshes its contents on every following run.

Requirements

Prepare the server before you add the connection.

1. Network access.
   Renta connects to the database port (default 1433) from the Renta IP addresses. Allow them on the firewall. The server needs no outbound access: Renta delivers rows over the same database connection.
2. An existing database.
   Renta writes only into the database named in the connection and does not create databases. Tables land in the default schema of the connection user, which is dbo unless you changed it.
3. Dedicated user privileges.
   The account needs to create, fill, clear, and drop tables in that database. The exact statements are on the user page below.

Connect SQL Server as a destination

A connection stores the address of one SQL Server database together with the credentials Renta signs in with.

Go to the CatalogStep 1

1. In the Renta console, open Connections > Catalog in the left sidebar.
2. Expand the Data warehouse category and click the Microsoft SQL Server card.

Enter the server addressStep 2

Point the connection at the database:

1. Server hostname.
   The hostname or IP address of the server, without a protocol prefix. For Azure SQL Database this is the value like myserver.database.windows.net.
2. Database name.
   The existing database that will receive the tables.
3. Port.
   The database port. The SQL Server default is 1433.

Enter the credentialsStep 3

1. User.
   The SQL Server account created for Renta.
2. Password.
   The password of that account.

Turn on Trusted connection if you connect to the server over SSL.

Name the connection and saveStep 4

Enter a Destination name (a label used only in the Renta console) and click Save.

On save, Renta signs in to the database and runs a test query. A wrong password, a closed port, or a missing database comes back as an error right away, before any pipeline runs.

Verify the connectionStep 5

The connection appears in the Destinations list with the Active status and is ready to be used in pipelines.

Create a pipeline into SQL Server

The steps below use Display & Video 360 as the source, and the same flow applies to every other source.

Select the sourceStep 1

Click New pipeline in the left sidebar. Keep the ETL tab active, pick a source in the Already connected section, and click Next step.

Select the source connectionStep 2

Pick the source connection to extract data from and click Next step.

Select SQL Server as the destinationStep 3

On the Destination step, choose Microsoft SQL Server in the Already connected list and click Next step.

Select the destination connectionStep 4

Pick the SQL Server connection that will receive the data and click Next step. Each card shows the database name and host, which helps when the workspace holds several servers.

Pipeline configuration

The last step of the wizard gathers every pipeline setting on one page. Source-specific settings sit at the top, followed by the settings that look the same for every source.

Source settings

The first blocks define what to extract, so their content depends on the source. For Display & Video 360 these are the partner, the advertiser, and the report type.

Parameters

Tick the source fields to load. Every ticked field becomes a column of the SQL Server table, and the column name is written under each field.

To take every available field at once, click Select All. The Selected tab collects everything you ticked.

Integration and table name

The next block names the pipeline and its table.

1. Integration name.
   The display name of the pipeline in the Renta console.
2. Table name.
   The table Renta creates in the connected database. Keep the generated name or type your own. Use a unique name for every pipeline, because each pipeline rewrites its table on every run.

Date range

The date range bounds the history loaded on the first run and on a manual Full refresh.

1. Date start.
   The first day of the extraction window.
2. Date end.
   The last day of the window: a fixed date or a moving boundary such as Today.

Overwrite period

The overwrite period sets how many recent days are reloaded on every scheduled run. It applies to report types with a date column, which produce partitioned tables.

Renta deletes the rows of that window and inserts them again with fresh values. With Without overwrite data, past rows stay as they are and only new data is appended.

Schedule

The schedule controls when the pipeline runs. All times are in UTC.

For a Daily schedule, pick the Update time and click Create pipeline.

The new pipeline shows up on the Pipelines page under the ETL tab with its table name, run status, and extracted row count.

Destination table

Renta owns the destination table: it creates the table on the first run and rebuilds it when the pipeline field list changes.

Column names and types

Column names repeat the field names shown in the pipeline settings. Renta replaces . and : in a name with an underscore, so the field fee.amount becomes the column fee_amount.

A value missing in the source arrives as NULL, not as zero or an empty string.

Schema changes

Adding or removing a field changes the column list, so the table has to be rebuilt.

Sync strategy

How a table is refreshed depends on the report type of the source.

Troubleshooting

Renta maps known SQL Server responses to the messages below. Both can appear when you save the connection and during a run.

If a run fails with a message that is not in the table, check the run logs on the pipeline page and contact Renta support.