Skip to main content

MS SQL Server Query Performance

Our company have a rather complex add-in to Project Server. For some time we have been struggling with performance issues and no matter how much we tuned the SQL procedures, after some time they would always become slow in a production environment. 

Today I came across a tool in SQL Server Management Studio which very easily can pinpoint which queries are running slow. In our case we discovered that one query was very slow and slowed all other queries.
This tool is called Activity Monitor and is build into most versions of Management Studio.
Note: Activity Monitor requires SysAdmin permissions to be used.


The tool is very simple to use. Simply open SQL Server Management Studio and connect to your database.

  Click on the Activity Monitor icon.

Here you will see a number of sections showing different information about the server.  Overview shows IO, wait time, etc. Processes shows information about which processes/connections is using the server. Resources Waits can tell you where a potential bottleneck is. Data File I/O is shows which databases is using a lot of IO.

However, the one I find really interesting is the "Recent Expensive Queries". This tells you which queries are running slowly. The database, average process time, etc.
In a production environment it was very easy to pinpoint where our problem was.
Only regret is, we did not know about this tool earlier.


Comments

Popular posts from this blog

Azure DevOps - Gantt Chart

It's been a while since my last post - in the past couple of weeks I have played around with some videos of topics I find interesting. One of these topics are a very cool way of displaying a Gantt Chart upon your Azure DevOps board's. Check it out here!

Project Server - Change field name on PDP for standard fields (like the Owner field)

Project Server - Change owner field name on PDP The field names on the PDPs (Project Detail Pages) has been preselected on the standard fields for a project. If you want to change the Owner to something else it is quite difficult. In the following i will explain how we can change this field through the Content Editor webpart. To change the owner field add a Content Editor webpart to the PDP page where the field is inserted. Select the webpart and from the ribbon select HTML->Edit HTML Source. Copy/Paste the following code into the Content Editor webpart. < script type ="text/javascript">     var old_name = "Owner" ;     var new_name = "Ansvarlig" ;     var ttnA = document.getElementsByTagName( "div" );     for ( var j = 0; j < ttnA.length; j++) {         var orig = ttnA[j].innerHTML;         var stripped = orig.replace( /^\s*/ , "" ).replace( /\s*$/ , &quo

PowerShell results size unlimited/truncated - $FormatEnumerationLimit/Width

Ever experienced the problem where you run a Powershell command and you cannot see the whole result because the result is truncated. Problem: If you for example run the Test-SPsite command you might see something like the following: Site : SPSite Url=http://atlas/pwa Results : { SPSiteHealthResult Status=Passed RuleName="Conflicting Content Types" RuleId=befe203b-a8c0-48c2-b5f0-27c10f9e1622, SPSiteHealthResult Status=FailedWarning RuleName="Customized Files" RuleId=cd839b0d-9707-4950-8fac-f306cb920f6c, SPSiteHealthResult Status=Passed RuleName="Missing Galleries" RuleId=ee967197-ccbe-4c00-88e4-e6fab81145e1, SPSiteHealthResult Status=Passed RuleName="Missing Parent Content Types" RuleId=a9a6769f-7289-4b9f-ae7f-5db4b997d284, SPSiteHealthResult Status=FailedError RuleName="Missing Site Templates" RuleId=5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd,