Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-08-28 : 08:40:35
|
| Jamil Sarraf writes "The question is simpleWe are using MS-SQL2000 as the DB behind our ASP project. So far we have interacted with the DB in diffrent ways. Something we call Stored procedures, some othertimes we construct our query (especially the where clause) based on user input and then we execute it with a command object.execute or a connection object.execute.....Recently we come across this statement. "We should only use stored procedures to access the DB", but we could not have enough information to accept or reject this statement. While I personally lean toward using stored procedures whenever I can, I still can not justify bounding myself, especillay when my user is offered to enter any of a 15 keys to filter the result he/she wants to see. The resulting query will be contructed based on the user input.Any advise in this area please. What advantages and disadvantages would the over-all usage of stored procedures have on my application.Thanks" |
|
|
|
|
|
Stored Procedures