How to Configure Make SQL Server Credentials
To set up make sql server credentials, create a dedicated database user first. Then store that login inside your Make scenario to run automated queries. Many teams take a shortcut and reuse an admin account for this step. That broad role lets a single bad workflow change or drop production tables. A safe setup pairs a scoped SQL Server identity with strict database roles. How to set up make sql server credentials in your database Start by picking the right identity type inside SQL Server for
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
To set up make sql server credentials, create a dedicated database user first. Then store that login inside your Make scenario to run automated queries. Many teams take a shortcut and reuse an admin account for this step. That broad role lets a single bad workflow change or drop production tables. A safe setup pairs a scoped SQL Server identity with strict database roles.
How to set up make sql server credentials in your database
Start by picking the right identity type inside SQL Server for your app. SQL Server supports thirteen different types of database users for various login needs. A database user represents the identity of a login when it connects. If Make needs to reach many databases on one instance, use a login. You create that SQL login inside the master database first. Then you map a database user to that login in each target database.
If Make only touches one database, a contained database user is another option. This user has a password and does not tie to a master login. An admin must enable contained databases on the server and database first. Either option gives your Make scenarios a dedicated identity to log in with.
Next, assign fixed database roles to control what your new user can do. You cannot change the base permissions assigned to fixed database roles. Every role, including the public role, grants the basic permission to connect. If your Make scenario only pulls records, assign the fixed datareader role. Members of this role can read all data from all user tables. They can also read from all views inside that database. If the scenario must insert or update rows, add the datawriter role. That role lets the user add, delete, or change data in user tables. Never give the database owner role to an automation tool. Database owners can run all maintenance tasks and even drop the whole database.
What native roles solve and where gaps remain
Fixed database roles do a good job of blocking broad actions at login. You can also apply deny roles to block read or write actions fast. A deny datareader role stops a user from reading any user tables. A deny datawriter role blocks all adds, changes, and deletes on user tables. These rules help you lock down the baseline permissions for your Make user.
Ephemeral Credentials + Kubernetes API Server Access: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Still, native database roles only check who logs in at the table level. They do not inspect what individual queries do while they run in flight. A user with the datareader role can read every column in every table by default. That means a Make workflow can pull emails, phone numbers, and card numbers. It can also pull national IDs and send them to outside web apps. Similarly, a user with the datawriter role can delete every row by mistake by default. Native roles also force you to store static passwords inside the Make platform. If someone copies those keys, they gain full database permissions right away. Teams need a way to inspect queries and mask sensitive fields in results.
Govern SQL Server queries and responses in flight
Table grants decide which SQL Server objects a caller may touch. They do not check query intent or rewrite sensitive values in results across every client and agent. By design, hoop.dev is an open-source proxy that sits next to SQL Server as a sidecar for your SQL Server. It inspects TDS batches and parameterized queries in real time.
With hoop.dev guardrails and hoop.dev data masking, banned statements are refused with your message. Matched sensitive fields in supported result columns are masked in memory, and each decision is logged per listener. Check out the code on GitHub.
Frequently asked questions
Should I use a master login or a contained user for Make?
Use a login in master when Make needs to query several databases. Pick a contained database user when Make only needs one or two databases. Remember that an admin must turn on contained databases on the server first.
How do I make my SQL Server account read-only for Make?
Add your Make database user to the fixed datareader role. Combine it with the deny datawriter role so it cannot change any rows. Note that the datareader role still reads all user tables and views.
Why is the database owner role risky for Make workflows?
The database owner role allows all setup and maintenance tasks on the database. It even lets the user drop the entire database in SQL Server. A broken Make scenario with this role could wipe out your production data.
Related guides
In this post