One of the most common problems when running SQL Servers is slow queries. The help desk or database team usually hears that described as the application is slow or ...

As I discussed in an earlier column, SQL Server keeps a plan cached for each query it sees (assuming the query requires planning in the first place, of course). That's great for speeding up processing ...

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 ...

See performance gains by using indexed views in SQL Server Your email has been sent A view is a saved T-SQL query in SQL Server. The view definition is stored by SQL Server so that it can be used as a ...

Using Access to build a front end for SQL Server Your email has been sent What are the advantages of using Access as the front end to a SQL Server database? For starters, it's likely that your ...

SQL is a convenient way to manage and query your data, but badly written queries can tie up your database. Here are seven common SQL traps and how to avoid them. Database developers have it tough.

OK, I’ll admit it. I’m not a DBA, but that doesn’t mean I haven’t overseen databases and their performance. I was (and probably still am) the guy who installed a Microsoft SQL database by hitting Next ...