Posted by Hugo Kornelis on 10/01/12 11:38

On 27 Jan 2006 06:19:03 -0800, mooreit wrote:

>The purpose for my questions is accessing these technologies from
>applications. I develop both applications and databases. Working with
>Microsoft C#.NET and Microsoft SQL Server 2000 Production and 2005 Test
>Environments.
>
>What is the purpose of a view if I can just copy the vode from a view
>and put it into a stored procedure?
>
>Should I be accessing views from stored procedures?
>
>Should I use views to get information? and Stored Procedures for
>Inserts, Updates and Deletes?
>
>What are the performance differences between the two?
>
>Thank you for any and all information.
>
>SBProgrammer

Hi SBProgrammer,

I wrote about the differences between stored procedures and views ten
days ago. Here's a link to the article on Google (warning - long URL,
might wrap)

http://groups.google.com/group/microsoft.public.sqlserver.newusers/browse_frm/thread/b20d4abdede81ada/75cc4092b8603807?lnk=st&q=view+stored+procedure+author%3Ahugo+author%3Akornelis&rnum=1&hl=en#75cc4092b8603807

--
Hugo Kornelis, SQL Server MVP

• Next in forum: Re: SQL Server 2000 Audit for login
• Prev in forum: Re: Can i debug/watch on the trigger's INSERTED and DELETED records/values?
• Thread view: Re: Views vs Stored Procedures, whats the difference?

[Reply to this message]