How to Configure Teradata Read Only User

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a teradata read only user by making a dedicated role with select rights. Then you attach that role to a user profile with zero permanent disk space. Most data teams start by sharing one broad reporting account across several analysts. When permissions stay too wide, a single bad query can change tables or drain system CPU. How a teradata read only user works in native roles Teradata controls data access through a hierarchy of databases, users, roles, and profiles. In this engine, a

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.

You set up a teradata read only user by making a dedicated role with select rights. Then you attach that role to a user profile with zero permanent disk space. Most data teams start by sharing one broad reporting account across several analysts. When permissions stay too wide, a single bad query can change tables or drain system CPU.

How a teradata read only user works in native roles

Teradata controls data access through a hierarchy of databases, users, roles, and profiles. In this engine, a user and a database are almost the same object. A user is simply a database that holds a password and can log in.

To keep an account from making tables, admins set its permanent space to zero. Without permanent space, the account cannot store new tables or hold data objects. Next, the admin creates a dedicated role for reading data.

The admin grants select privileges on specific target databases or views to that role. If analysts need to inspect view logic, they also need the show privilege. Rather than granting rights to each person, admins assign the role to a user profile.

The profile also sets spool space limits and password rules for the group. Spool space holds temporary results while a large query runs. When you assign the role as the default, the user gets read rights at login.

View layers and spool limits for safe reporting

Many teams do not grant select rights directly on base tables. Instead, they build a separate database layer that only holds views. They grant the read role select access on those views alone.

This pattern keeps analysts from seeing raw staging tables or internal system columns. It also lets database admins change base table layouts without breaking analyst queries. Even with views, read queries can still lock tables if not managed well.

Read-Only Root Filesystem + User Provisioning (SCIM): architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Standard read queries place a read lock on the underlying table rows. That lock can block batch load jobs that need to write new data. Views often include locking modifiers for access so queries read rows without blocking writers.

Admins also set strict spool limits inside the user profile. If an analyst writes a bad join, the query hits the spool cap and stops. This protects the rest of the warehouse from running out of shared scratch space.

What native read roles solve and what they miss

Native roles and zero permanent space stop users from running insert, update, or drop statements. They give you a clean way to group analysts and enforce basic storage caps. Still, native permissions only check which tables or views a user can query.

Once a user has select rights on a table, they can read every column inside it by default. If that table holds emails, phone numbers, card numbers, or national IDs, the query returns them. Building separate views for every team and data sensitivity level takes constant manual work.

Shared read accounts also hide who actually ran a specific query. When five apps or ten contractors share one login, the database audit log shows one name. Static passwords for those accounts also sit in local scripts and desktop tools for months.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Why should a read only account have zero permanent space?

Zero permanent space stops the user from creating new tables or storing objects in their own schema. They can still run queries as long as their profile grants enough temporary spool space.

How do you grant read access to future tables in a database?

When you grant select on the database level, the role covers all current and future objects inside it. You do not need to update the role each time a team adds a new table.

How can we protect emails and card numbers from read users?

Native roles require you to build and maintain separate restricted views for each user group. A faster option is applying dynamic data masking that rewrites matched fields in query results in flight.

The query runs. The emails stay hidden.