Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence

Hello,

I am using the Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence to connect to SAP BW queries. I have tried looking for documentation on the connection string arguments but have not had much success. My question is this: How do you specify the connection timeout in the connection string:

Connection string example: DataSource=http://mySAPNetweaverBIServer:8000/sap/bw/xml/soap/xmla?sap-client=020

Cheers

Hi MMuffett,

Can u provide me the URL to get evaluation software of Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence.

Or from where do i get this ?

Thanks,

Anil

|||

Hi MMuffett,

I am using the Microsoft .NET Data Provider v1.0 for SAP mySAP Business Intelligence to connect to SAP BW queries.

I am not getting a success browser with xml code while doing the "Test Service in XMLA", its showing Bad Gateway error in browser

The link which is displayed on the address bar of browser is http://sapmdm.wipro.com:8000/sap/bw/xml/soap/xmla?sap-client=800.

The above link is used for the connection datasoure in Reporting services.

Can u pls suggest me what to do? what may be the problem, do we need to made some Middleware cofiguration settings? if yes then how?

Thanks in Advance

Anil

Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence

Hello,

I am using the Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence to connect to SAP BW queries. I have tried looking for documentation on the connection string arguments but have not had much success. My question is this: How do you specify the connection timeout in the connection string:

Connection string example: DataSource=http://mySAPNetweaverBIServer:8000/sap/bw/xml/soap/xmla?sap-client=020

Cheers

Hi MMuffett,

Can u provide me the URL to get evaluation software of Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence.

Or from where do i get this ?

Thanks,

Anil

|||

Hi MMuffett,

I am using the Microsoft .NET Data Provider v1.0 for SAP mySAP Business Intelligence to connect to SAP BW queries.

I am not getting a success browser with xml code while doing the "Test Service in XMLA", its showing Bad Gateway error in browser

The link which is displayed on the address bar of browser is http://sapmdm.wipro.com:8000/sap/bw/xml/soap/xmla?sap-client=800.

The above link is used for the connection datasoure in Reporting services.

Can u pls suggest me what to do? what may be the problem, do we need to made some Middleware cofiguration settings? if yes then how?

Thanks in Advance

Anil

Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence

Hello,

I am using the Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence to connect to SAP BW queries. I have tried looking for documentation on the connection string arguments but have not had much success. My question is this: How do you specify the connection timeout in the connection string:

Connection string example: DataSource=http://mySAPNetweaverBIServer:8000/sap/bw/xml/soap/xmla?sap-client=020

Cheers

Hi MMuffett,

Can u provide me the URL to get evaluation software of Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence.

Or from where do i get this ?

Thanks,

Anil

|||

Hi MMuffett,

I am using the Microsoft .NET Data Provider v1.0 for SAP mySAP Business Intelligence to connect to SAP BW queries.

I am not getting a success browser with xml code while doing the "Test Service in XMLA", its showing Bad Gateway error in browser

The link which is displayed on the address bar of browser is http://sapmdm.wipro.com:8000/sap/bw/xml/soap/xmla?sap-client=800.

The above link is used for the connection datasoure in Reporting services.

Can u pls suggest me what to do? what may be the problem, do we need to made some Middleware cofiguration settings? if yes then how?

Thanks in Advance

Anil

Mgs 8650:

