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

Microsoft Agent Framework Makeover: Claws, Loops and Harnesses

Microsoft's newly released Agent Framework Harness packages the loops, planning, memory, context management and safety controls that developers previously had to assemble around AI models themselves.
Visual Studio 2026 Gives Copilot Built-In Skills -- and Makes Them Prove Their Worth

Microsoft is moving Agent Skills beyond bring-your-own instructions by shipping expert-authored workflows with the IDE, while keeping them off by default until testing shows their benefits justify the additional token use.
Copilot AI Billing Shock Met with Meters, Caps and Token-Saving Tools

GitHub is layering spending limits, expanded credit allowances and increasingly granular usage reporting onto Copilot, while Microsoft is reworking Visual Studio and VS Code to expose -- and reduce -- the cost of agentic development.
The AI-Powered Software Development Lifecycle

René van Osnabrugge makes the case that AI's biggest opportunity in software development is not faster coding -- it's reducing the friction everywhere else in the SDLC.