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

T-SQL Tuesday #198 Roundup: How Do You Detect Data Changes?

By

Thank you to everyone who participated in T-SQL Tuesday #198! When I wrote the...

Optimizing Redshift Performance by Configuring WLM Queues

By

Efficient query performance in Amazon Redshift often comes down to how well you manage...

PowerShell Strikes Back: Return of the Loop

By

Welcome back to PowerShell Strikes Back. We’re three weeks in, and the training is...

Read the latest Blogs

Forums

BCA KCU SURYOPRANOTO No.Telpon 087781685647

By ricardooliveira

Whatsapp 087781685647 Jl. Suryopranoto No.40, RT.12/RW.7, Petojo Utara, Kecamatan Gambir, Kota Jakarta Pusat, Daerah...

Stairway to Reliable Database Deployment Level 3 – Rehearsing Changesets Across Environments

By Massimo Preitano

Comments posted to this topic are about the item Stairway to Reliable Database Deployment...

QUOTENAME Quote Parameters

By Steve Jones - SSC Editor

Comments posted to this topic are about the item QUOTENAME Quote Parameters

Visit the forum

Question of the Day

QUOTENAME Quote Parameters

When I use QUOTENAME(), I can optionally provide the character used to surround the string in the result. Can I use any character?

See possible answers