External Article

How to Get SQL Server Security Horribly Wrong

It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.

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