Robust Plan execution error?

I am running a select against a View that exceeds the max allowable row size and added OPTION (ROBUST PLAN) to the select to enable the select to return a result when the row size is a problem. The original view does a number of joins.

One of our users has reported that some data values they expect to see in some of the columns for specific rows are missing or incorrect. Could using the ROBUST PLAN hint cause this to occur?

Thanks,

ChrisRefer to this link (http://www.sql-server-performance.com/hints_query.asp) for tips on ROBUST PLAN and SQLMAG (http://www.sqlmag.com/forums/messageview.cfm?catid=9&threadid=15767) link for references.

Robust Plan

Folks,
I am getting the follwoing error:
"cannot sort a row of size 8192, which is greater than the allowable
maximum of 8094" .
Doing the research around the web, I found a solution which had be
using Option "Robust Plan" as a part of the query.
I am getting another error "Warning: The query processor could not
produce a query plan from the optimizer because the total length of all
the columns in the GROUP BY or ORDER BY clause exceeds 8000 bytes.
Resubmit your query without the ROBUST PLAN hint."
Am i missing something.
- JessHave you calculated how much bytes the arguments in the GROUP BY and/or
ORDER BY clause need? If it exceeds 8094 bytes, then it will simply not
work, regardless of the ROBUST PLAN option.
When in doubt, then please post the query and relevant DDL.
HTH,
Gert-Jan
Hess wrote:
> Folks,
> I am getting the follwoing error:
> "cannot sort a row of size 8192, which is greater than the allowable
> maximum of 8094" .
> Doing the research around the web, I found a solution which had be
> using Option "Robust Plan" as a part of the query.
> I am getting another error "Warning: The query processor could not
> produce a query plan from the optimizer because the total length of all
> the columns in the GROUP BY or ORDER BY clause exceeds 8000 bytes.
> Resubmit your query without the ROBUST PLAN hint."
> Am i missing something.
> - Jesssql

Robust Plan

Folks,
I am getting the follwoing error:
"cannot sort a row of size 8192, which is greater than the allowable
maximum of 8094" .
Doing the research around the web, I found a solution which had be
using Option "Robust Plan" as a part of the query.
I am getting another error "Warning: The query processor could not
produce a query plan from the optimizer because the total length of all
the columns in the GROUP BY or ORDER BY clause exceeds 8000 bytes.
Resubmit your query without the ROBUST PLAN hint."
Am i missing something.
- JessHave you calculated how much bytes the arguments in the GROUP BY and/or
ORDER BY clause need? If it exceeds 8094 bytes, then it will simply not
work, regardless of the ROBUST PLAN option.
When in doubt, then please post the query and relevant DDL.
HTH,
Gert-Jan
Hess wrote:
> Folks,
> I am getting the follwoing error:
> "cannot sort a row of size 8192, which is greater than the allowable
> maximum of 8094" .
> Doing the research around the web, I found a solution which had be
> using Option "Robust Plan" as a part of the query.
> I am getting another error "Warning: The query processor could not
> produce a query plan from the optimizer because the total length of all
> the columns in the GROUP BY or ORDER BY clause exceeds 8000 bytes.
> Resubmit your query without the ROBUST PLAN hint."
> Am i missing something.
> - Jess

Right and Bottom Margins

Hi,
I have a doubt in margins.
Setting Left margin, Top Margin and Body Size would be enough. Then why
Right and Bottom Margins.
PonnurangamI need more specific information about your situation before I can comment.
Could you post a sample RDL that demonstrates the behavior?
If a datasource is required , please make sure it works with one of the
common sample databases: Northwind, Pubs, or Adventure Works.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ponnurangam" <ponnurangam@.trellisys.net> wrote in message
news:er4VCjQrEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a doubt in margins.
> Setting Left margin, Top Margin and Body Size would be enough. Then why
> Right and Bottom Margins.
> Ponnurangam
>|||Hi Bruce,
I do not have any specific situation.
The reason why I posted this is, I have set Right and Bottom Margins to 0 to
all my reports.
Does this will affect my reports in any way.
I could not understand why we have to specify Right and Bottom Margins
because specifying Left, Top Margins and Body Size will provide you the
required layout.
Thanks
Ponnurangam
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
news:Oe7PrvVrEHA.3396@.tk2msftngp13.phx.gbl...
> I need more specific information about your situation before I can
comment.
> Could you post a sample RDL that demonstrates the behavior?
> If a datasource is required , please make sure it works with one of the
> common sample databases: Northwind, Pubs, or Adventure Works.
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Ponnurangam" <ponnurangam@.trellisys.net> wrote in message
> news:er4VCjQrEHA.1272@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > I have a doubt in margins.
> >
> > Setting Left margin, Top Margin and Body Size would be enough. Then why
> > Right and Bottom Margins.
> >
> > Ponnurangam
> >
> >
>sql