View & SP's for just a few users

[Jake Jessup]

I have read about Views vs. SP's and I have question to which I could not
readily find the answer.

The database I'm creating will only have 1 user from the start and up to
three maximum. Is there any reason that I shouldn't just use SP's for
everything or might there be an advantage to using views.

This is not a heavy I/O project either and most of the day to day use will
be record manipulation and reference rather than new record entry.

Thanks

-Jake

[Simon Hayes]

"Jake Jessup" <wa*********@hotmail.com> wrote in message news:<31Zpc.57382$iy5.15229@okepread05>...

I have read about Views vs. SP's and I have question to which I could not
readily find the answer.

The database I'm creating will only have 1 user from the start and up to
three maximum. Is there any reason that I shouldn't just use SP's for
everything or might there be an advantage to using views.

This is not a heavy I/O project either and most of the day to day use will
be record manipulation and reference rather than new record entry.

Thanks

-Jake

In general, it's good practice to use stored procs for database
access, although some tools (especially for reporting) build queries
for you, so views may be a better abstraction layer in that case.

Views are useful for encapsulating frequent and/or complex joins, to
avoid having to type the same joins everywhere in your code. Also,
don't forget that views can be indexed (assuming you have MSSQL 2000 -
you didn't mention a version), which can be very useful for some types
of query, such as large joins and aggegrations.

Simon

[Jake Jessup]

"Simon Hayes" <sq*@hayes.ch> wrote in message
news:60**************************@posting.google.c om...

In general, it's good practice to use stored procs for database
access, although some tools (especially for reporting) build queries
for you, so views may be a better abstraction layer in that case.

Views are useful for encapsulating frequent and/or complex joins, to
avoid having to type the same joins everywhere in your code. Also,
don't forget that views can be indexed (assuming you have MSSQL 2000 -
you didn't mention a version), which can be very useful for some types
of query, such as large joins and aggegrations.

Simon

I'm using MSDE 2000. I'll keep that in mind about the complex joins, I might
have a few. Thanks for the advice. I'll stick mostly to SP's.

-Jake