michael.buono Posted July 19, 2016 Share Posted July 19, 2016 What restrictions or best-practices should be adhered to when constructing a custom Domain? In other words: "How big is too big"? As long as it is manageable by a human, how much can the system handle? Questions I've considered:Number of joins?Number of Tables or Derived Tables?Number of Sets and Displayed Fields?Datasource type / technology limitations?Computer specification or powere needed? (client- or server-side)When will Views and Reports become unusable or unstable? Link to comment Share on other sites More sharing options...
Solution hozawa Posted July 20, 2016 Solution Share Posted July 20, 2016 I think it mostly depends on response time when using the domain. This depends on the server performance, network performance, and datasource performance. I personally don't recommend using domain because of memory usage and performance. I just create a new table using Jaspersoft ETL (Talend ETL) and use that because disk space is very cheap nowadays. Link to comment Share on other sites More sharing options...
michael.buono Posted July 22, 2016 Author Share Posted July 22, 2016 I should use Jaspersoft ETL to build a datasource, then point reports to that (instead of a Domain)? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now