September 24, 2007 at 9:29 am
you should be able to see what is using the pagefile - or have you done this already? I find some windows services use the page file constantly regardless of how much memory is allocated to the o/s. I haven't tried running a 64bit box with no pagefile - if you've ever had Tivoli on a box then welcome to excessive page requests.
I thin it's wrong to compare 32bit sql2000 and 64bit sql2005 - they're not the same.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
March 7, 2008 at 2:23 pm
Hi there, in SQL 2005, SQL Server Memory manager, target and total sever memory.
When first installed and did a few updates etc, the total server memory was 6 gig now did some routine tasks, restored 40 gig backup and dbcc checkdb it now up to 39 gig which is ok i have 64 gig memory.
I thought that in SQL 2005 that once its used the memory,
will not change the values in total server memory and this become lower. ...bascially telling me how much memory is in use at anyone time.
Thanks
March 10, 2008 at 7:35 am
Just my 2 cents.
If you set pagefile too small or worse disable it, the system will be slow regardless of ram size. On my comp with 2 GB ram the default pagefile was 603mb (huh), recommended 3gb, I wasn't satisfied with performance and turned it off. The system was a lot slower. When I changed the pagefile to recommended size, the system was snappy as expected. A friend mentioned a special registry setting, if you want it perform well without a pagefile, but didn't want to reveal it.
March 10, 2008 at 10:23 am
i created a separate thread so that not to interfere with your thread . Thank you.
oh im not sure if it created it so i continue here.
64 gig sql 2005 enterprise, lock pages in memory has been set
AWE is not set on SQL
Set Max memory in sql to 50 gig
physical memory 64 gig, available 64 gig
PF 1.34 gig
Ran DBCC CHECKDB on 40 gig
PF went up to 32 gig and available memory went down to 25 GIG.
I just wondering if (Even though you have told SQL to reserve physical memory and you have specified an amount of memory that is small enough to be all physical memory, the operating system is able to swap this out to the page file in certain situations.)
That the dbcc checkdb is one of them situations.
I was just wondering is this is correct that the PF increase is this great.
Thanks
March 10, 2008 at 3:32 pm
Hi there we on SQL 2005 64 Bit, configured the lock in memory pages on windows.
64 GIG
102 Page File
Enterprise Edition of SQL .
AWE is not flagged.
Available Memory 64 G
The Physical Memory was 64 GIG, Available was about the same. PF was 1.34 GIG.
So then I run one command in SQL DBCC CHECKDB 40 gig db
The Physical Memory Available goes to 25 GIG
Paging File goes to 38 GIG from 1.34 GIG.
This statement is from the thread 918483
After you restart the SQL Server service, all memory that is allocated for the buffer pool will be ineligible for paging by Windows.
So im a little confused why such a big PF that went from 1 gig to 38 GIG.
Any clairification be appreciated.
March 11, 2008 at 6:15 am
That much pagefile usage indicates a memory problem. If memory is set correctly you should only see a minimum amount of the pagefile being accessed. The main reason you would want to set a pagefile large for a database server as some Microsoft articles indicate is to be able to capture memory dumps, which to most people is useless unless you plan on sending the dump to Microsoft.
March 11, 2008 at 7:39 am
Brand new server nothing else running on it. No users. Should i do a memory diagnostics
March 11, 2008 at 7:55 am
Run DBCC Memorystatus to look for problems and run the Memory Consumption report.
March 11, 2008 at 10:59 am
MEMORYCLERK = SQLBUFFERPOOL
Allocated
1,544
virtual memory reserved 67,190,784
Committed 65,536
AWE 38,469,128
Only thing i see
Viewing 9 posts - 16 through 23 (of 23 total)
You must be logged in to reply to this topic. Login to reply