Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Checking Up on Developers

By Steve Jones,

This editorial was originally published on May 8, 2009. It is being re-run as Steve is on vacation.

The other day I was reading Brad McGeHee's post on duplicate indexes, and it struck a chord with me. That same issue is one I've seen many times with in house applications. Developers don't understand indexing, they create one clustered index (CI) as the PK, and then they create the same index as a nonclustered (NCI) one. Either they don't realize that the PK is an index, or they are ignorant of the differences between a CI and an NCI.

What's worse is that I see it in third party applications as well. If you're selling a product, I think you ought to know how to tune it for a database. If you don't, I'd like to see some recourse for clients. Maybe some common settlement in a lawsuit. A few of those and I bet you'd have more DBAs hired by software firms.

Or a little more training for developers.

For this Friday's poll, I wanted to pick on developers a little. I like developers, I appreciate the work they do creating some great applications I use, but I also think they make some silly database mistakes. So this week:

What are common mistakes developers make in SQL Server?

Indexing is one area, but what other things do you see a lot from developers? I'm thinking a good list of mistakes here might be a nice checklist to go over with developers as they complete an application. It could be in code reviews, QA, pre-purchase requirements, RFPs, any number of places.

I'll add one more indexing issue that I've seen often in third party applications. Too often I've seen developers create a separate index on every single field in a table. For all tables! I realize that indexes improve query performance, but it does create an issue with inserts/updates, and space. Space isn't an issue as much as it was in the past, but as data sizes get larger, I would not be surprised to see this becoming a problem in some applications. More indexes also impact backup time and size.

Give us a response this Friday of the common mistakes that you see developers making, and that you wish they'd learn to avoid.

Steve Jones

Total article views: 485 | Views in the last 30 days: 3
 
Related Articles
FORUM

Creating an index

Creating an index

FORUM

Dynamically Creating Indexes

Dynamically Creating Indexes

BLOG

How to Avoid Some Common Developer and DBA Mistakes

In March, I ran a Question of the Month that asked, “What is the biggest mistake/problem you ever fo...

FORUM

Tips on creating indexes

Tips on creating indexes

BLOG

Don’t Make Dumb Mistakes by Duplicating Indexes

Just today, I was reviewing the indexing of a database used by a third-party application. As part of...

Tags
 
Contribute

Join the most active online SQL Server Community

SQL knowledge, delivered daily, free:

Email address:  

You make SSC a better place

As a member of SQLServerCentral, you get free access to loads of fresh content: thousands of articles and SQL scripts, a library of free eBooks, a weekly database news roundup, a great Q & A platform… And it’s our huge, buzzing community of SQL Server Professionals that makes it such a success.

Join us!

Steve Jones
Editor, SQLServerCentral.com

Already a member? Jump in:

Email address:   Password:   Remember me: Forgotten your password?
Steve Jones