Comments on: Database Myths: Stored Procedures vs. Ad Hoc Queries

By: Sebastian

Sebastian — Wed, 04 Nov 2009 14:36:37 +0000

Yes, at least in SQL Server, it doesn’t matter.

Be careful though, it’s easy to build dynamic queries that don’t hit any index.

By: Hemant

Hemant — Wed, 04 Nov 2009 13:00:42 +0000

So, does this mean that whether I use a stored procedure or fire a query from my app using some data-access logic .. both count the same in terms of performance.

That is – there’s no extra benefit of ‘compiled’ query, infact it is better to have a ‘dynamic’ query built-up’ on the app side whihc provides great flexibility !!!

Please clarify/confirm my doubts …

By: Sebastian

Sebastian — Wed, 05 Aug 2009 22:14:54 +0000

Yes, you have way more control if you set the rights at the table level, yet one has to admit that you usually don’t create stored procedures that do everything.

And yes, naming is absolutely important but that isn’t limited to stored procedures.

By: DotNetBurner - SQL Server

DotNetBurner - SQL Server — Tue, 04 Aug 2009 01:09:12 +0000

Database Myths: Stored Procedures vs. Ad Hoc Queries | Coding Efficiency…

DotNetBurner – burning hot .net content…

By: Robz

Robz — Mon, 03 Aug 2009 23:05:37 +0000

Security is a BIG WRONG for Stored Procs. Grant Execute versus Grant Select from a table. You know EXACTLY what the select allows and doesn’t allow. Granting execute on a stored proc really gives someone the ability to create, update, delete, and select all in ONE. You say naming the sprocs accordingly is the answer (i.e. Something_SELECT)? What happens when you get out of sync with the name and someone executes something that makes updates to production???! Ouch…

True story.

By: DotNetShoutout

DotNetShoutout — Mon, 03 Aug 2009 17:00:49 +0000

Database Myths: Stored Procedures vs. Ad Hoc Queries | Coding Efficiency…

Thank you for submitting this cool story – Trackback from DotNetShoutout…