Missing column statistics from default trace

Question

I am seeing Missing statistics events on my default trace and was wondering whether I need to create statistics on the table.

Missing Column Statistics

Is this a good practice considering the advice on http://msdn.microsoft.com/en-us/library/ms190397.aspx

Answer 1

Yes you are right .As per the same Article :

Consider creating statistics with the CREATE STATISTICS statement when any of the following applies:

The Database Engine Tuning Advisor suggests creating statistics.

The query predicate contains multiple correlated columns that are not already in the same index.

The query selects from a subset of data.

The query has missing statistics.

 

---

Abhay Chaudhary OCP 9i, MCTS/MCITP (SQL Server 2005, 2008, 2005 BI) ms-abhay.blogspot.com/

Answer 2

I think this columns is not a part of any index ....else stats are automatically created .

---

Abhay Chaudhary OCP 9i, MCTS/MCITP (SQL Server 2005, 2008, 2005 BI) ms-abhay.blogspot.com/

Answer 3

You might find the information in this older post interesting:

http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d881009e-afbc-4857-879b-7e4983ca6cfc

I show a couple of ways of querying the plan cache to find further information about the specific queries that actually triggered the Missing Column Statistics warnings.  In addition I also provide a number of links to blog posts by Kimberly Tripp and Connor Cunningham (the current PM for the SQL Optimizer team) about column statistics inside the database engine.

---

Jonathan Kehayias
http://sqlblog.com/blogs/jonathan_kehayias/
http://www.twitter.com/SQLSarg
http://www.sqlclr.net/
Please click the Mark as Answer button if a post solves your problem!