Comments on: SQL SERVER – Challenge – Puzzle – Usage of FAST Hint

By: Ankit

Ankit — Fri, 12 Apr 2013 10:53:23 +0000

which query is ruuning faster?
1. Select * from tablename
Or
Select Column1,Column2,…. from tablename.

By: SQL SERVER – Weekly Series – Memory Lane – #006 « SQL Server Journey with SQL Authority

Sat, 08 Dec 2012 01:31:06 +0000

[...] SQL SERVER – Challenge – Puzzle – Usage of FAST Hint (Solution) [...]

By: Michael

Michael — Fri, 07 Dec 2012 03:33:57 +0000

I’ve seen it used in in situations where the query is feeding an SSIS package. For big record sets this can make a difference because SSIS can start to process the returned records sooner.

By: SQL SERVER – Weekly Series – Memory Lane – #005 « SQL Server Journey with SQL Authority

Sat, 01 Dec 2012 01:31:14 +0000

[...] SQL SERVER – Challenge – Puzzle – Usage of FAST Hint [...]

By: SQL SERVER – Solution – Challenge – Puzzle – Usage of FAST Hint Journey to SQL Authority with Pinal Dave

Mon, 06 Dec 2010 01:31:34 +0000

[...] The puzzle was posted here: SQL SERVER – Challenge – Puzzle – Usage of FAST Hint [...]

By: samira

samira — Sun, 05 Dec 2010 19:40:41 +0000

I never use this hint
but I think it maybe usefull for some reporters which not showing data until recieve it all.

if programmer can trick the reporter and with this syntax show preview of first page of report, it will be usefull for many situations

By: pinaldave

pinaldave — Wed, 01 Dec 2010 04:44:34 +0000

This is great blog post Sir!

I think you nailed it!

By: SQL SERVER – 3 Simple Puzzles – Need Your Suggestions « Journey to SQL Authority with Pinal Dave

Wed, 01 Dec 2010 01:31:54 +0000

[...] SQL SERVER – Challenge – Puzzle – Usage of FAST Hint [...]

By: Brad Schulz

Brad Schulz — Tue, 30 Nov 2010 18:49:00 +0000

Hi Pinal…

I wrote a blog post in August that gave an example of using the FAST hint:

http://bradsruminations.blogspot.com/2010/08/taking-hint.html

The FAST hint won’t help in just scanning one table… but it can help in JOINs.

–Brad

By: Ewelina

Ewelina — Mon, 29 Nov 2010 09:12:03 +0000

Hello Pinal,
Thank You for writting this topic! It helped me to figure out how to accelerate my view. It uses couple unions, and one pivot, and the difference is really very important!
I really appreciate Your work. Keep it simple ! :)

By: SQL SERVER – Challenge – Puzzle – Why does RIGHT JOIN Exists Journey to SQL Authority with Pinal Dave

Sun, 28 Nov 2010 01:31:53 +0000

[...] SQL SERVER – Challenge – Puzzle – Usage of FAST Hint [...]

By: SQL SERVER – Challenge – Puzzle – Why does RIGHT JOIN Exists Journey to SQL Authority with Pinal Dave

Sat, 27 Nov 2010 01:31:42 +0000

[...] I wrote SQL SERVER – Challenge – Puzzle – Usage of FAST Hint and I did receive some good comments. Here is another question to tease your mind. Run following [...]

By: Ramdas

Ramdas — Fri, 26 Nov 2010 16:12:54 +0000

Thanks for witing on this topic, Looks like these can be used in certain scenarios like DISTINCT, would like to check this out.

By: aasim abdullah

aasim abdullah — Fri, 26 Nov 2010 06:10:08 +0000

We have many complex queries, most of them returns DISTINCT rows. These query are slow because of DISTINCT. When ever we need to get some quick results we like to use FAST hint. Which omits sort process for distinct values and returns results quickly.

By: Benjamin Nevarez

Benjamin Nevarez — Fri, 26 Nov 2010 01:57:10 +0000

Something I wrote for Chapter 7 of my book about the Query Optimizer

“This hint can help in applications where you want to retrieve the first records of a query as quickly as possible and perhaps you will not be using the remaining records of the query at all. The price to pay for achieving this goal is that retrieving the remaining records of the query may take longer than a plan without this hint. The Query Optimizer usually accomplishes this goal by avoiding any blocking operators, like sort, hash join or hash aggregation, so the client submitting the query does not have to wait before producing the first records. Since the query is optimized to retrieve the first N records as soon as possible, retrieving all the records of the query may be very expensive.”

Ben