Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 2.0 > BOOK: Beginning ASP.NET 2.0 and Databases
Password Reminder
Register
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Beginning ASP.NET 2.0 and Databases
This is the forum to discuss the Wrox book Beginning ASP.NET 2.0 and Databases by John Kauffman, Bradley Millington; ISBN: 9780471781349
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning ASP.NET 2.0 and Databases section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
 
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old June 26th, 2008, 05:25 PM
Authorized User
 
Join Date: Apr 2008
Location: , , .
Posts: 26
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to AspNetGuy
Default Stored Procedure versus Data Access Logic Componen

I have a form that contains 65 fields. The fields contain data related to the person applying to go on a trip, his parent, his church, and his abilities. I have created tables for Applicants, Parents, Churches and Abilities.

Next I created Stored procs for INSERT, UPDATE, DELETE and SELECT for each of the tables.

Before INSERTing the Applicant record, the other records must first be INSERTed. I have three directions I could go in.

1) Feed all of the data necessary to INSERT all of the records to the InsertApplicant stored proc and let it invoke the other stored procs (InsertParent, InsertChurch, InsertAbilities).

2) Create another stored proc and feed it all of the data and relieve the InsertApplicant stored proc of all of the parameters. Then have his new stored proc invoke the other stored procs (InsertApplicant, InsertParent, InsertChurch, InsertAbilities).

3) Create a C# Data Access Logic class that consumes all of the parameters and invokes each of the stored procs for the INSERTs.

What are the advantages and disadvantages of the three methods and do you have a better idea.

Thanks in advance for any guidance.

 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
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

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
how to use stored procedure in Access hertendreef ADO.NET 1 June 3rd, 2006 03:04 AM
stored procedure that inserts data desireemm SQL Language 5 January 22nd, 2006 04:25 PM
How to add a stored procedure in Access badgolfer Access 2 June 17th, 2004 08:13 PM
Mixing Data access logic and business logic polrtex BOOK: Professional Jakarta Struts 0 December 15th, 2003 07:19 PM



All times are GMT -4. The time now is 09:21 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.