External Article

Investigating the Cause of SQL Server High CPU Load Conditions When They Happen

Any DBA who is trying to find the cause of an intermittent problem with a server or database dreams of being able to use a query or procedure take a snap of the relevant variables at the point when the problem occurred. Laerte takes an example of a slow-running query hogging resources to show that you can run queries when a WMI alert is fired, and save the results for later inspection, whenever it happens.

Blogs

Why Database AI Agents need Layers?

By

Third part in my Ai series with databases. When building AI solutions within the...

Un-Migrating From the Cloud: T-SQL Tuesday #199

By

This month we have a very interesting invitation from Koen Verbeeck. He has hosted...

T-SQL Tuesday #199: Back to the on-prem

By

It’s the second tuesday of the month, which means T-SQL Tuesday time! This month’s...

Read the latest Blogs

Forums

Unable to restrict permission

By LearningDBA

I have 13 restricted views in my EDW DB. 6 of them are created...

Install SQL Scripts via GUI Wizard

By Jörg

Hallo all! My problem is this: I have quite a bunch of TSQL scripts...

Would You Retire Rather Than ...

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Would You Retire Rather Than...

Visit the forum

Question of the Day

Converting Money

Does this run successfully on a SQL Server 2022, US English default installation?

DECLARE @YenAmount MONEY;
SET @YenAmount = ¥1500; 

SELECT @YenAmount AS RawValue;

See possible answers