Hi SQL Geeks, The Microsoft® SQL Server® 2012 Feature Pack is a collection of stand-alone packages which provide additional value for Microsoft® SQL Server® 2012. You can download the feature pack from here: http://www.microsoft.com/download/en/details.aspx?id=29065 Regards www.FaceBook.com/SQLServerGeeks
Read More
You can use DBCC SQLPERF statement to observe log space usage. For example; DBCC SQLPERF(LOGSPACE); GO Output: Database Name Log Size (MB) Log Space Used (%) Status ----------------------------------------------------- master 0.9921875 52.75591 0 tempdb 0.4921875 85.71429 0 model 0.4921875 80.95238 0 msdb 5.054688 15.37867 0 ReportServer$SQL2K8R2 6.742188 16.74392 0 ReportServer$SQL2K8R2TempDB 0.7421875 44.21053 0 AdventureWorks2008R2 1.992188 18.43137 0 AdventureWorksDW2008R2 1.992188 31.76471 ...
You can use DBCC SQLPERF statement to clear wait & latch stats. For example; -- clear the wait stats DBCC SQLPERF('sys.dm_os_wait_stats',CLEAR); You can use this statement to also clear latch stats. For example; -- clear the latch stats DBCC SQLPERF('sys.dm_os_latch_stats',CLEAR); If you like the tip, do like us on FaceBook at http://www.FaceBook.com/SQLServerGeeks @SQLServerGeeks
While apply Service Pack 2 update to a SQL Server 2008 instance, you might come across the following: This basically means that if fdhost.exe is stopped, than a reboot will not be required. Fdhost.exe is the Full Text Search Service and can be stopped from the Services Control Panel or from SQL Server configuration Manager.
DBCC PAGE is one of many undocumented and unsupported commands in SQL Server. However, it is safe to use it. It is widely used by SQL folks, Microsoft SQL engineers for troubleshooting purposes. For example; DBCC PAGE ('AdventureWorks', 1,300,1); The above command gives the complete hex dump along with slot array information of Page 300 from file 1 of AdventureWorks database. The last parameter is stands for output style and can have 4 possible values (0,1,2,3). If we change the last parameter t...
Lock escalation in SQL Server happens automatically when the number of Locks threshold is reached orthe memory threshold of the lock manager is reached. Locks are escalated from ROWS/PAGE to TABLEor PARTITION (if the table is partitioned and partition-level locking is enabled). However, lock escalation can be completely disabled using TRACE FLAG 1211. Use it wisely as it canimpact DB engine performance. TRACE FLAGS are mostly used to diagnose performance issues ! Alternatively, you can use TRACE...
In SQL Server 2008, lock escalation to Table object is default. You can make partition-level lock escalation as default as follows: ALTER TABLE [Table_Name] SET (LOCK_ESCALATION = AUTO); For more detailed explanation, see this: http://www.sqlservergeeks.com/articles/sql-server-bi/73/sql-server-2008-%E2%80%93-partition-level-locking Regards Quick Tip from SQLServerGeeks.com