In this section:
It is important to ensure that databases are fully optimized for best performance. Databases vary in terms of optimization and tuning parameters. Common database optimization options include:
The amount of data stored in a database can vary tremendously and can impact performance depending on how it is stored. You need to account for the volume of data in the database and the answer sets that need to be returned.
The physical location of the data directly impacts performance depending on the speed of the network, network availability, and network distance. Understanding data movement and the frequency of data movement is important. For example, if data is moved from an EDW to a data mart, how often does the data get updated and how will this affect reports? How are user expectations set and managed?
Data movement may impact:
Users must be notified of the frequency of data updates so they expect differences in report output when reports are executed at different times. For instance, if data is moved from an EDW to one or more data marts every hour, reports accessing the data marts will produce different report output at different times during the day.
A published schedule available on the Dashboard or on a SharePoint site are some of the ways to keep users aware of data updates and any changes that may be scheduled on the database. This information can also be accessed from a customized portal sign-in page, where a link can be added to the ETL schedule and other information regarding data updates and changes.