Re: Views vs. Stored Procs
From: Nags (nags_at_RemoveThishotmail.com)
Date: 12/30/04
- Next message: Olu Adedeji: "Re: SQL-Insert-Statement crashing server"
- Previous message: Andrew J. Kelly: "Re: why is execution of a storedprocedure in QueryAnalyzer faster than executing this SP as scheduled job?"
- In reply to: Aaron [SQL Server MVP]: "Re: Views vs. Stored Procs"
- Next in thread: Geoff N. Hiten: "Re: Views vs. Stored Procs"
- Reply: Geoff N. Hiten: "Re: Views vs. Stored Procs"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 30 Dec 2004 12:52:39 -0500
But, why should the performance be better when using a procedure ?
-Nags
"Aaron [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:#u0IDIp7EHA.2196@TK2MSFTNGP11.phx.gbl...
> Views are typically not used for performance. They are usually used to
> simplify common joins/queries and or to implement moderate security.
>
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
>
>
> "James" <cppjames@aol.com> wrote in message
> news:eMlsA8o7EHA.1024@TK2MSFTNGP10.phx.gbl...
> > I created a pretty complicated query that joins a number of tables and
> > pivots a table. When I put this in a view, it takes about 6-7 seconds
to
> > run. When I put it into a stored procedure, it only takes about 5
> seconds.
> > Is there any reason to NOT put this into a stored procedure? I guess it
> > begs the question, why use a view at all?
> >
> > Thanks!
> > James
> >
> >
>
>
- Next message: Olu Adedeji: "Re: SQL-Insert-Statement crashing server"
- Previous message: Andrew J. Kelly: "Re: why is execution of a storedprocedure in QueryAnalyzer faster than executing this SP as scheduled job?"
- In reply to: Aaron [SQL Server MVP]: "Re: Views vs. Stored Procs"
- Next in thread: Geoff N. Hiten: "Re: Views vs. Stored Procs"
- Reply: Geoff N. Hiten: "Re: Views vs. Stored Procs"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|