SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Upgrading to 2012


Upgrading to 2012

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)

Group: Administrators
Points: 223634 Visits: 19628
Comments posted to this topic are about the item Upgrading to 2012

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Dave Poole
Dave Poole
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24195 Visits: 3487
The shift to per core licencing rather than per CPU while a reasonable thing to do does have big cost implications.

"Always-on" technology puts us in a good place for hybrid cloud implementations.

Column store indexes definitely justify the cost if you are running a data warehouse.

If security is a constant concern then the security enhancements of 2012 may be worth it.


I'm going to say something contraversial here. You can do cold hard financial logical analysis of cost vs benefits and put forward a recommendation but if your business people read about a fabulous new feature that will solve all their problems then somehow fact based cost analysis goes out of the window. Even if the facts say don't the "feeling" is do. A bit of a double-edged sword that one so make sure you are holding the handle.

LinkedIn Profile
www.simple-talk.com
Martin Stephenson
Martin Stephenson
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1272 Visits: 693
I'm happily using SQL2008 and still finalizing the shift from older 2005/2000 servers to 2008, with one exception our sharepoint 2010 install is run using SQL 2012 as the BI integration is far beyond all previous versions and the only selling point as far as the business was concerned. The majority of business apps need a working database and unless application vendors insist on new versions we stay where we are.
Steve-3_5_7_9
Steve-3_5_7_9
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4542 Visits: 1611
We're in the process of upgrading, and in fact, we're going live this weekend with SQL 2012. It's only one instance of many.

Our company skips releases, so we're moving from SQL 2005 to SQL 2012. For us, it is NOT cost effective to upgrade to every SQL release because it takes us about 3 years to migrate all databases over to the next version; which coincides with MS 3 year release plan. If we upgraded with every release, my full time job would be upgrades.

SQL 2012 is an outstanding release.



Megistal
Megistal
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3869 Visits: 2570
Our customer base still mostly runs XP and they don't plan to upgrade their OS soon. So we go where the money is therefore we will stay with 2008 R2 for quite long.
So long that I'm not ever sure if we will upgrade on the next release of SQL server (v. 12) either.
I know, this will be quite an issue.
Sigerson
Sigerson
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1427 Visits: 1239
We have no plans to upgrade to 2012. For us, there is so discernible business benefit to doing so.

We have a mix of applications running both 2005 and 2008, and they're all working fine. These are straightforward client server apps with nothing fancy involved, just basic d/b functions and a little BI. If it ain't broke ...

Sigerson

"No pressure, no diamonds." - Thomas Carlyle
OCTom
OCTom
SSCarpal Tunnel
SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)

Group: General Forum Members
Points: 4893 Visits: 4152
Many of our SQL server instances are running packaged software. It's up to the vendors when they switch. We usually follow suit about a year later.
We have two vendors still running 2005, most are on 2008 and none are planning for 2012.
lionfan91
lionfan91
SSCertifiable
SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)SSCertifiable (5.9K reputation)

Group: General Forum Members
Points: 5917 Visits: 433
We're a US government (US Air Force) organization and we'll be sticking with 2008 R2 for the forseeable future. My specific application runs using SQL 2008 on three different networks, all of different classification levels. In order for us to upgrade anything we have to get Information Assurance and the security officers to approve the new software for all three networks. That's typically a nightmare. Fortunately SQL is US-owned software so the process is much simpler. Getting software developed by foreign-owned companies approved is nearly impossible.



terrance.steadman
terrance.steadman
SSC Eights!
SSC Eights! (823 reputation)SSC Eights! (823 reputation)SSC Eights! (823 reputation)SSC Eights! (823 reputation)SSC Eights! (823 reputation)SSC Eights! (823 reputation)SSC Eights! (823 reputation)SSC Eights! (823 reputation)

Group: General Forum Members
Points: 823 Visits: 538
Greetings,

I am currently in the process of updating our system to SQL 2012. Our present system is SQL 2005. Needless to say, this is causing us some problems as 2005 is no longer supported or being updated. So, by making the big jump from 2005 to 2012, the company felt that we could avoid the need to run a database upgrade for at least 5 years. We can also keep our system more secure with the better security enhancements and encryption techniques. We felt it was easier than upgrading to 2008 and then needing to upgrade again in 2 - 3 years.

Have a good day.
AspiringGeek-40457
AspiringGeek-40457
SSC Journeyman
SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)

Group: General Forum Members
Points: 75 Visits: 112
Two words: Columnstore rocks! It's a game changer in SQL Server 2012, & even more so now that it's writeable in SQL Server v.next codename SQL 14 (& already in production in PDW). By itself, columnstore can be a compelling reason to upgrade.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search