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

Houston AI-Lytics 2026–Powerpoint Slides

By

Thanks to everyone for attending my session on running a Local LLM. If you...

The Book of Redgate: Do the Right Things

By

I do believe that Redgate has been very customer focused since it’s inception. I’ve...

GenAI vs Dashboards: Not the Same (And Never Will Be)

By

There’s a question I’ve been hearing more and more lately, especially as Copilot, Fabric,...

Read the latest Blogs

Forums

Warning: Could not open global shared memory to communicate with performance DLL

By water490

Hi everyone I am getting below warning when I run SSIS: Warning: 0x80049304 at...

Let's Talk Community Events!

By Pat Wright

Comments posted to this topic are about the item Let's Talk Community Events!

that one limitation in replication

By stan

Hi as shown below a replication target requires a primary key.  if we want...

Visit the forum

Question of the Day

Detecting Deadlocks

By default, how often is the SQL Server Database Engine checking for deadlocks?

See possible answers