| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Want to get organized in 2022? Let Dokkio put your cloud files (Drive, Dropbox, and Slack and Gmail attachments) and documents (Google Docs, Sheets, and Notion) in order. Try Dokkio (from the makers of PBworks) for free. Available on the web, Mac, and Windows.

View
 

How to BLAST your Database — A Study of Stored Procedures for BLAST Searches

Page history last edited by Nathan T Suver 2 years, 10 months ago

Abstract: 

Abstract. Stored procedures are an important feature of all major database systems that allows to execute application logic within database servers. This paper reports on experiences to implement a popular scientific algorithm, the Basic Local Alignment Search Tool (BLAST), as stored procedures within a relational database. We implemented the un-gapped, nucleotide version of the BLAST algorithm with four different relational database engines, both commercial and open source. In an experimental evaluation, we compared our dbBLAST implementations with a standard file-based BLAST implementation from NCBI with regard to the implementation effort, runtime performance, and scalability. It shows that although our dbBLAST runs faster than the file-based BLAST program for short query sequences, all implementations lack scalability. However, the results also indicate that stored procedures require significant less development effort—both in time and space—than traditional programming approaches.

 

Biblio:

U. Röhm, T. M. Diep, "How to BLAST your database—A comparison study of stored procedures for BLAST searches", Proc. Int. Conf. Database Syst. Adv. Appl., pp. 807-816, 2006.

 

Key Content:

Authors used a combination of stored procedures and sql CLR to achieve results, noting the benefits of doing all the computations on one machine (no latency), the ease of coding.  They also noted that scalabilty became a problem for large datasets.   This is a good example of a very specific use case that illustrates both pros and cons nicely.

Comments (0)

You don't have permission to comment on this page.