"When an index scan is done on the clustered index, it’s a table scan in all but name."
Then why do we see index scan and table scan separately in execution plan rather just table scan on a single query with simple join?
Possibly because they're against different indexes or different tables?
What I'm saying there is that a clustered index scan is virtually the same as a table scan. You won't see the table scan operation against a table that has a clustered index. It appears in the execution plan as a clustered index scan. That doesn't make it any more efficient than a table scan.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass