Report Server and Maria DB

[Serguei]

I am new to the product and trying to overcome basic hurdle - connect to DB from within Report Designer

Sorry if it was discussed already but I only can find very old threads on the subject and one of the videos on the steps is using Adobe Flash which is dead now.
Any help is appreciated

===

Maria DB 10.4 is installed on the same machine as Report Server
ODBC Drivers both 32 and 64 deployed to both server and my desktop machine

Telerik Data Direct is not being used as it does not have support of Maria DB, only mySQL.
I have tested ODBC access both remote and on the server from ODBC Manager and it is working
Data Connection "my-server" is added on Report Server and looks like this

DRIVER={MariaDB ODBC 3.1
Driver};TCPIP=1;SERVER=server-name;UID=*********;PWD=********;DATABASE=******;PORT=3309;OPTIONS=4194384;

it is unfortunate that there is no action on the portal to test it from UI, but may be it is done automatically, hard to say

When in Report Designer using SQL Data Source I can see existing data connection listed as "server:/http://server-name:83/my-server" but when I try to execute simple select statement (ex: select * from my_table; ) in next step I am getting

"An error has occurred. Parameter information cannot be retrieved: The query parameters cannot be obtained...."

followed by empty screens and more errors.

In documentation there is a reference to https://docs.telerik.com/reporting/sqldatasource but content is convoluted to read and figure out what is missing.

are there additional steps which need to be taken for Report Server to work out of the box?

[Todor]

Hello Serguei,

Thank you for your interest in our product.

Let me clarify that the SqlDataSource utilizes the specified ADO.NET provider/ODBC driver to establish the connection to the database and fetch the schema and execute the specified Stored Procedure or query. The observed error is also thrown by the data provider and transferred to the user by our code. I'm afraid I am not familiar with MariaDB. However, I suspect that the observed issue can be related to the provider/driver that you use. Can you test with an alternative ADO.NET provider/ODBC driver?

For example, we are aware, based on previous reports from our clients, that MariaDB (10.3.17) stored procedure can be successfully executed through MySQL data provider in the Standalone designer.

Regards,
Todor
Progress Telerik

[Serguei]

here is my confusion with the designer logic
when I am in "configure data source" dialog > Build new data connection > ODBC data provider > Build > use user or system data source > select existing odbc source I already set and tested through Window's odbc manager > provided user/password and Test Connection - I will get that connection is successful
I say Ok and go back to data source configuration dialog it then test connection itself and errors out that Data source name not found and no default driver specified

Connection String looks like "Dsn=<dsn_name>;uid=<user>;pwd=<password>"

Why it succeeds in testing the connection in the builder but fails reestablish the connection once back to configurator? Would not be using the same logic?

[Todor]

Hello Serguei,

When you create a new ODBC connection in the Standalone Report Designer, it gets created locally, on the user machine. It is not related to the Report Server even if the latter is installed on the same machine. Note that if you save the connection, it will appear with the prefix 'local:/'.

You need to configure the data connection in the Report Server and select it in the Standalone designer that is connected with the Report Server. The server connections appear with the prefix 'server:/' in the SqlDataSource wizard - see the linked screenshot for clarity.

Generally, the logic in the connection builder and the SqlDataSource wizard is the same. However, the builder only tests whether the connection is opened successfully. It doesn't check for permissions and doesn't make any queries to the databases. For that reason, a successful connection test doesn't guarantee that a particular query will be executed successfully.

Regards,
Todor
Progress Telerik