on 12-31-2014 9:06 PM
Hi,
We are writing a Crystal report based on Oracle database. In Crystal designer lot of database fields are displaying wrong length compared to actual lengths defined in the database. Is there any reason for mismatch between Crystal and database? I have attached a screenshot of some fields from Crystal, Week_number is showing as 4000 characters length where as database side that field is 10 characters.
Is there any way we can make it real length in Crystal?
Thanks
Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhilash, I am using Oracle native driver to connect to the database from Crystal. I also have tried with connecting through ODBC connection but there also it's behaving like that.
Is this behavior(length mismatch) cause any performance related issues?
If we run the same report query on Toad it's taking ~10 minutes where as in Crystal it's around ~50 minutes!
Thanks
No, it's not been joined to another table. Report has few sub reports based on the same query but we are passing ID values to sub report from main report. Sub report query is fast in msecs with the filter based on that ID. Report shouldn't take 50 minutes.
I was just wondering, fields which are showing 4000 characters length in Crystal bringing any junk characters to report? Because database side they are just 8 characters.
Thanks!
Subreports could tremendously slow down a report - especially if they're placed on the Group Header/Footer or the Details Sections.
A Subreport sends as many queries to the database as there are Details/Group Sections (If that's where it's placed).
How long does the Main Report's query take when it is run separately as a different report - I'm pretty sure it would take around the same time as Toad.
-Abhilash
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.