The Red9 Blog
Get our new tips before anyone else. Enter your email below to join our private list!
Most Popular Red9 Posts
Latest From Red9
Never use the full recovery model without a backup
Full Recovery mode without backup logs Why should you care about it? If you are using a database is in Full Recovery Model or Bulk
Forcing index, order, and join hints and being careful
Why should you care about SQL Server query hints? Hints in SQL queries is like a double-edged sword. While you might find a better query
How to find slow SQL queries using DMVs in SQL Server?
What is Dynamic Management Views (DMVs)? Introduced within SQL Server 2005, SQL Dynamic Management Views (DMVs) are significant features of SQL Server. There are several
Why should you care about users with elevated permissions in SQL Server?
The security model offered by Microsoft SQL Server is highly configurable and very robust when all security best practices are followed. Why should you care
Improve your SQL Server performance enabling data compression
What is the data compression feature in SQL Server? It is a feature introduced in SQL Server 2008 Enterprise Edition. Later, Microsoft added to Standard
How to keep SQL Server Management Studio (SSMS) updated?
Microsoft pealed out SQL Server Management Studio (SSMS) into its own distribution from SQL Server. SQL world would only get new SSMS every time new
Should you use the SQL Server change tracking feature?
What is the SQL Server change trackings feature? Change tracking was introduced in SQL Server 2008 to help you sync data. It allows relatively easy
Index Tuning for Performance in SQL Server
You’ve probably heard: “indexes are not free”. And this is right! Indexes can greatly improve queries performance in the SQL server, but they may hamper
How to enable SQL Server Query Store: Best Practices
What is the Query Store? The SQL Server Query Store is a feature introduced in SQL Server 2016. It provides you with insight on query plan choice
[Case Study] We did SQL Performance Tuning and now TSQL is running 2,307 (not a typo) times faster! How did we do it?
Description: Problem: Stored procedure takes 38 seconds to execute. It times out on the application front-end. It was performing multiple scans and reading too much
[Case Study] We tuned SQL Server Performance and now it runs 57 times faster(not a typo)! How did we do it?
Description: Problem: This stored procedure showed up in the top resource-consuming report. It was putting too much stress on the CPU. Solution: Added two new
[Case Study] We tuned SQL Server Performance and now its 9,320 TIMES faster(not a typo)! How did we do it?
Description: Problem: Select command inside trigger (EHRHist<removed>_AFTER_INSERT_UPDATE) doing an index scan. Solution: Added an index. Command: Change: Before: After: Technical Background: Most SQL Servers bottleneck