Best Practice for passing session variable in SP

[specialist]

Greetings-

I wanted to ask anyone and everyone what they consider the best practice for passing session variables.

I have a situation in which i need to pass two variables ( a Start Date and End Date) in a SP in order to capture records between those two dates.

Would it be best to add the variables in the SP, or outside the SP? There are roughly 80 or so different calculations which need to be made in the application against a DB with roughly 1600 records.

Thank you in advance for any response, and apologies as well is this is the wrong forum!

happy holidays,

mike

 

[NoCoolHandle]

The questions I would tend to ask are...

How many users will be on the system concurrently?
How intensive are the calcualtions?
How powerfull are the client systems?

Bottom line.
Don't do things on the server that arn't necessary.. however if the work load is small.. Who cares? But if it isn't.... Do as much on the client (or the middle tier layer) as possible..

1 word of caution. We tend to find that successfull apps get used by more and more people, so don't build a bottle neck into the system.

My 1c

Rob

 

[specialist]

Rob-

Thank you for the reply...to answer your questions:

How many users will be on the system concurrently?

>20 users max

How intensive are the calcualtions?

pretty basic select statements, nothing outrageous.

How powerfull are the client systems?

unknown at this time. I would assume nothing outrageous either.

Thanks againand happy holidays.

Mike

 

[NoCoolHandle]

My guess is that you can have fun and write as much logic as you can on the server

For what you are looking at, you really shouldn't see much of a hit. Depending on how and where you are working with your dates and what type of systems you are running (olap vrs oltp) you might want to evaluate indexed views..

However you sound like you should be well within a servers comfort range..