InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 12:36:25 GMT20http://www.sqlservercentral.com/Forums/Topic1405298-392-1.aspxThanks Howard (sorry I forgot in my first reply) and Gail. Thu, 10 Jan 2013 04:03:03 GMTJason-299789http://www.sqlservercentral.com/Forums/Topic1405298-392-1.aspx[quote][b]Jason-299789 (1/10/2013)[/b][hr]It is also my understanding that while you can get data being returned faster from the initial execute you can also end up with a sub optimal plan being used, is this correct?[/quote]Correct. The point of the hint is that you want to ensure that the first few rows arrive fast and you don't mind if then entire resultset takes longer than it would otherwise. The optimiser avoids blocking operations (like sorts or hashes) as far as possible, even if they may be the lowest cost option.Thu, 10 Jan 2013 03:44:44 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1405298-392-1.aspxThese are 'end user' views, and used to feed SSAS and reports, the tables are pretty small with around 100-150 million rows in, although it seems some of the developers have heard the 'good news' about this and it seems to be creeping into other areas as well.I've done some 'prelim' testing using the views with and with out the hint and the results are interesting, in that data is returning around 4 times fast without the hint.Thu, 10 Jan 2013 03:33:39 GMTJason-299789http://www.sqlservercentral.com/Forums/Topic1405298-392-1.aspxThe views are used to populate the DW, rather than for end user queries? Yes, they can definitely produce sub-optimal plans as by definition, they sacrifice overall execution time in order to get the first rows out quicker. So generally, unless statistics are incorrect or there's another reason that it's "tricking" the optimiser into picking a better plan, there's nothing to gain and much to lose from the hint.The hint is generally only used for queries that an end-user is receiving the results for and implements client-side paging, to give the appearance of a more responsive system.Thu, 10 Jan 2013 03:27:25 GMTHowardWhttp://www.sqlservercentral.com/Forums/Topic1405298-392-1.aspxI've been doing a review of a DW project and noticed that several of the views use a WITH (FASTFIRSTROW)I need to start putting together a list of issues, but I'm unsure how to put this down as a possible issue, the first issue is a future compatibilty as I'm aware that the FASTFIRSTROW hint is being deprecated and replaced with OPTION(FAST n).It is also my understanding that while you can get data being returned faster from the initial execute you can also end up with a sub optimal plan being used, is this correct?Are there any other issues that anyone can point out.Thu, 10 Jan 2013 02:57:35 GMTJason-299789