How to use CURRENT_USER in SQL Server

How do I get the current SQL Server user in a query?

CURRENT_USER returns the name of the SQL Server database principal executing the statement.

Welcome to the Galaxy, Guardian!

Oops! Something went wrong while submitting the form.

Description

What does CURRENT_USER return?

CURRENT_USER returns the database user name that SQL Server maps to the current execution context. It reflects EXECUTE AS impersonation, making it ideal for auditing and row-level security.

How do I select the current user?

Run SELECT CURRENT_USER; in any query window. The function is parameter-less, so parentheses are not required. The result is a single-row, single-column result set containing the user name.

Why choose CURRENT_USER over SESSION_USER?

SESSION_USER shows the login at connection time, ignoring EXECUTE AS. CURRENT_USER respects impersonation, so use it inside stored procedures, triggers, or dynamic SQL where context can switch.

When is CURRENT_USER most useful?

Typical cases include auditing which database principal touched data, enforcing row-level security predicates, tagging rows with the creator, and validating permissions inside stored procedures.

What is the exact syntax for CURRENT_USER?

The keyword stands alone; no schema prefix, brackets, or parentheses are needed. Combine it with computed columns, variables, filters, or INSERT statements.

Syntax breakdown

CURRENT_USER

How can I store CURRENT_USER in ecommerce tables?

Add a created_by column to tables like Orders. Insert rows with CURRENT_USER so you always know which service account or analyst created the order record.

Best practices for CURRENT_USER

Always qualify permissions with schema names to avoid broken ownership chains. Pair CURRENT_USER with ORIGINAL_LOGIN() for complete audit trails. Avoid caching the value in variables unless absolutely necessary.

Common mistakes and how to avoid them

Using SESSION_USER when EXECUTE AS is active. Replace with CURRENT_USER to capture impersonated principals.

Casting CURRENT_USER to INT. The value is varchar. Keep it as text or join against sys.database_principals for IDs.

Why How to use CURRENT_USER in SQL Server is important

How to use CURRENT_USER in SQL Server Example Usage


-- Show who is running the query and their recent orders
SELECT CURRENT_USER   AS RunningUser,
       o.id           AS OrderID,
       o.total_amount AS Total
FROM   Orders o
WHERE  o.created_by = CURRENT_USER;

How to use CURRENT_USER in SQL Server Syntax


-- Basic retrieval
SELECT CURRENT_USER;

-- Audit insert in Orders table
INSERT INTO Orders (customer_id, order_date, total_amount, created_by)
VALUES (42, GETDATE(), 199.99, CURRENT_USER);

-- Filter rows created by current user
SELECT *
FROM Orders
WHERE created_by = CURRENT_USER;

-- Use inside a view for row-level security
CREATE VIEW Orders_CurrentUser AS
SELECT * FROM Orders WHERE created_by = CURRENT_USER;

Common Mistakes

Relying on SESSION_USER inside stored procedures that use EXECUTE AS. SESSION_USER ignores impersonation, leading to incorrect audit data. Use CURRENT_USER instead.
Assuming CURRENT_USER returns the server login. It returns the database user. Join with sys.server_principals if you need the server-level login.