pkapas (1/22/2015)
Haha, well that's a + for Microsoft then. A good product starts with making sure it can adapt to even inexperienced users. I'm planning on getting better with SQL Server in the next couple of years, but I guess I can only do that by researching and trying out new things. Any ideas how I could try to tweak my SQL Server, or change defaults to get better performance? I'm not an expert at understanding the execution plan either. Where are you supposed to look at the number of rows that are estimated. Is it at the last step. For that one it says 3.30018 rows. Is this the issue, that it cannot estimate the proper number of rows? The actually rows affected was 12192. Why am I getting a bad estimation?
There are a myriad of reasons for bad estimates.
Best way to a) get your system in shape and b) learn, is to have your company bring in an expert for a performance review. Significant ROI there on many levels. Stuff like this is shooting fish in a barrel for a qualified consultant!!
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service