In side-by-side tests I did a few years ago (that anyone with a few minutes can replicate), there was effectively no performance difference between the two. In practice then, that savings doesn't matter. ![]() Who's willing to bet that the SQL Parser, with decades of optimization work, can parse 100% of your queries in a few hundred nano-seconds? ![]() Execution for either would come up with the same, cached plans, but sprocs wouldn't have to parse each time. IIRC the only additional step Stored Procedures avoided was Parsing. This means that the Query Plan for every query run on ADO.NET is cached. It just became religion for the masses of MS platform Developers.ĪDO.NET (and whatever it's called these days) executes all Parameterized queries through (see if I can get the casing right) the sp_execsql procedure. SQLBooksOnline actually has this information clear as day, but MS Evangelists like Rob Howard (went on to create Teligent) would go around spouting the "sprocs are faster!" line and no one would ever think to point out the discrepancy. This is the old Microsoft Misinformation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |