performance

External Article

Is Tempdb Causing a Bottleneck?

  • Article

One of your SQL Server instance shows a major dip in performance or throughput, affecting all the user databases. You notice that the slow interludes coincide, as if orchestrated. On investigation, it appears that several transactions running over that period were using a lot of space in tempdb. However, which of them, if any, are causing the tempdb bottleneck, and why?

2021-01-26

External Article

Right-Sizing Row Mode Query Memory Requirements

  • Article

When the optimizer doesn’t estimate the correct amount of memory for a query, either memory is wasted that could be used for other processes or some operations will spill to disk. Microsoft has added Memory Grant Feedback to help overcome this issue. In this article, Greg Larsen explains what you need to know about this new feature.

2020-06-10

Blogs

The Comprehensive Guide to Mastering Your SQL DBA Skills

By

Database administrators (DBAs) are the backbone of data-driven organizations. If you're looking to break...

Friday Basics: Authentication vs. Authorization

By

Another security fundamentals topic is authentication versus authorization. For those who have a clear...

A New Word: mcfeely

By

mcfeely – adj. inexplicably moved by predictable and well-worn sentiments, even if they are...

Read the latest Blogs

Forums

How to install mysql-connector-python-8.4.0.zip it does not have setup.py

By ivanb

How to install mysql-connector-python-8.4.0.zip it does not have setup.py. Checked also: mysql-connector-python-8.4.0.tar.gz

when primary is down and not accessible failover not occured then how to recover

By naga.rohitkumar

HI All, can any one reply on this when primary is down and not...

The On-Call Load

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The On-Call Load

Visit the forum

Question of the Day

Two Table Hints

What happens when I run this code:

SELECT
  p.ProductName
, p.ProductCategory
FROM dbo.Product AS p WITH (NOLOCK, TABLOCK);

See possible answers