Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

Reasons not to upgrade to SQL Server 2012

As exciting as SQL Server 2012 is, with its multitude of new features, it’s not always possible to upgrade right away.  Here are some reasons that may cause you to delay your upgrade:

Training – Your developers and dba’s will need to learn the new features of SQL Server 2012.  Finding the time for them to carve out and take away from their other tasks could take a while

Licensing – You will have to spend money to purchase new licenses.  For earlier SQL Server versions, you bought one license per physical processor regardless of how many CPU cores it had.  If you chose your server hardware smartly, you could buy eight CPU cores for the cost of one SQL Server license and save enough in licensing fees to pay for the new server.  To license SQL Server 2012 for that same server, you’ll need eight core licenses.  The new core license fees are less than the previous per-CPU fees, but, if you do the math, Microsoft has conspicuously increased SQL Server’s price

New server purchases – Usually the purchase of a new server or two is required in order to test out SQL Server 2012, and then more servers to upgrade just a portion of your databases (since rarely will you upgrade everything at once and you usually don’t want to mix two versions of SQL Server on the same server)

Certification by hosting company – Many companies are at the mercy of their hosting company to certify the use of SQL Server 2012 before it can be installed into production

Certification by 3rd-party applications – Chances are you are running at least one large application from a 3rd-party, and you can’t upgrade the databases it uses to SQL Server 2012 until the 3rd-party gives the ok

Testing – Of course you must test all the databases on the new version.  This takes time and you may be too busy to get to it

More info:

When Will You Upgrade to SQL Server 2012?


Leave a comment on the original post [, opens in a new window]

Loading comments...