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

Install DLL in GAC - Windows 2008/2012 (Using Powershell, No GacUtil.exe)

If you want to install a DLL in the GAC and do not have the GACUtil.exe available. Powershell is properly the easiest way to procede.

Before Powershell you would properly just drag the DLL file into the C:\Windows\Assembly but this option is usually not available anymore.

Powershell - Add DLL to GAC So to install a DLL file in the GAC simply execute the below Powershell script. Remember you migth want to run the Powershell prompt as an administrator.
[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")$publish=New-ObjectSystem.EnterpriseServices.Internal.Publish$publish.GacInstall("c:\temp\MyDllFile.dll")iisreset
The first line adds a reference to the assembly we need to be able to mange the GAC.
The second and third lines retrives the GAC object and publish a new DLL file to it.
The last line resets the Internet Information Services. This is only needed if your DLL file is used in a websi…

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.


My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site

SharePoint 2013 : Cannot connect to the targeted site.

On my Contoso environment I was trying to create a sandboxed solution. I have already configured my app domain and app management services. But when I tried to validate the site I got the following error message.
Error

Cannot connect to the targeted site. This error can occur if the specified site is not hosted on the local system. SharePoint solutions work only with locally-installed versions of SharePoint Foundation or SharePoint Server. Remote development is supported only for apps for SharePoint 2013.
If you search around the internet you will find many people suggesting to change your host file from 127.0.0.1 to the actual IP.

Solution However the solution, at least on a Contoso environment, is to type in the actual IP address in the host file.
(the IP 192.168.150.1 is the special IP for Contoso, I have 2 network adapters)
And do not forget to clear/flush the DNS cache. Now the solution can be created and validates.