We are trying to build new reports against our SAP BW system. Versions SAP BW 7.01 - SP5 Reporting Services 2008 R2 Report Builder 3 using the SAP Netweaver Bi connector When we run the reports we notice that the report is generating mulitple connection in SAP.. connections are generate are found using SM04, the number of connections appears to be tied to the number of columns. A single simple report could generate 10 connections in BW. Due to the number of connections and length of time it takes for these connections to drop off SM04 after the report runs these reports will cause problems if we release them in production. Is there a way to limit the number of connections a report generates in SAP BW?

Hi Riley, We are looking into your question and will respond as soon as possible. Thank you, Cathy Miller Microsoft Online Community Support

Hello, We have seen this issue in Reporting Services 2005 SP2 and should be fixed in build 9.00.3239, 2005 SP2 CU7. Can you please double check on the reporting services version? What is the visual studio (BI) environment you are using to build the report/test the report? Are you creating the report directly in Report Builder 3? Here is the reference KB: http://support.microsoft.com/kb/951186/ CAUSE This problem occurs because the server does not reuse the session when you run the report. Hope this helps. Thanks.Terrell An -MSFT

Morning.. Below are the release levels of the Reporting services and BW instance. Reporting Services SS 2008 R2 Reporting Services database 10.50.1600 SAP BW SQL Server database 10.0.2531 The reports were built using Report Builder 3. I will get with the develper and test using the BIDS 08 version to see if that makes a difference and will let you. She does not have that version of BIDS installed. Thanks for the KB link and the reply. Riley

We created a new report using Bids 08. We found the same problem of mulitple connection existed, so how you build the report does not matter either reports creates mulitple connection in SAP. We have applied an the lastest support pack to the BW system and have retested the report and we are still finding the problem exist. I have been working with Microsoft support but not getting anywhere there.

We found a solution to what was causing the multiple connections. We added to the connection string sap-client to the end of the datasource connection string. Example of old connection string Data Source=https://sap8:8000/sap/bw/xml/soap/xmla New connection string. Data Source=https://sap8:8000/sap/bw/xml/soap/xmla?sap-client=100 In the the tech doc http://msdn.microsoft.com/en-us/library/cc974473(SQL.100).aspx it lists this as optional .. but really should be used. Paragraph from tech doc. You can optionally provide an SAP BW client number and language in this editor. If you are using an SSO URL then you must specify a client number and language in the editor. Otherwise you may receive errors opening a connection to the SAP server. The language you choose corresponds to the sap-language parameter for SAP, and the client you choose corresponds to sap-client. The language entry can be a one-character SAP language specification or a two-character ISO 639 language specification. If you do not specify a client number or language, the server uses the default value configured on the server. After specifying your connection properties, you can test the connection by pressing Test Connection. Once a connection can successfully be established, you can optionally pick a specific catalog to associate with the connection.