Right now I'm working on an application (ASP.NET 2.0, SQL 2005) which uses stored procedures for all SQL, apparently so nobody has to "play find the SQL" (their words) in the application.<BR><BR>The ...

SQL Server is one of the best products to come out of Microsoft, but not every professional knows how to use it effectively. For example, some might find it difficult to create a stored procedure but ...

A while ago somebody posted in one of my threads six or so reasons to use stored procedures instead of raw SQL in asp applications. I know a couple of reasons, but a few of the reasons he listed I ...

Stored procedures can speed up your code by reducing trips to your database -- even if you only have one SQL statement to execute. Here's how to speed up your application (and how to simplify your ...

Tony Patton discusses the merits of stored procedures versus placing SQL directly in the code. Find out which one is best for your particular situation. I once was pulled into a discussion about the ...

Entity Framework 6 gives you a variety of ways to call stored procedures that return data and capture the results those procedures return. Here's a look at all of them. In an earlier column, I showed ...

A common SQL habit is to use SELECT * on a query, because it’s tedious to list all the columns you need. Plus, sometimes those columns may change over time, so why not just do things the easy way? But ...

SQL is neither the fastest nor the most elegant way to talk to databases, but it is the best way we have. Here’s why Today, Structured Query Language is the standard means of manipulating and querying ...