Service pack 1 for SQL Server 2012 has been released on 9th Nov 2012. It took couple of weeks for me to install it in our servers. Before I settle down I got another notification from Microsoft that Cumulative Update 1 has been released for SP1. So I started analyzing what they missed major in SP1 and finally I found a article by Aaron.
Performance dashboard is developed for SQL Server 2005 which provides useful information about the server, in simple it will give you an performance overview of entire SQL Server. If you worked with SQL Server 2005 then you might be familiar with this tool. Unfortunately they didn’t provide or updated the tool to work with SQL Server 2008\R2, however based on user request we have done an workaround to make SQL 2005 reports to work with SQL 2008\R2. The good news is now MS have upgraded performance dashboard to SQL Server 2012 which now includes extended event trace details.
Hope you guys are getting ready for Diwali Festival :-). Before you guys start with the festival event I thought of writing an article on performance. Couple of days ago one of the developer came to me and said he was using an INNER join in his query and he is getting delay in results, soon after he changes it to LEFT OUTER join he could see some improvement in getting the results. I was blinking for a second and I started arguing with him that this will change the business logic & asked him to explain me how’s OUTER join faster so we went into an argument which resulted in this article.
DTA stands for Database Tuning Advisor which has introduced from SQL Server 2005. This utility helps the end user to tune their query and give them suggestions for better performance. It takes T-SQL query or profiler trace as workload, based on this it will analyze and give you the recommendation. Now in SQL Server 2012 it has been extended to include plan cache as workload, which means now you can directly point your db plan cache for analysis.
Yesterday we saw the trace flag 1204 which will give you the information based on nodes. Today we are going to get similar deadlock information using trace flag 1222 in XML like format which means the format does not conform to an XML Schema Definition (XSD) schema. After you enable the trace flag when an deadlock happens it will pushes the information to errorlog you can get the deadlock information from errorlog .