What are your index_id and page_count values?

They might be heaps or cointains very few pages. You could look for a better script that ignores heaps and small tables.

colin.Leversuch-Roberts (6/3/2011)

---

sorry I disagree, on a x64 system with 64GB of ram allocating 60GB to sql server is too much. The allocated memory is only for data cache it does...

It is advised. This may help you.

http://www.sqlservercentral.com/blogs/glennberry/archive/2009/10/29/suggested-max-memory-settings-for-sql-server-2005_2F00_2008.aspx

SELECT name, type, type_desc FROM master.sys.server_principals

..or something

You didn't mention your SQL Server edition in one of your previous posts ...

1. In this case what will be the maximum memory used by SQL Server .?

I believe 2GB....

What edition of SQL Server/OS?

As advised above you can set it to 1000.

and p.page_count >= 10

why 10? should be a lot higher value.

Did you enable lock pages in memory?

oh yeah, sorry thats ~22GB 🙂

http://www.connectionstrings.com/%5B/url%5D

Oh yeah. By the way, I did...

thought it was 4 and express supports only 1.. :unsure:

Not an answer to my question but it is helpful anyways. thanks.

SQLkiwi,

What if I only can see:

Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only....

I'm not an expert but would probably start with Performance Monitor first and once you figured which counter is causing issues then focus on that and start profiler.

Also download...