Technical Article

Engine Separation of Duties for the Application Developer

Separation of duties is an important consideration for databases and database applications. By properly defining schemas and roles, you can create a distinction between users who can manipulate data from those that administer the database. This paper discusses the topics of which application developers should be aware and provides a heuristic example to guide you in achieving separation of duties.

SQLServerCentral Article

How to Become an Exceptional DBA

Brad McGehee provides a "career guide" for DBAs. It is intended both to help prospective DBAs find a "way in" to the profession, and to advise existing DBAs on how they can excel at their jobs, and so become Exceptional DBAs.

Blogs

From Firefighting to Future‑Building: SQL Server 2025 and the New DataOps Mindset

By

There are moments in technology when the ground shifts beneath our feet. Moments when...

Why Developers Shouldn’t Have sysadmin access in SQL Server

By

 Why Developers Shouldn’t Have sysadmin access in SQL Server 7 reasons—and exactly what to do instead It...

A New Word: Ecstatic Shock

By

ecstatic shock – n. a surge of energy upon catching a glimpse from someone...

Read the latest Blogs

Forums

sp_prepare and sp_execute vs sp_executesql

By rajemessage 14195

I have noticed sp_executesql also makes a single plan for a stmt with parameter...

Who am I?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Who am I?

Find Invalid Objects in SQL Server

By Nisarg Upadhyay

Comments posted to this topic are about the item Find Invalid Objects in SQL...

Visit the forum

Question of the Day

Who am I?

If I want to track which login called a stored procedure and use the value in an audit, what function can I use to replace the xxx below?

create procedure AddNewCustomer
  @customername varchar(200)
AS
BEGIN
    DECLARE @added VARCHAR(100)
    SELECT @added = xxx

    IF @customername IS NOT NULL
      INSERT dbo.Customer
      (
          CustomerName,
          AddedBy 
      )
      VALUES
      (@customername, @added)
END

See possible answers