Posted by JayCallas on 03/29/06 07:23

Thanks Erland for responding. As usual your posts are very helpful.

So, a Clustered Index Scan is as bad as a Table Scan? In this case,
what is it actually checking? The LoadDate is not even used in the
query so I am not sure what it is scanning for. Is it just using the
scan to look up the rest of the row?

As I already knew that the particular WHERE clause was bad, was I just
lucky all this time that the response time was good? Maybe because
there had not been any changes to the view or table in ages? Or maybe
because the plan was determined when there was a lot less data in the
table? Do query plans survive server reboots or restarting SQL?

Will take a look at the index hint any see how it goes.

• Next in forum: how to setup the permission of share fold in log shipping ?
• Prev in forum: Re: SQL Server 2005: Collation Conflict Error when selecting Database Properties
• Thread view: Re: Odd query plan for view

[Reply to this message]