Stored Procedures vs. Dynamic SQL

Seems to be back on the agenda again. Check out Frans’s blog if you want to track through this one again.
This entry was posted in Computers and Internet. Bookmark the permalink.

28 Responses to Stored Procedures vs. Dynamic SQL

  1. chris seary says:

    Hi Ian
    Security – it\’s easier to restrict access via task than via table/column access. If you try to regulate access via tables/columns, once you have a few different roles it becomes incredibly complex, and so security suffers.
    Performance – so many articles on precompilation and caching, but nobody mentions indexes. If the dba has the SQL (in stored procs), then he/she can tune indexes to match the queries. This is orders of magnitude more important than whether the query is precompiled or not. If you don\’t have the right indexes, then you\’ve turned your million dollar sql cluster into Acess 2.0. Regardless of whether or not the query plan is in the cache.
    This certainly ain\’t directed at yourself, but more to the general blogosphere discussion. There\’s no point just saying that the security and performance issues with LINQ don\’t exist because of precompilation and parameterised queries. We need new patterns and processes to make it all work. I\’ve got an article which is hopefully a start to the security issues, but needs more work

  2. Unknown says:

    エスピーエフ 花粉症  新宿賃貸    マンスリーマンション     営業代行 印鑑 営業支援  雛人形  フレッツ光  人材派遣  マンション 投資 マンション投資   オートローン   ゴルフ会員権   バイク便 
    派遣   投資マンション  
    鼻づまり  Bフレッツ  FX  いびき  販売促進 

  3. Unknown says:

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s