On Tue, Jan 7, 2014 at 3:45 PM, Mark Rotteveel <m...@lawinegevaar.nl> wrote:
>
> With the SQL Server syntax optimizing for retrieval of the first 150
> rows is done with:
>
> SELECT ...
> FROM someTable
> ...
> OPTION (FAST 150)
>
> It also contains an interesting option (OPTIMIZE FOR) for 'helping' the
> optimizer decide on a plan by providing exemplar values for parameters.
>
A problem I'm having with general solutions is that (as far as I know) we're
not dealing with a general problem. The problem of slow access to the
first record is specific to queries with an ORDER BY and no FIRST/ROWS
clause. Adding a general mechanism opens the door to a lot more
opportunities to paper over optimizer problems and blame the user for
bad performance.
Cheers,
Ann
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
