Articles

External Article

Using the kill to cure

Code profiling tools can help cure most performance problems, but sometimes the problem is so severe that you'll first need to know how to wield computing's least understood tool, the debugger, before diving in with the Profiler. Brian Donahue, Crash Scene Investigator, is on hand to explain why.

2007-11-02

2,944 reads

Blogs

A Broken Copilot Query

By

I was testing the new SSMS (v22 Preview 3) with Copilot and ran into...

SQL Server Alerts

By

Don’t Let Trouble Sneak Up on You   Most SQL Servers run quietly. Until...

Prompt AI helping with Auditing

By

I had a conversation with a customer asking this question: how can I tell...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

Building a RESTful API with FastAPI and PostgreSQL

By sabyda

Comments posted to this topic are about the item Building a RESTful API with...

The Journey to PostgreSQL (or anything)

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Journey to PostgreSQL (or...

Visit the forum

Question of the Day

A Common Split

What happens when I run this code:

DECLARE @s VARCHAR(1000) = 'apple, pear, peach'
SELECT *
FROM STRING_SPLIT(@s, ', ')

See possible answers