HighDots Forums  

Re: Stored Procedure vs. SQL Through Recordset.

Macromedia Dreamweaver Macromedia Dreamweaver Discussions (macromedia.dreamweaver)


Discuss Re: Stored Procedure vs. SQL Through Recordset. in the Macromedia Dreamweaver forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
craig v
 
Posts: n/a

Default Re: Stored Procedure vs. SQL Through Recordset. - 07-10-2003 , 11:04 AM






The advantage to using stored procedures are many.

1. Speed. Once a stored procedure is compiled SQL "remembers" it, executing
it extremely fast from then on. Inline SQL statements is must be executed as
a new query each time.

2. Ease of maintenance. If you have to change a query that is used by
multiple pages you only need to go in and change one stored procedure
instead of several web pages.

3. Security. Your call to the database is handled by SQL Server and not your
web page, preventing someone that may see your code from getting your table
names and structure.

I have not used Access databases for web pages, but a quick google search
turned up this tutorial that may help you.
http://www.stardeveloper.com/articles/display.html?article=2001050101&page=1

craig



"Jordan Marton" <JMarton (AT) HAHAmarketaxess (DOT) com> wrote

From what I've gathered, a stored procedure is a SQL statement STORED in the
database as opposed to the ASP page correct? Are there any advantages to
this? And does Accesshave stored proceudres?

Jordan




Reply With Quote
  #2  
Old   
Jordan Marton
 
Posts: n/a

Default Re: Stored Procedure vs. SQL Through Recordset. - 07-10-2003 , 11:15 AM






That was absolutely brilliant!!!

Jordan

"craig v" <craig765 (AT) spamless-yahoo (DOT) com> wrote

Quote:
The advantage to using stored procedures are many.

1. Speed. Once a stored procedure is compiled SQL "remembers" it,
executing
it extremely fast from then on. Inline SQL statements is must be executed
as
a new query each time.

2. Ease of maintenance. If you have to change a query that is used by
multiple pages you only need to go in and change one stored procedure
instead of several web pages.

3. Security. Your call to the database is handled by SQL Server and not
your
web page, preventing someone that may see your code from getting your
table
names and structure.

I have not used Access databases for web pages, but a quick google search
turned up this tutorial that may help you.

http://www.stardeveloper.com/articles/display.html?article=2001050101&page=1

craig



"Jordan Marton" <JMarton (AT) HAHAmarketaxess (DOT) com> wrote in message
news:bejt9p$56e$1 (AT) forums (DOT) macromedia.com...
From what I've gathered, a stored procedure is a SQL statement STORED in
the
database as opposed to the ASP page correct? Are there any advantages to
this? And does Accesshave stored proceudres?

Jordan






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.