Applications that access SQL Server databases should make extensive if not exclusive use of stored procedures for any statement, from a very simple one-row select to a complex cascaded delete. Applications that paste together SQL statements are more difficult to manage and result in less secure databases than applications that exclusively use stored procedures.
This article discusses facets of Microsoft SQL Server 7.0 textual searches such as: how SQL queries can be used on file systems lacking tables; how to use SQL extensions to make full-text queries; and how to work with a combination of file and database information. This article also discusses how BackOffice products (including: SQL Server distributed queries, Window NT Server's built-in Web Server, Internet Information Server (IIS), and Index Server 2.0) support textual searches in SQL Server 7.0
This is the second installment in an explanation of Database Design for Ultradev E-commerce application developers. It's based on my database experience (and all the mistakes I made along the way) with building E-commerce apps in Drumbeat 2000. I hope it's helpful
Author: Rick Curtis