Write High-Performance Stored Procedures -- Visual Studio Magazine

Write High-Performance Stored Procedures

Bill Vaughn''s session focuses on some best practices to help you optimize performance when working with stored procedures.

By Bill Vaughn
10/01/2005

Watch the video of the session! (1 hour, 4 minutes, Windows Media format)

SQL Server stored procedures are used by companies large and small to fetch intelligent rowsets, perform updates, manage data and referential integrity, enforce business rules, and protect the underlying data. These server-side blocks of T-SQL code can improve performance if they're written and executed correctly. Otherwise, they make a developer's (or DBA's) life miserable. The problem is, most developers do not fully understand how SQL Server compiles, caches, and reuses the query plan. This session focuses on a number of "best-practices" used to optimize developer and code performance when stored procedures are part of your application's design.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.