So, if I inderstand you correctly,...

Just make sure you do not perform any table scans after the morning run. Data that you dont read will never be loaded into RAM.

The data that you loaded in...

If you post the execution plan, table definitions, and index definitions it becomes much easier to help... 😉

I am not sure I understand exactly what you are trying to do, but I dont think it is possible to call a stored procedure for each row in a...

wmalik001 (5/20/2010)

---

Thanks for the link,

I already read that, but i first want to try reducing the max value,

so you are suggesting I should make it to 12gb that...

I agree. This seems strange. This could possibly be regarded as an optimizer bug.

Even this code gives an index scan:

DECLARE @v-2 INT=45

select * from BAR where smallid =...

wmalik001 (5/20/2010)

---

This is from the Data base logs:

05/20/2010 05:33:14,spid1s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds....

cgreathouse (5/20/2010)

---

The entire stored procedure takes ~450 ms. When I look at the actual execution plan in SMS, there are 7 queries in the batch and this 1 query...

Maybe table_name is a view that contains an expensive join or order by.

If table_name is really a table and there is no order by involved there should be no problems

So it seems that MacAfee and SQL server is fighting each other for the last bit of memory.

Either disable the antivirus or reduce max memory for SQL server.

How slow is this statement?

You say that it takes 100% of the query according to the execution plan, but how many ms is that ?

To see this exactly you could...

SQL Server itself should not cause any paging.

Paging is probably caused by other processes on the machine.

If paging is really a problem you can try to force SQL server to...

Sorry, I have no more ideas.

Maybe time to let Microsoft look at this?

Weird. Glad you found a solution. 🙂

Exactly how are you trying to shrink the files ?

Are you perhaps using the GUI ?

Try giving the command directly:

DBCC SHRINKFILE (filename,1)

Did that work ?

If not, what was the result...