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 |
|
OwnedByTheMan
Starting Member
35 Posts |
 Posted - 2001-01-17 : 02:44:10
|
| I have spent most of the last 2 days trying to suck up as much information as I can regarding SQL stored procedures via ASP (VBScript). I have to admit I wish I had found this site earlier than today. Seems to have a great deal of useful info in a very functional layout.I have a couple of questions that could probably be cleared up quite nicely by someone with a bit more experience than I. First, am I right in my assumption that the only access I have to a value RETURNed from a Stored Procedure is via the Command object? My present method of firing a stored proc has been:set rsObj = objCon.Execute("MyStoredProc '" & strField1 & "'")and then reading the rsObj values into a local array etc...I have since written a few stored procs that return only a boolean or single string value to indicate simple business rules (CanWriteOrder etc). A recordset seems such a waste for this.I realize that I can RETURN a value from the procedure but am not sure 'where' it shows up.Second, Is there some extreme speed benefit in Dynamic SQL in stored procs? The string concatenation methods required to build the commands appear to be far more tedious than their ASP counterparts. I could see if there was some performance benefit.. Is there?Thanks in advance to anyone who cares to respond. |
|
|
|
|
|
ASP, Stored Prcoedures and the Command object