A way of buffering the Items-table ??
I'm having several report servers running at different locations.
Until now the table soring all reports was at a central database.
Problem is that there are already quite some repots in in with some
graphical stuff.
Meaning, the select on the table takes a while to get to each server.
As in these servers i'm using a TrsReportTemplateVolume, each time the
entiry table is opened.
As the datamodule is created quite often this slows down the report server.
Would it be wise to set this table on the main form of the server or
wouldn't that be thread-safe ??
Until now the table soring all reports was at a central database.
Problem is that there are already quite some repots in in with some
graphical stuff.
Meaning, the select on the table takes a while to get to each server.
As in these servers i'm using a TrsReportTemplateVolume, each time the
entiry table is opened.
As the datamodule is created quite often this slows down the report server.
Would it be wise to set this table on the main form of the server or
wouldn't that be thread-safe ??
This discussion has been closed.
Comments
It is my understanding that Datasets are not thread-safe.
One solution would be to convert to .rtm files.
--
Nard Moseley
Digital Metaphors Corporation
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
As i want to keep the reports centralized in one DB and distribute the
servers this would work by a share and is slower than the database.
On our wan we use a quality of service and the ports for windows networking
(135,136,137) are in the lowest level, 1433 (SqlServer) is in the highest.
I could work with replication of this table to several servers.
Thx
I will give it first a try with the RTM files, (and distribute them) this
might be faster al the datamodule will not open each report every time i
hope, but just take a direcory listing.