Link to home
Start Free TrialLog in
Avatar of subhorachana
subhorachana

asked on

Stored Procedures vs views for connecting to Iseries DB2 databse using .NET

Hello,
I have a requirement to access the Iseries DB2 database using .NET.
I need to acce a number of AS 400 files on DB2.
For that we can think of the option of creating store procedures using Iseries ACcess, since stored procedures are mostly used for connecting to the datbases from .NET.
However we got a suggestion from a more experienced person on AS 400 that views will probably be a better solution.
We were told that it will be very easy for an AS 400 person to create one single views on all the tables that are required in a query and then oiut query will only access that view.
Can some one please suggest the pros and cons of  using views over Sored procedures or vice versa?
Avatar of silemone
silemone
Flag of United States of America image

hmmm...both have cached exec plans, the only thing I can think that can be of benefit with the view is that security would be better since you can hide rows that you may not want exposed.
However and indexed view would have increased performances so a view would be the way to go.
However an indexed view would have increased performances so a view would be the way to go.
i should warn you though...indexed views are more efficient for loading, but not updating...so if you're going to have many updates then the bad outweigh the benefits...
ASKER CERTIFIED SOLUTION
Avatar of Gary Patterson, CISSP
Gary Patterson, CISSP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial