SQL Server engine errors

SQL Server 229 Permission Denied

229
MediumDatabase Engine

Permission Denied — the current user lacks the required permission on the object

What 229 Means

The 229 error on the SQL Server engine errors indicates permission denied — the current user lacks the required permission on the object. This typically occurs due to the database user has not been granted select, execute, or other required permissions.

Error 229 is a granular permission failure. Unlike error 18456 (login failure) or 4060 (database access failure), error 229 means the user is authenticated and inside the database but lacks specific object-level permission.

Technical Background

SQL Server uses a layered security model: server-level logins, database-level users, and object-level permissions. Error 229 fires at the third layer. The user passed server authentication and database authorization but was denied when accessing a specific table, view, stored procedure, or function.

The error message includes both the permission type (SELECT, EXECUTE, ALTER, etc.) and the fully qualified object name. This makes the required remediation very specific compared to broader access errors.

Common Causes

  • The database user has not been granted SELECT, EXECUTE, or other required permissions
  • A schema change removed permissions that were previously inherited
  • Role membership does not include access to the specific object

Typical Scenarios

  • A developer queries a production table they have not been explicitly granted access to
  • An application fails after a DBA restructured schema ownership and object permissions

What to Know

The error message itself identifies the exact permission type and object name that was denied. This precision makes it one of the more straightforward security errors to diagnose in SQL Server.

Frequently Asked Questions

Common questions about SQL Server 229 error

Error 18456 is a login-level failure (wrong credentials), while 229 means the login succeeded but the user lacks permission on a specific database object like a table or stored procedure.