'NEXT' in 5.0 version

asieraies
asieraies Member Posts: 49
edited 2007-04-06 in SQL Performance
Hi,

In version 5.0 with SqlServer2005, has "NEXT" any improvement?

Thanks

Asier

Comments

  • frede
    frede Member Posts: 80
    No - but you have the FINDFIRST, FINDLAST AND FINDSET which should make it faster to do the searches through the database with the NEXT command.
    Regards,

    Henrik Frederiksen, Denmark
  • davmac1
    davmac1 Member Posts: 1,283
    And don't make updates directly to records in the NEXT set - use a temp table
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • bbrown
    bbrown Member Posts: 3,268
    davmac1 wrote:
    And don't make updates directly to records in the NEXT set - use a temp table

    This is only an issue if updating fields that are part of the current key. In that case use FINDSET(TRUE,TRUE) and copy the record to another record variable before modifying
    There are no bugs - only undocumented features.
  • Waldo
    Waldo Member Posts: 3,412
    Well, to be hones ... it should have been done this way, even without the new FINDSET-statement, don't you agree?

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • bbrown
    bbrown Member Posts: 3,268
    True
    There are no bugs - only undocumented features.
  • kriki
    kriki Member, Moderator Posts: 9,121
    [Topic moved from Upcoming version NAV 5.1 forum to SQL Performance forum]
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

Categories