mistakes

Upgrading to SQL Server 2014: A Dozen Things to Check

Upgrading to SQL Server 2014: A Dozen Things to Check

Here we go again! It seems that it was only yesterday we were talking about all the things you want to look out for when upgrading to SQL Server 2012. Now, just two years since SQL Server 2012 was released, we have a shiny new version with SQL Server 2014. And that means, of course,(…)

Upgrading To SQL 2012: Ten Things You Don’t Want To Miss

Upgrading To SQL 2012: Ten Things You Don’t Want To Miss

Many novice administrators make the common mistake of believing that the upgrade process for a database server is as easy as pressing a few buttons. While you can certainly click “Next, Next, Finish” and consider your task to be complete the truth is that the upgrade process is often considerably more complex. A proper upgrade(…)

The 5 Database Design Process Failures You Don’t Want To Make

The 5 Database Design Process Failures You Don’t Want To Make

Recently I wrote about about five database design mistakes you don’t want to make. Those mistakes were focused on database design, but what about the design process itself? It is possible that you could have all intentions of a solid design only to be let down by your overall design process. Here are the five ways(…)

Do You Make These 5 Database Design Mistakes?

Do You Make These 5 Database Design Mistakes?

Look, everyone makes mistakes. It’s true. But not all of us have the chance to make mistakes that end up costing millions of dollars in hardware and production support costs. Any one of the following five mistakes listed below will add additional costs to your company. It’s guaranteed. The costs could be hardware related (extra disk(…)

7 Mistakes You Can’t Afford To Make When Upgrading to SQL 2012

7 Mistakes You Can’t Afford To Make When Upgrading to SQL 2012

It’s new, it’s shiny, and it smells like frozen yogurt. No, it’s not the blender you got for Christmas. It’s SQL 2012 (formerly known as codename ‘Denali’). And it’s here. And you want to use it, you know you do. As much as you would like to believe that migrating to SQL 2012 is as(…)