SQL Server user for Renta

Renta signs in to SQL Server as a regular database user and works only inside the database named in the connection. This page shows how to create such an account and which permissions it needs.

Run the statements from an administrator account, such as the server admin of your Azure SQL server or a member of db_owner.

What Renta runs in your database

Every permission below maps to a statement the connector issues.

Create the user

On Azure SQL Database, create a contained user directly in the target database.

CREATE USER renta WITH PASSWORD = 'your-strong-password';

On a self-managed server or Amazon RDS, create a server login first and attach a database user to it.

CREATE LOGIN renta WITH PASSWORD = 'your-strong-password';
GO
USE your_database;
CREATE USER renta FOR LOGIN renta;

Use the same name and password in the User and Password fields of the SQL Server connection in Renta.

Grant permissions

Run the grants in the database the connection points to. They cover the whole dbo schema, so tables of future pipelines need no extra statements.

GRANT CREATE TABLE TO renta;
GRANT ALTER ON SCHEMA::dbo TO renta;
GRANT SELECT, INSERT, DELETE ON SCHEMA::dbo TO renta;

The set is minimal on purpose. The account stays inside one schema of one database and cannot change anything else on the server.

Check the result

Read back the permissions the account actually holds.

EXECUTE AS USER = 'renta';
SELECT permission_name FROM fn_my_permissions('dbo', 'SCHEMA')
UNION ALL
SELECT permission_name FROM fn_my_permissions(NULL, 'DATABASE')
WHERE permission_name = 'CREATE TABLE';
REVERT;

The output must include SELECT, INSERT, DELETE, ALTER, and CREATE TABLE.

Then open the SQL Server destination page, fill in the connection form, and click Save. Renta runs a test query against the database and reports a permission problem immediately.