Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: SQL Server
Expertise: Beginner
May 30, 1997



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Using views to improve performance

We are building a Web-based interface for an existing database. We're using a SQL interpreter that runs the queries, then sends them to the server without the need for a client side plug-in. Some of the queries take up to 20 minutes to process. The largest table has more than 800,000 rows. Would a view table help the query's performance without slowing down the whole system? What is the deciding factor in using a view table?

Performance issues usually are very specific to the data involved, and are best decided using test runs. A view may be particularly useful if you use it to limit the rows that would be processed by a query.

For instance, a view that contains only the rows related to a particular topic would allow you to ask users to select a topic in advance of issuing their query. This would allow you to use the view rather than the base table, improving performance.

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date