Post reply

different execution plan on SQL7 and SQL2000

  • July 6, 2004 at 8:24 am

    #513460

    Check whether the indexes on the tables are the same - hash match and clustered index scan both indicate that no useful index has been found.

  • July 8, 2004 at 10:24 pm

    #513964

    I have seen SQL2000 problem with comparisons between Unicode (Nvarchar) and regular varchar after conversion from 7 (they did implicit conversion the opposite way).

    Another one might be Collation - default collation of a new SQL2000 install is different than converting from SQL7. Although usually this causes errors not slowness.

Viewing 2 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply