Re: OLAP Linked query - 8k limit

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I checked the MSOLAP properties & the 'In Process' option is enabled. I'm not
sure if there is any thing else we can do to overcome the 8k limit.

Thanks,

Venkat.

"Pascal Deliot" wrote:

IN or OUT of process is defined by OLEDB provider. This can be seen in
SSMS/Server/ServerObjects/LinkedServers/Providers/MSOLAP/Properties: "Allow
In process".

You can try to enable the "Allow In Process" for the MSOLAP provider, this
can help. But you can face other issue, as MSOALP provider is not supported
by Microsoft "InProcess".

IN process an OLEDB provider is loaded into the SQL Server process and
communicate with SQL Server using memory segement.
OUT of process an OLEDB provider is loaded outside the SQL Server process
and communicate with SQL using RPC with some limitations...

Pascal

"Prasad" <Prasad@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de
news:373408DF-E173-42CD-90D5-FF1B20F219F1@xxxxxxxxxxxxxxxx
How do i check this? InProcess.

Is this has anything to do the 8k limit for the OPENQUERY?

"Pascal Deliot" wrote:

Is you OLAP provider defined as "InProcess" ?

Pascal

"Prasad" <Prasad@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de
news:707C0DC9-EE31-4301-9B58-9A71348D2689@xxxxxxxxxxxxxxxx
We are using the Linked query to execute MDX statements but are having
issue
with 8k size limit of the statement.

Did any body have a work around for these so that we can pass bigger
MDX
statements?

Thanks,

Venkat.


.



Relevant Pages

  • Re: OLAP Linked query - 8k limit
    ... IN process an OLEDB provider is loaded into the SQL Server process and communicate with SQL Server using memory segement. ... OUT of process an OLEDB provider is loaded outside the SQL Server process and communicate with SQL using RPC with some limitations... ... > We are using the Linked query to execute MDX statements but are having ...
    (microsoft.public.sqlserver.olap)
  • Re: Strange error code for deadlock
    ... Since you are working through OLEDB provider, ... > I am currently writing an deadlock handler for our application (a COM ... > Having searched both ADO and SQL Server references, ... > error message to find "deadlock victim" for example); ...
    (microsoft.public.vb.database.ado)
  • Re: Does asynchronous operation supported by oledb provider for openquery?
    ... The result rowset is forward readonly and dynamic collumns. ... for OleDB Provider? ... If SQL Server use any of IDBAsynchStatus/IDBAsynchNotify ... stop populating and end rowset. ...
    (microsoft.public.sqlserver.programming)
  • Re: parameter names in Sql Server
    ... If you stick to the OLEDB provider you can use ... > query that can be used with both SQL Server and Oracle. ... > executed to make any necessary changes. ... >> character or something like this... ...
    (microsoft.public.data.ado)
  • Re: C# Windows Service Problem
    ... Note that connecting to SQL server and using DSO are ... I don't use an OLEDB provider anywhere in the program.. ... The error message refers to the OLEDB provider for DSO, ...
    (microsoft.public.dotnet.languages.csharp)