February 9, 2011 at 6:33 am
Hi ,
Please help me..
I am strugling with one memory page out error -in sql server 2005 64 bit machine -- "Insufficent systmem memmory to run this query"
February 9, 2011 at 7:38 am
Post the query you're using and we'll see what we can see.
February 9, 2011 at 7:48 am
I am used below query
SELECT lims2.LOGIN.LOGINNUM
FROM lims2.LOGIN WITH (NOLOCK) INNER JOIN
lims2.USERS WITH (NOLOCK) ON lims2.LOGIN.REQUESTER_UID = lims2.USERS.PROFSID LEFT OUTER JOIN
lims2.TA_CloseOut WITH (NOLOCK) ON lims2.LOGIN.LOGINNUM = lims2.TA_CloseOut.LOGINNUM
WHERE (lims2.LOGIN.STAGE = 'COMPLETE') AND (lims2.LOGIN.COMPLETE_DATE > CONVERT(DATETIME, '2005-01-01 00:00:00', 102)) AND
(lims2.LOGIN.PRIORITYFLAG LIKE 'DVP%') AND (lims2.TA_CloseOut.CloseOutEmailSent IS NULL) AND (lims2.TA_CloseOut.CloseOutID IS NULL) AND
(lims2.LOGIN.IncludeInMetrics = 1) AND (LEN(lims2.LOGIN.REQUESTER_UID) < 9) AND (lims2.USERS.EMAIL LIKE '%testserver%' OR
lims2.USERS.EMAIL LIKE '%ach-llc%') AND (lims2.LOGIN.DIVISION = 'EX') AND (NOT (lims2.LOGIN.CHARGE_DEPT = '1239H910')) AND
(NOT (lims2.LOGIN.STATUS LIKE 'RFQ Only%')) AND (lims2.LOGIN.ImportedRequest = 0)
February 9, 2011 at 7:54 am
what is your SQL build numbers? there were bugs like this in some older builds
February 9, 2011 at 7:57 am
It looks like you've posted your question in the wrong forum. This forum is for backup related issues and your query doesn't look like it's saving backups or doing restores.
I'm going to ask Steve to move this to the T-SQL forum where you'll get more eyes on this thread, and hopefully the proper answer.
February 9, 2011 at 8:06 am
Just now saw the sql error log : " A significant part of sql server process memory has been paged out. This may result in performanence degradtion duration (30 )seconds
February 9, 2011 at 8:10 am
Are you seeing performance issues with any other processes, views, or queries?
EDIT: Are you using Query Designer?
February 9, 2011 at 8:18 am
solomon.jernas (2/9/2011)
Just now saw the sql error log : " A significant part of sql server process memory has been paged out. This may result in performanence degradtion duration (30 )seconds
i bet you don't have lock pages in memory set
February 9, 2011 at 8:22 am
I'm betting it's a QD problem. I've seen similar problems before and the query you presented us with looks exactly like it was "written" by Query Designer. QD just doesn't have the capacity to execute the high-volume queries.
Run the query in an open query window in SSMS, not Query Designer. Tell me what happens.
February 9, 2011 at 9:13 am
Lock Pages in Memory privilege must be enabled for the account that runs SQL Server.. is it correct .. any memory related problem
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply