Issue |
EPJ Web of Conferences
Volume 68, 2014
ICASCE 2013 – International Conference on Advances Science and Contemporary Engineering
|
|
---|---|---|
Article Number | 00033 | |
Number of page(s) | 5 | |
DOI | https://doi.org/10.1051/epjconf/20146800033 | |
Published online | 28 March 2014 |
https://doi.org/10.1051/epjconf/20146800033
Evaluation of Sub Query Performance in SQL Server
1 School of Information System, Bina Nusantara University, Jl. K.H. Syahdan No. 9 Palmerah Jakarta 11480 Indonesia
2 School of Computer Science, Bina Nusantara University, Jl. Kebon Jeruk Raya No. 27, Jakarta Barat 11530 Indonesia
a e-mail: toktavia@binus.edu
b e-mail: surya.ss@binus.edu
Published online: 28 March 2014
The paper explores several sub query methods used in a query and their impact on the query performance. The study uses experimental approach to evaluate the performance of each sub query methods combined with indexing strategy. The sub query methods consist of in, exists, relational operator and relational operator combined with top operator. The experimental shows that using relational operator combined with indexing strategy in sub query has greater performance compared with using same method without indexing strategy and also other methods. In summary, for application that emphasized on the performance of retrieving data from database, it better to use relational operator combined with indexing strategy. This study is done on Microsoft SQL Server 2012.
Key words: Sub query / indexing / performance / SQL Server
© Owned by the authors, published by EDP Sciences, 2014
This is an Open Access article distributed under the terms of the Creative Commons Attribution License 2.0, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.