
jayraj
jay
Get flash to fully experience Pearltrees
By Jonathan Kehayias, SQL Server MVP. You can view Jonathan’s blog at http://sqlblog.com/blogs/jonathan_kehayias/ . As SQL Server matures with time, the diagnostics tools available to administrators to troubleshoot problems when they arise have also matured.
Using SQL Server 2008 Extended Events
For those fighting with all the Extended Event terminology, let's step back and have a small overall introduction to Extended Events. This post will give you a simplified end to end view through some of the elements in Extended Events.
Introduction to Extended Events - Using SQL Server Extended Events
March 29, 2010 by pinaldave
Introduction to Extended Events – Finding Long Running Queries « Journey to SQLAuthority
http://msdn.microsoft.com/en-us/library/ms365393.aspx
The 64-bit versions of Microsoft Windows Server 2003 and Microsoft Windows XP can support more RAM than the 32-bit versions of these products.
How to determine the appropriate page file size for 64-bit versions of Windows
Understanding SQL server memory grant - Tips, Tricks, and Advice from the SQL Server Query Processing Team
This article describes how query memory grant works in Microsoft SQL Server.Page V: SQL Server Architecture
How to reduce paging of buffer pool memory in the 64-bit version of SQL Server
http://wtv.watchtechvideos.com/topic11.html
Free MCITP 70-450 Practice Test Questions - Accelerated Ideas
With Performance Data Collector in SQL Server 2008, you can now store performance data from a number of SQL Servers in one central location. This data is collected by a collection set on each server and stored in a shareable management data warehouse (MDW). Reports can be generated from this data using the built-in reports or generating your own with reporting Services.
SQL Server 2008: Performance Data Collector
Published: June 26, 2006 SQL Server Technical Article
Working with tempdb in SQL Server 2005
Help! My SQL Server Log File is too big!!!
Takeaway: Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim Chapman discusses the perils of not handling SQL Server log growth properly, and what can be done to correct the problems.When you use database mirroring in Microsoft SQL Server 2005, SQL Server automatically propagates any changes on the principal database to the mirror database. However, if you run the DBCC SHRINKDATABASE statement or the DBCC SHRINKFILE statements to shrink the principal database, the shrink operation is not duplicated on the mirror database. Database mirroring will change the physical file sizes only after a checkpoint.
The shrink operation is not duplicated on the mirror database when you use database mirroring in SQL Server 2005
The transaction log is used to guarantee the data integrity of the database and for data recovery. The topics in this section provide the information about the physical architecture of the transaction log. Understanding the physical architecture can improve your effectiveness in managing transaction logs.
Transaction Log Physical Architecture
Factors That Can Delay Log Truncation
Log truncation frees space in the log file for reuse by the transaction log.Pearltrees videos

