“One thing at a time / And that done well / Is a very good thing / As any can tell”
But life isn’t always that easy is it? I spend a lot of my workday juggling priorities. And I want to compare what I think to others. So I wrote a survey which explores the importance people place on different SQL Server issues. It’s easy to say avoid redundant indexes. But does it follow that it’s more important to clean up redundant indexes before rewriting cursors?
The List
Prioritize this list from greatest concern to least. So if an item appears above another item, then you would typically tackle that issue first.
- Corrupted database
- A SQL injection vulnerability
- Stale statistics
- Fragmented indexes
- Developers use a mix of parameterized SQL and stored procedures
- Sprocs prefixed with “sp_”
- Cursors
- GUID identifiers
- NOLOCK hints
- No automated backups
I want to hear what you think. Submit your prioritized list in the comments, or by using this survey: https://www.surveymonkey.com/r/MV9F9YT
I’ll be posting my own answers on Thursday, July 5, 2016.