Insufficient memory tu run this query

[fidel2k]

Hi there !! i newly on this i hope if any one could help me !!!

I have i report that have a lot of metrics about 20
an run fine when in the report options the join type is
inner join , but i wat to do this with outer type.
when i run the report its fails with err:

i dont think about the memory , becouse i ran other
query more bigger than its.


thanks in advance

FIdel

Report: RESUMEN INDICADORES

Status: Execution failed

Error: QueryEngine encountered error: Call SQLExecDirect got SQL_ERROR
[37000:701: on HSTMT] [Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient system memory to run this query.

Error in Process method of Component: QueryEngineServer, Project 5, Job 70, Error Code= -2147212544.


Starting Time: 11:27:58

 

[chael]

You have quite a few options here...

First, Try using 'page-by' on the report to restrict the number of rows returned to the desktop. To do this, drag an attribute up to the page-by field. This will reduce the number of rows returned to the client. You could also filter your report by some of the attribute elements....

The server has several settings that can be tweaked, i.e. max number of rows. Also, the SQL Server ODBC driver has its own settings that can be adjusted if the physical size of the query is too big.

What version of MSTR are you using?
Are you running everything off of one machine, or are the machines separated?

 

[fidel2k]

i will try to reduce the numbers of rows filtering,

about the MSTR version is 7.2.0 and run everthing in one machine.

Could you give me some kind of MSTR configuration?.

thanks.

P.S. Im having some problems to login to the page
could you send me CC to fsilva@gnm.com.mx

regards

 

[fidel2k]

its works filtering the report , for now i use i prompt
but i have i question.

If i increase the number of rows of a report this will work?


thanks cael

 

[nlim]

this looks like a SQL server error, actually. The following troubleshooting steps will verify it.

1) instead of running the report, view sql instead.
2) copy and paste the sql into another tool accessing sqlserver directly. maybe in SQLServer enterprise manager.

if the same error occurs it's a sqlserver problem, get your admin to tweak sqlserver.