Session variable vs. Stored Proc
From: Andy G (ajgould_at_iastate.edu)
Date: 11/30/04
- Next message: John Hoge: "Re: Bind multiple selections to a query"
- Previous message: Shaun Wilde: "Re: Authorization HTML Header going missing"
- Next in thread: Ben Strackany: "Re: Session variable vs. Stored Proc"
- Reply: Ben Strackany: "Re: Session variable vs. Stored Proc"
- Reply: Karl Seguin: "Re: Session variable vs. Stored Proc"
- Reply: Hans Kesting: "Re: Session variable vs. Stored Proc"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 30 Nov 2004 16:11:22 -0600
I have a registration page that captures 75% of the users data. After they
enter that info they are redirected to one of two pages depending on how
they answered a question on the registation page. My question is would it
be better to store all of the fields(15 or so) from the first page in
session variables and reference them from the next page and run ONE stored
procedure OR would it be better to run a stored procedure the first page and
then run an update procedure on the next page with the rest of the fields?
So it would be 15 session variables with 1 stored procedure or 1 stored
procedure with 1 update stored procedure?
Thanks
- Next message: John Hoge: "Re: Bind multiple selections to a query"
- Previous message: Shaun Wilde: "Re: Authorization HTML Header going missing"
- Next in thread: Ben Strackany: "Re: Session variable vs. Stored Proc"
- Reply: Ben Strackany: "Re: Session variable vs. Stored Proc"
- Reply: Karl Seguin: "Re: Session variable vs. Stored Proc"
- Reply: Hans Kesting: "Re: Session variable vs. Stored Proc"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|