Hi
With our configuration of the report, it takes 30 seconds to render it. I think it should be possible to do it faster.
I have one Date-Connection to a SQL-Server with 20 Datasources. One of the Datasource ist the "main"-source, what means, that all other sources relate on that source. The Parameter to call the report ist in the "main"-source.
Question:
If I render a Report, does Stimulsoft loads all datasets from the sources(20!) completly or does it first the relation to the the "main"-source and loads only the datasets that are used at the end?
If it's the first one, how could I do I better? I tried to handle it with a Parameter in the SQL statement, but with no success.
Thanks for all help.
low Performance
low Performance
Hello,
If we understood your problem correctly, then you can set the ConnectOnStart property to false for the data source and connect to a report only required data sources DataSource.Connect()
Thank you.
If we understood your problem correctly, then you can set the ConnectOnStart property to false for the data source and connect to a report only required data sources DataSource.Connect()
Thank you.
low Performance
hi
First of all, sorry for my bad english. I try to explain the problem as best as i can..
I've tried to set the ConnectOnStart to false. If I understand that correctly then the sources (false) don't show up in the report anymore.
Example:
Source 1: SQL-Table Member, Attributes: ID; Name; Adress; City
Source 2: SQL-Table Job, Attributes: ID; Job
Source 3: SQL-Table Salary, Attributes: ID; Salary
...
(it is not possible to merge all the sources to one source, it would be a too big table)
To open the report I use the parameter ID from the Source 1 (I call the report from a GIS). All other sources have a relation to source 1 with the attribute ID.
If I call the report, does the report loads every source (source 2, 3, ...) completly and filters the datasets in a second step because of the realtion to source 1? Or should I adjust my SQL-statement where I define my source 2 like: "select * from Job where ID like Member.ID" or something like that?
First of all, sorry for my bad english. I try to explain the problem as best as i can..
I've tried to set the ConnectOnStart to false. If I understand that correctly then the sources (false) don't show up in the report anymore.
Example:
Source 1: SQL-Table Member, Attributes: ID; Name; Adress; City
Source 2: SQL-Table Job, Attributes: ID; Job
Source 3: SQL-Table Salary, Attributes: ID; Salary
...
(it is not possible to merge all the sources to one source, it would be a too big table)
To open the report I use the parameter ID from the Source 1 (I call the report from a GIS). All other sources have a relation to source 1 with the attribute ID.
If I call the report, does the report loads every source (source 2, 3, ...) completly and filters the datasets in a second step because of the realtion to source 1? Or should I adjust my SQL-statement where I define my source 2 like: "select * from Job where ID like Member.ID" or something like that?
low Performance
Hello,
If we understood your problem correctly, as a way, you can merge these 3 data sources in one query and apply the filter to this query.
Thank you.
If we understood your problem correctly, as a way, you can merge these 3 data sources in one query and apply the filter to this query.
Thank you.
low Performance
Hello Bud!
best regards
Your assumption is correct. If you use relations then every source is loaded and the filters are applied afterwards.If I call the report, does the report loads every source (source 2, 3, ...) completly and filters the datasets in a second step because of the realtion to source 1?
Yes, if you adjust your statement like mentioned above, you will increase performance significantly.Or should I adjust my SQL-statement where I define my source 2 like: "select * from Job where ID like Member.ID" or something like that?
best regards