One note if you use top and there are some equal values, you might get more than the number you require returned. A simple fix is to add the unique id at the end of the Order by list.
-----Original Message----- From: Rob Baxter [mailto:[EMAIL PROTECTED]] Sent: Friday, 3 May 2002 10:31 a.m. To: CF-Talk Subject: RE: SELECT TOP n vs MaxRows... It would seem that TOP is more efficient because you're dropping the extra rows on the sql side instead of the cf side, thereby saving yourself some resources on the recordset transfer. </rob> -----Original Message----- From: Tyler Silcox [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 6:32 PM To: CF-Talk Subject: SELECT TOP n vs MaxRows... A quickie: Is there any benefit to using SELECT TOP n vs using the MaxRows attribute in cfquery? Tyler Silcox email | [EMAIL PROTECTED] ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
