Hi!

I'm using Visual Studio 2005 + MSSQL Developer edition 2005 (SP1) +
WinXP (SP2).

I'm experiencing this major problem. Whenever SQL Server Management
Studio (SSMS) is started, the execution of ASP .NET application
drastically slows down.

Nornally the app takes less than a second to present any information.
But when I start SSMS, each request (that queries a database also) is
slowed down to about 25 seconds. Application becomes totally unusable.
If SSMS is shut down, the app performance get back to normal,
immediatelly.

I've been using this configuration for last 14 days and ever since the
first installation of SQL 2005 I'm encouontering these problems. It
happens very rarely that all the tools together run normally.

I've done some test on Errors with the Profiler and found out that with
every postback there is a warning issued. Simultaneously when this
warning is traced by the profiler the page is presented to the web
browser: so there's deffinitelly link to the problem but i don't know
how to solve it out! This is the warning:

<MemoryGrants
xmlns='http://schemas.microsoft.com/sqlserver/2004/07/queryprocessor'
Version='1.0' Build='9.00.2047.00'>
    <Grant>
        <SPID>63</SPID>
        <BatchId>0</BatchId>
        <SQLHandle>0x030007004BA83434E8CB1D019C9600000100000000000000</SQLHandle>
        <PlanHandle>0x050007004BA83434B8819B10000000000000000000000000</PlanHandle>
        <MemoryRequested>128</MemoryRequested>
        <MemoryGranted>0</MemoryGranted>
        <MemoryUsed>0</MemoryUsed>
        <DOP>0</DOP>
        <TimeOutInMS>25000</TimeOutInMS>
        <MemoryRequestTime>2006-04-27 17:55:09.26</MemoryRequestTime>
        <MemoryGrantTime></MemoryGrantTime>
    </Grant>
</MemoryGrants>

I've been searching through web a lot and haven't find any solution so
this is my last hope.

Thanks in advance for your help! Regards,

(uba***@gmail.com) writes:
And all this runs on the same box? How much memory do you have?

I've noticed myself, that response time from SQL 2005 can be amazingly
big for simple queries against Northwind. At that point I had 1 GB of
memory, a virtual machine running, Mgmt Studio running, Opera and Mozilla
running, one SQL 2000 instance and one SQL 2005 instance.

Since then I've bought one more 1GB or memory, and I have not seen these
problems.

My conclusion is that SQL 2005 becomes real slow when it gets short of
memory, but I have not looked at in detail. But the warning about
MemoryGrants that you included in your post, indicates that memory is
the problem.

See your local hardware vendor, or scale out SQL Server on a second
machine.

What's the best way to keep a live db and an archive db?
SQL 2005 Flat File source (in Import wizard) missing
run Profiler on a specific SP/Query/Function
Need Help with "System.Data.SqlClient.Sqlerror: Cannot open backup device (DLT tape) ...
SQL Server Profiler