External Article

The Importance of Caching

Performance tuning and optimization definitely have their place in minimizing SQL Server Licensing costs – by helping keep CPU utilization low. But it’s important to remember that the fastest and most efficient query possible is the one that you never execute against your SQL Server. That might sound trite, but it’s at the heart of caching – which is key to helping organizations save significant money on SQL Server licensing costs while simultaneously enabling better application performance and increased scalability.

External Article

The Promise - and the Pitfalls - of In-Memory OLTP

When SQL Server 2014 was released, it included Hekaton, Microsoft’s much talked about memory-optimized engine that brings In-Memory OLTP into play. With memory-optimized tables 30 times faster than disk-based tables, higher performance is promised – but at what cost? Jonathan Watts looks at the features that have improved, and those that need careful consideration.

Blogs

KDA: Echoes of Deception - Case 6

By

A cryptic message, a book cipher hidden in art provenance records, and a trail...

Capturing My Own Metrics: #SQLNewBlogger

By

A customer was trying to compare two tables and capture a state as a...

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

Read the latest Blogs

Forums

A Quick Second Opinion

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Second Opinion

Five Intelligent Query Processing Features in SQL Server 2022 That Quietly Tune Your Workload

By vgupta

Comments posted to this topic are about the item Five Intelligent Query Processing Features...

Checking the Error Log I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking the Error Log I

Visit the forum

Question of the Day

Checking the Error Log I

On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?

See possible answers