Evaluation: Problem switching OleDB from Oracle to SQL Server

Stimulsoft Reports.NET discussion
Post Reply
paubne
Posts: 12
Joined: Sun Sep 16, 2007 7:24 pm
Location: Brisbane, Australia

Evaluation: Problem switching OleDB from Oracle to SQL Server

Post by paubne »

Hi

I am currently evaluating StimulReports as the potential future platform for my company's reporting products.
So far I am very impressed with the power and functionality; however I seem to have run into a fairly critical problem which must be resolved in order for us to move to StimulReports.

My company supports both Oracle and SQL Server, and as such we need to be able to write a report once and be able to run it on either database platform.
Working in Designer, I can set up the oledb connection connecting to say a SQL Server database, define a simply query with no parameters as the datasource, and preview the report - the results display fine.
However if I then change the connection string of the oledb connection to an Oracle provider, with no changing the data source or anything else, the preview shows nothing.
Interestingly if I try the "View Data" option on the datasource after changing the connection string, I can see the data fine.
So the preview has got an issue I think.

This happens whether I start with an Oracle oledb connection or if I start with SQL Server connection, and then try switch the connection string.

I have also tried using a wrapper program to dynamically set the database connection, with the same result when I try using a different database.
I used this code found in the documentation:

Code: Select all

rep.Dictionary.Databases.Clear();
rep.Dictionary.Databases.Add(new StiOleDbDatabase("oleDBConnection", connString));
Can anyone from StimulSoft help with this?



paubne
Posts: 12
Joined: Sun Sep 16, 2007 7:24 pm
Location: Brisbane, Australia

Evaluation: Problem switching OleDB from Oracle to SQL Server

Post by paubne »

Hi again

I think I have traced the problem to case sensitivity on the Name in Source property of each datasource column.
Basically my SQL Server column names are mainly all lower case, whereas the same table in my Oracle database has all uppercase column names.
So when I define the datasource initially, all the columns are created using the specific case of the column as defined in the database.
Then when I switch to the other database, the Name in Source property remains in the previous database's case, and the query seems to fail at runtime/preview.

This is a strange problem though, in that the View Data command works fine with the query - but the preview and report rendering doesn't.
Is there a bug fix for this? Seems like somewhere in your previewer/render code, the property in question is not taking case insensitivity into account.

Obviously I do not want to go through changing one of my database platform schemas to be in line in terms of case of column names.
Edward
Posts: 2913
Joined: Fri Jun 09, 2006 4:02 am

Evaluation: Problem switching OleDB from Oracle to SQL Server

Post by Edward »

The issue is confirmed. We need time to analyze the situation with the NameInSource.

We will inform you about results of our investigations in this topic.

Thank you.
paubne
Posts: 12
Joined: Sun Sep 16, 2007 7:24 pm
Location: Brisbane, Australia

Evaluation: Problem switching OleDB from Oracle to SQL Server

Post by paubne »

Great thanks. As mentioned before your product seems to fit our requirements perfectly otherwise.

FYI, I am working around this issue at present by aliasing all my Oracle columns to their SQL Server case-sensitive equivalent, thus maintaining a consistent Name in Source property.
eg. Column named "authuser" in SQL Server is AUTHUSER in Oracle.
I construct select statement in DataSource as: select authuser as "authuser" from xyz

The above approach works fine with SQL Server and Oracle, but of course is tedious since I have to be careful to alias all columns selected.

Looking forward to your resolution of this :)
Edward
Posts: 2913
Joined: Fri Jun 09, 2006 4:02 am

Evaluation: Problem switching OleDB from Oracle to SQL Server

Post by Edward »

Thank you very much for your tip.

The issue is resolved in the build from September, 18.

Thank you.
paubne
Posts: 12
Joined: Sun Sep 16, 2007 7:24 pm
Location: Brisbane, Australia

Evaluation: Problem switching OleDB from Oracle to SQL Server

Post by paubne »

Thanks for the quick turn around on this - very impressive.

I have verified that the issue is resolved.

My purchase order for licences will be going through shortly. Keep up the great work on this product.
Edward
Posts: 2913
Joined: Fri Jun 09, 2006 4:02 am

Evaluation: Problem switching OleDB from Oracle to SQL Server

Post by Edward »

Thank you very much for the good words.

Let us know if you need any help.

Thank you.
Post Reply