Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / April 2008

Tip: Looking for answers? Try searching our database.

Need advice: Stored Proc vs SQL Code vs GUI

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Cirene - 22 Apr 2008 12:41 GMT
I am working on an ASP.NET 2.0/SQL Server enterprise application which is
basically a online scheduler (like Outlook functionality.)  There will be
many simultaneous users hopefully.

For my sql related tasks I was thinking that most of the work can be done
using Visual Studio's GUI Wizards (drag/drop, etc...) without writing any
SQL related code.

Is there any benefit to choosing to write stored procedures or inline SQL
code (like in a DAL class) over simply using the GUI to do the "code"?

I hope I asked this correctly.

Thanks!
Cowboy (Gregory A. Beamer) - 22 Apr 2008 13:47 GMT
>I am working on an ASP.NET 2.0/SQL Server enterprise application which is
>basically a online scheduler (like Outlook functionality.)  There will be
[quoted text clipped - 6 lines]
> Is there any benefit to choosing to write stored procedures or inline SQL
> code (like in a DAL class) over simply using the GUI to do the "code"?

Yes. Separation of concerns.

You have a UI of some sort (web, it appears, since you posted here), some
business logic and data logic, along with physical data storage. Each has
its own purpose.

When you drag and drop UI code, you marry the UI to the database you are
using. This may be okay in your case, but you should be making a conscious
decision to bind the layers together in this manner.

Signature

Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss

or just read it:
http://gregorybeamer.spaces.live.com/

*************************************************

| Think outside the box!

*************************************************
sloan - 22 Apr 2008 15:26 GMT
As previously illuded to, you'll have this "marrying" of hte
layers/concerns.

If you actually do this, then I would suggest not calling it an " enterprise
application ".

I would call it a "hobbyist application that my enterprise is going to
use"...because that RAPID development model of drag/dropping isn't good for
maintainable code.

..

>I am working on an ASP.NET 2.0/SQL Server enterprise application which is
>basically a online scheduler (like Outlook functionality.)  There will be
[quoted text clipped - 10 lines]
>
> Thanks!

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.