When I switched to a multiple processor SQL Server 2000 machine, some of the
more complex queries produced this error
(http://support.microsoft.com/?kbid=837983):
Msg 8650:
Intra-query parallelism caused your server command (process ID #50) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
I had SP3a but the error still occured even with the MAXDOP 1 hint on the
query. The only resolution that worked was to set the "Use" processors = 1
on the properties. Does anyone know if SP4 has the resolution for this in
in?
DabHi David
There are 6 options to try in this article, did you try any of the others?
John
"David A. Beck" wrote:
> When I switched to a multiple processor SQL Server 2000 machine, some of the
> more complex queries produced this error
> (http://support.microsoft.com/?kbid=837983):
> Msg 8650:
> Intra-query parallelism caused your server command (process ID #50) to
> deadlock. Rerun the query without intra-query parallelism by using the query
> hint option (maxdop 1).
> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
> query. The only resolution that worked was to set the "Use" processors = 1
> on the properties. Does anyone know if SP4 has the resolution for this in
> in?
> Dab
>
>
>|||John,
All except re-writing the query. The hints (2 options) did not do anything.
The reason for my question is that I thought SP4 might negate the need for
option 1 (crippling the SP3+ parallel scan behavior). Running the query
again (as if I hadn't run it a zillion times) never works.General
performance tuning is just hit and miss.
MS has know about this problem for some time so I ask this question again,
does SP4 resolve the intra-query parallelism deadlock problem?
Dab
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D95D94BC-2149-4B32-9224-3A9DCDF6E0A3@.microsoft.com...
> Hi David
> There are 6 options to try in this article, did you try any of the others?
> John
> "David A. Beck" wrote:
>> When I switched to a multiple processor SQL Server 2000 machine, some of
>> the
>> more complex queries produced this error
>> (http://support.microsoft.com/?kbid=837983):
>> Msg 8650:
>> Intra-query parallelism caused your server command (process ID #50) to
>> deadlock. Rerun the query without intra-query parallelism by using the
>> query
>> hint option (maxdop 1).
>> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
>> query. The only resolution that worked was to set the "Use" processors =>> 1
>> on the properties. Does anyone know if SP4 has the resolution for this in
>> in?
>> Dab
>>
>>

Mgs 8650:

When I switched to a multiple processor SQL Server 2000 machine, some of the
more complex queries produced this error
(http://support.microsoft.com/?kbid=837983):
Msg 8650:
Intra-query parallelism caused your server command (process ID #50) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
I had SP3a but the error still occured even with the MAXDOP 1 hint on the
query. The only resolution that worked was to set the "Use" processors = 1
on the properties. Does anyone know if SP4 has the resolution for this in
in?
DabHi David
There are 6 options to try in this article, did you try any of the others?
John
"David A. Beck" wrote:

> When I switched to a multiple processor SQL Server 2000 machine, some of t
he
> more complex queries produced this error
> (http://support.microsoft.com/?kbid=837983):
> Msg 8650:
> Intra-query parallelism caused your server command (process ID #50) to
> deadlock. Rerun the query without intra-query parallelism by using the que
ry
> hint option (maxdop 1).
> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
> query. The only resolution that worked was to set the "Use" processors = 1
> on the properties. Does anyone know if SP4 has the resolution for this in
> in?
> Dab
>
>
>|||John,
All except re-writing the query. The hints (2 options) did not do anything.
The reason for my question is that I thought SP4 might negate the need for
option 1 (crippling the SP3+ parallel scan behavior). Running the query
again (as if I hadn't run it a zillion times) never works.General
performance tuning is just hit and miss.
MS has know about this problem for some time so I ask this question again,
does SP4 resolve the intra-query parallelism deadlock problem?
Dab
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D95D94BC-2149-4B32-9224-3A9DCDF6E0A3@.microsoft.com...[vbcol=seagreen]
> Hi David
> There are 6 options to try in this article, did you try any of the others?
> John
> "David A. Beck" wrote:
>

Mgs 8650:

When I switched to a multiple processor SQL Server 2000 machine, some of the
more complex queries produced this error
(http://support.microsoft.com/?kbid=837983):
Msg 8650:
Intra-query parallelism caused your server command (process ID #50) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
I had SP3a but the error still occured even with the MAXDOP 1 hint on the
query. The only resolution that worked was to set the "Use" processors = 1
on the properties. Does anyone know if SP4 has the resolution for this in
in?
Dab
Hi David
There are 6 options to try in this article, did you try any of the others?
John
"David A. Beck" wrote:

> When I switched to a multiple processor SQL Server 2000 machine, some of the
> more complex queries produced this error
> (http://support.microsoft.com/?kbid=837983):
> Msg 8650:
> Intra-query parallelism caused your server command (process ID #50) to
> deadlock. Rerun the query without intra-query parallelism by using the query
> hint option (maxdop 1).
> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
> query. The only resolution that worked was to set the "Use" processors = 1
> on the properties. Does anyone know if SP4 has the resolution for this in
> in?
> Dab
>
>
>
|||John,
All except re-writing the query. The hints (2 options) did not do anything.
The reason for my question is that I thought SP4 might negate the need for
option 1 (crippling the SP3+ parallel scan behavior). Running the query
again (as if I hadn't run it a zillion times) never works.General
performance tuning is just hit and miss.
MS has know about this problem for some time so I ask this question again,
does SP4 resolve the intra-query parallelism deadlock problem?
Dab
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D95D94BC-2149-4B32-9224-3A9DCDF6E0A3@.microsoft.com...[vbcol=seagreen]
> Hi David
> There are 6 options to try in this article, did you try any of the others?
> John
> "David A. Beck" wrote:

Message Queue

Hi, I have a question, I don't know if it is possible but I have an
application (.NET) that executes queries against SQL Server 2000. I have an
scenario where the database maybe is offline. I have been working with MSMQ
to communicate between apps and send messages from SQL Server but my question
is if SQL Server can read from the queue.
I want to send the query to a queue and when SQL is up again read from the
queue and process the queries, is this possible?
Thanks
Hi
You need to do that in code. SQL Server 2000 does not process against
message queues.
Regards
Mike
"Salvador" wrote:

> Hi, I have a question, I don't know if it is possible but I have an
> application (.NET) that executes queries against SQL Server 2000. I have an
> scenario where the database maybe is offline. I have been working with MSMQ
> to communicate between apps and send messages from SQL Server but my question
> is if SQL Server can read from the queue.
> I want to send the query to a queue and when SQL is up again read from the
> queue and process the queries, is this possible?
> Thanks
>

Message Queue

Hi, I have a question, I don't know if it is possible but I have an
application (.NET) that executes queries against SQL Server 2000. I have an
scenario where the database maybe is offline. I have been working with MSMQ
to communicate between apps and send messages from SQL Server but my question
is if SQL Server can read from the queue.
I want to send the query to a queue and when SQL is up again read from the
queue and process the queries, is this possible?
ThanksHi
You need to do that in code. SQL Server 2000 does not process against
message queues.
Regards
Mike
"Salvador" wrote:
> Hi, I have a question, I don't know if it is possible but I have an
> application (.NET) that executes queries against SQL Server 2000. I have an
> scenario where the database maybe is offline. I have been working with MSMQ
> to communicate between apps and send messages from SQL Server but my question
> is if SQL Server can read from the queue.
> I want to send the query to a queue and when SQL is up again read from the
> queue and process the queries, is this possible?
> Thanks
>

Message Queue

Hi, I have a question, I don't know if it is possible but I have an
application (.NET) that executes queries against SQL Server 2000. I have an
scenario where the database maybe is offline. I have been working with MSMQ
to communicate between apps and send messages from SQL Server but my questio
n
is if SQL Server can read from the queue.
I want to send the query to a queue and when SQL is up again read from the
queue and process the queries, is this possible?
ThanksHi
You need to do that in code. SQL Server 2000 does not process against
message queues.
Regards
Mike
"Salvador" wrote:

> Hi, I have a question, I don't know if it is possible but I have an
> application (.NET) that executes queries against SQL Server 2000. I have a
n
> scenario where the database maybe is offline. I have been working with MSM
Q
> to communicate between apps and send messages from SQL Server but my quest
ion
> is if SQL Server can read from the queue.
> I want to send the query to a queue and when SQL is up again read from the
> queue and process the queries, is this possible?
> Thanks
>