Jeff Moden

  • Interests: SQL. When Im not having fun with that, then SQL. ;-)

SQLServerCentral Article

How much will it cost or save to rebuild that index? (SQL Oolie)

What's the true and permanent cost of lowering the Fill Factor of an index in SQL Server? It's a lot more than many people think. 9 year SQL Server MVP veteran, Jeff Moden, demonstrates how to calculate the extra space that will be used by lowering the Fill Factor and saved by increasing it.

4.35 (17)

You rated this post out of 5. Change rating

2021-05-28 (first published: )

10,108 reads

SQLServerCentral Article

Some T-SQL INSERTs DO Follow the Fill Factor! (SQL Oolie)

With origins from the world of “Submarine ‘Dolphin’ Qualification” questions, an “Oolie” is a difficult question to answer, or the knowledge or fact needed to answer such a question, that may or may not pertain to one's duties but tests one's knowledge of a system or process to the limit. Introduction Contrary to what many […]

5 (10)

You rated this post out of 5. Change rating

2019-08-08

6,280 reads

SQLServerCentral Article

A Simple Formula to Calculate the ISO Week Number

He admits it wasn't his idea but his head sure wishes it was. SQL Server MVP Jeff Moden explains a wonderful, super simple, very high performance formula that will calculate ISO Week Numbers. If you're "stuck" with SQL Server 2005 or less, you're going to like this a whole lot!

4.89 (36)

You rated this post out of 5. Change rating

2015-10-23 (first published: )

37,938 reads

SQLServerCentral Article

Calculating Duration Using DATETIME Start and End Dates (SQL Spackle)

It's an old problem with a solution that's nearly as old. SQL Server MVP Jeff Moden shows us the old trick mixed with a slick trick to format the duration as extended hours, minutes, seconds, and milliseconds.

4.84 (50)

You rated this post out of 5. Change rating

2015-04-03 (first published: )

62,882 reads

SQLServerCentral Article

Hierarchies on Steroids #1: Convert an Adjacency List to Nested Sets

SQL Server MVP Jeff Moden shows us a new very high performance method to convert an "Adjacency List" to “Nested Sets” on a million node hierarchy in less than a minute and 100,000 nodes in just seconds. Not surprisingly, the "steroids" come in a bottle labeled "Tally Table".

4.9 (63)

You rated this post out of 5. Change rating

2014-09-19 (first published: )

42,066 reads

SQLServerCentral Article

How to Make Scalar UDFs Run Faster (SQL Spackle)

It's a well known fact that Scalar UDFs are the stuff of performance nightmares in T-SQL. But are they really as bad as they say? SQL Server MVP Jeff Moden shows us that they might not really be as big a problem as you might think and what you can do when they actually are.

4.93 (102)

You rated this post out of 5. Change rating

2014-06-24 (first published: )

27,186 reads

Blogs

Time to Revive our YouTube Channel

By

It’s been forgotten about and neglected for few years but I’ve decided to dust...

Microsoft MVP 2025: Continuing the Data Platform Journey

By

I am honored to announce that I have been renewed as a Microsoft MVP...

What is KTLO? Keep The Lights On vs Project Work in Agile

By

🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Navigating Multi Platform Realities in My Database Life

By dbakevlar

Comments posted to this topic are about the item Navigating Multi Platform Realities in...

Import/Export SSMS Settings issue

By Brandie Tarvin

I have tried a number of times to export and then import my SSMS...

Visit the forum

Question of the Day

Query Plan Regressions --

For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question:  You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?

See possible answers