Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Reports & Microsoft SQL Server 2012 Express LocalDB support policy

Hello,

Willing to move some databases into Microsoft SQL Server 2012 (2014) Express LocalDB, I have tryed to map some reports on that database.

Using OLE DB SQL Native Client (v11) and SAP CR RunTime SP10 (>SP9), I still have trouble when using this data source:

After drawing some simple reports (standard ones with 2-3 fields from the database):

- VS designer:

+ when "checking database" or "getting a preview" of the report, it always complains about missing tables.

+ when trying to "re-map" tables from one SQL Server 2012 Express LocalDB to another one it fails, complaining about not findind resources.

- Running application (.NET 4.0, 32 or 64-bits):

+ without any change to the report configuration: CR Viewer complains with multiple error codes (17, ...) that it cannot find the tables

+ trying to change the configured database from the report: CR VIewer complains with some more error codes

=> Is Microsoft SQL Server 2012 Express LocalDB now officially supported by CR ?

=> Is changing datasource/database configuraton during execution now officially supported by CR ?

Feel free to provide an any links / howto's / white paper about how managing Microsoft SQL Server 2012 Express LocalDB with SAP CR !

Many thanks in advance.

Regards.

Tags:
Former Member
replied

In CR Designer here how to:

Create a new report and the Database Wizard pop's up:

Select the SQL Native 11 client:

Fill in the info:

DO NOT select the MDF file, you should see your database name:

Or check on the Integrated Security, SQL Express must be configure to accept your local Domain name or pre-configured user name.

Then drill down to your Table:

And add it.

Now when you look at the connection properties you see this:

So this is the ONLY way CR will work. Doesn't matter what MS says on how to connect, this is how CR must connect. You can't specify the MDF file.

As you can see the initial catalog is the table name and not the MDF file.

Looking at your report the table name is Articles, it's not listed in your connection so check permissions, the user you are connecting with does not have rights to access that table.

Log in using the SQL Administrator account, that should work and don't use trusted for now.

Issue appears to be a permission problem since the User name and PW are grayed out: and you can't see Articles listed.

Don

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question