Articles

SQLServerCentral Article

The Paradox of NOLOCK: How Dirty Reads Can Sometimes Be Cleaner

Every SQL Server developer has heard it: "Don't use NOLOCK in production!" But this common rule isn't as simple as it seems. Sometimes, what seems like a bad practice can actually be the right choice. Let's explain what NOLOCK really does in simple terms. When you use NOLOCK, you're telling SQL Server "just show me […]

3.89 (9)

You rated this post out of 5. Change rating

2024-12-09

4,944 reads

External Article

Data Control Language (aka Security)

Like ancient Gaul, SQL is divided into three sub- languages. The DDL (Data Declaration Language) declares the data. This is where we find the data types, constraints, references and other structures that have to do with how the data stored . The DML (Data Manipulation Language) uses those declarations to change their contents or to invoke them. It does not change structures and schema objects.

2024-12-04

Blogs

A New Word: Ecstatic Shock

By

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

The CDO’s Playbook for AI Driven Decision Making

By

The New Arena of Leadership The role of the Chief Data Officer is no...

sp_snapshot – The easy way to take database snapshots of one or more databases – V3.0

By

Presenting you with an updated version of our sp_snapshot procedure, allowing you to easily...

Read the latest Blogs

Forums

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...

Lessons from the Postmark-MCP Backdoor

By dbakevlar

Comments posted to this topic are about the item Lessons from the Postmark-MCP Backdoor

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