Skip to main content

SQL Server 2012 Upgrade

SQL Server 2012 has been in RTM since the 1st April 2012. Many of my clients have been evaluating the new product but have not yet migrated their production servers to the new product. This is mainly to with timing and need. Over the next months (up to 12 months) several of my clients are planning on migrating some of their database servers to SQL Sever 2012.

How about you? Have you made the move yet?

SQL Sever 2012: DBA Skills Upgrade


  1. I've been eyeballing it this past week, and am thinking about it. Any news on when SP1 will be out? Has it been stable for everyone for the most part?

  2. We were considering it to help us with a Disaster recovery setup on a remote site. SQL 2012 would give us two options: 1. Using the Availability groups to fail over a set of databases 2. GeoClustering/Multi-Node Clustering.
    Both would be a better option than our current mirroring solution. However, we just go these new servers and they're less than a year old so it's hard to convince anyone that they need an upgrade now.

  3. Hi - SQL Server 2012 has been very stable since its release. I have several clients using it. I know in previous releases, people/DBAs have waited for the first service pack before upgrading. I don't think, these days, there is that much of need to do that. Its a very stable product. I guess you need to time the upgrade right so it right so it fits in best with your business needs. Which is what thesqlpro is trying to do

  4. It can be tricky to get people upgrade especially when they have just invested in new hardware. I'm guessing you like to stay away from in-place upgrades prefering a side by side migration when upgarding SQL Sever?

  5. We're not sure what we want to do yet Gethyn. We just released a new website and a new AMS product on our servers. It would be hard to use time and resources to upgrade these new servers while other servers are still on SQL 2005 and 2008. I'm guessing we would probably go with an in place upgrade. We're running a clustered environment, so what would the approach be? Upgrade the passive node, then failover then upgrade the other node? Or do you have to upgrade the active node first?


  6. Service pack 1 has been released for SQL 2012 by the way:


Post a Comment

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…