Shadab Shah (11/18/2013)
GilaMonster (11/18/2013)
None, there's no index useful for that query.I may be wrong over here but if none index is created on the table it gets stored on heap and retrival is slow. Hence i think one index should be created it can be on a random column.
With or without index, you're doing a full table scan, so indexes are worthless.
Maybe - and just maybe - you might benefit from a (clustered) columnstore index - if you're using SQL Server 2012 or 2014 - because those indexes compress the data really efficient and you might get less IO.
But this depends on a lot of factors, such as for example the number of unique values in your columns. It might even not help at all.
If you were not using * - shame on you - but just selecting a few columns, the columnstore index would give you some real benefit, as the reduced number of columns has a great impact on IO.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP