Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My Server is Windows 2003 and SQL Server 2005 Standard. 3 GB of RAM. After run my client program for a while a Private Bytes up to 1.7 GB and never come down.
only process 51 with status “runnable”. Click details.
create table #tmpDBCCinputbuffer (
[Event Type] nvarchar(512),
[Parameters] int,
[EventInfo] nvarchar(512))
insert into #tmpDBCCinputbuffer exec ('DBCC INPUTBUFFER(51)')
select [Event Info] from #tmpDBCCinputbuffer
Call connections have been closed.
Any clue?
1.7GB is the 2GB (default) user mode address space less 384MB. SQL Server leaves the 384 MB by default.
If you had /3GB set and 3GB RAM, it would use 2.7GB.
See this article, KB 316749 which applies to SQL 7 through to SQL 2005. Oddly, I’ve not found this information anywhere else, even with SQL Server memory whitepapers. It’s easily reproducable though.