I've got a large amount of reports that I generate on a monthly basis. As it currently stands, it is clunky, large, and takes a while to process. It's actually about 90 reports, each Report makes a page in the actual report I present to management. It's a portfolio report that shows asset counts/balances/totals for each region/division/asset status. Most reports have a coinciding pie chart/graph representing the numerical data at the bottom.
Currently this is calculated through a myriad of queries for each region/division/status. For instance, the report that shows Count, Balance, and Percentage of Portfolio has a query for each chart and a subreport to show the amounts/totals below.
I'm investigating a rebuild of this database. All of the data that is pulled into the reports originates in a single table that is an export from our primary database. It's basically the entire portfolio. It is a increasingly large table with a date stamp field at the end to show which month each line corresponds to and is currently 246,000 records.
this database is not multi-user, I'm really the only person who uses it. It doesn't have to have a fancy front end or anything like that. I'm mainly interested in different ways of reducing the number of reports/queries needed to build this 90 page monstrocity.
Any suggestions?
Currently this is calculated through a myriad of queries for each region/division/status. For instance, the report that shows Count, Balance, and Percentage of Portfolio has a query for each chart and a subreport to show the amounts/totals below.
I'm investigating a rebuild of this database. All of the data that is pulled into the reports originates in a single table that is an export from our primary database. It's basically the entire portfolio. It is a increasingly large table with a date stamp field at the end to show which month each line corresponds to and is currently 246,000 records.
this database is not multi-user, I'm really the only person who uses it. It doesn't have to have a fancy front end or anything like that. I'm mainly interested in different ways of reducing the number of reports/queries needed to build this 90 page monstrocity.
Any suggestions?