We live in an age where expectations about technology are high. With the Internet, information is readily available. If a Web site is slow to load, we move on to another one; with so many sites to choose from, there is no need to wait for the poor performers. This impatient attitude also applies to accessing information within an organization. Individuals searching for information have a variety of sources to choose from, and they will pick the sources that can provide reliable, quick results. Generally, business intelligence (BI)/ad hoc query applications can provide users with information on demand. However, when a BI/ad hoc query application’s performance deteriorates, users grow impatient and seek other means to access the information they need. In this month’s column, I will discuss several components that can affect the BI/ad hoc query application’s performance.
Two primary technical architectures currently exist for BI/ad hoc query applications: full client (non-Web BI applications) and thin client (Web- enabled BI applications). (Please refer to Differences between Web and Non-Web Applications, March 2000.)
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access