Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Reasons to install SQL Server v. 2008R2 versus 2012 on a new server? Expand / Collapse
Author
Message
Posted Friday, March 7, 2014 10:55 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 28, 2014 10:52 AM
Points: 72, Visits: 448
Other than if there's an application that isn't compatible with SQL Server 2012, are there any reasons v2008 or 2008R2 would be a better choice than v2012? As v2012 has been out for some time and v2014 will be the latest release soon, it's not bleeding edge or a "0" release so are there any other reasons? We have Windows Server 2008R2. Is an older version of SQL Server less expensive? Thanks. Any opinions or advice is welcome.
Post #1548827
Posted Friday, March 7, 2014 11:51 AM This worked for the OP Answer marked as solution
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, September 11, 2014 2:28 PM
Points: 1,194, Visits: 2,219
If you are heavily using SQL Server features that are discontinued in SQL 2012 and if it involves huge effort to replace those functionalities then that would be a business reason.

Check this link for the discontinued features ..

http://technet.microsoft.com/en-us/library/ms144262.aspx

Also legacy DTS packages can't be hosted in SQL 2012. Suppose you have large no of packages you need to convert them to SSIS before you can upgrade to 2012.

For cost comparison check these ..

http://itknowledgeexchange.techtarget.com/sql-server/sql-2008-r2-is-pricy-but-so-is-that-other-database/

http://www.brentozar.com/archive/2009/11/sql-server-2008-r2-pricing-and-feature-changes/

http://blog.fpweb.net/choosing-between-sql-server-2012-sql-server-2008/#.UxoRK-OwKk8

--
SQLBuddy

Post #1548843
Posted Friday, March 7, 2014 11:56 AM This worked for the OP Answer marked as solution


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:46 AM
Points: 13,752, Visits: 28,148
The only reason, other than outright compatibility issues, is price.

The licensing costs for SQL Server 2012 are different than 2008R2 and less. For most situations I've seen, they're more. So, going with the older version could cost less, at least in the short term. But then you're installing six year old technology as a starting point. It's more likely to age out of support, not have necessary updates, all sorts of other, hidden, costs that may preclude that short-term licensing cost gain.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1548846
Posted Friday, March 7, 2014 4:48 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 28, 2014 10:52 AM
Points: 72, Visits: 448
Thank you Grant Fritchey. I came to this job from a mostly SQL Server 2012 shop so I was dismayed to find the network administrator's husband installing SQL Server 2008. The compromise was 2008R2 when I asked if we could install a newer version. There weren't any existing SQL Server servers and no applications requiring an old version. Politics were thick. No one here knows what a DBA does but it's assumed that a DBA queries the data but doesn't take care of the database(??). The network admin (probably with help from her husband) wants to do that. I didn't have any knowledge of this situation until I arrived. I was told it was a new operation and I could build the servers from the ground up. Sounded ideal. Now there's another server that they've installed. I believe that in a situation of buying new licenses for SQL Server for a brand new operation there isn't a good reason to go with old versions as you said. I am a DBA but I was an Oracle one until two years ago. My last job was a SQL Server DBA with transactional replication between servers in different centers.

The budget here is not tight but no one knows whether I'm correct or the network administrator/desktop support person is correct so I have an uphill climb because she got here 6 months before me and none of the executive team has a technical background. Their eyes glaze over if I try to explain the difference between the roles.

Thanks for reading my tail of woe. Your answer helps me with trying to get upgrades though because maybe the licenses "purchased" through her husbands company can be upgraded.
Post #1548927
Posted Friday, March 7, 2014 4:51 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 28, 2014 10:52 AM
Points: 72, Visits: 448
Thank you SQL Buddy! None of these situations apply to us because everything is new because before I came the tiny staff never coded in SQL but one of the Directors wanted a server-based databases instead of the existing Access databases. That doesn't stop the two-person existing staff from installing everything and controlling things though, unfortunately.
Post #1548928
Posted Friday, March 7, 2014 9:51 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:38 PM
Points: 3,931, Visits: 7,160
Since this is a new position, it sounds like an ideal time to talk to your supervisor and relay the "you hired me because..." and "this is what we need because"

If you wait too long to have a talk, it might be too late, and the husband will forever be an obstacle in you getting your job done, and your handle on the company's data/processes.


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1548944
Posted Saturday, March 8, 2014 4:11 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:46 AM
Points: 13,752, Visits: 28,148
MyDoggieJessie (3/7/2014)
Since this is a new position, it sounds like an ideal time to talk to your supervisor and relay the "you hired me because..." and "this is what we need because"

If you wait too long to have a talk, it might be too late, and the husband will forever be an obstacle in you getting your job done, and your handle on the company's data/processes.


Plus 10 Million!

I really couldn't agree more.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1548955
Posted Saturday, March 8, 2014 5:03 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 28, 2014 10:52 AM
Points: 72, Visits: 448
Thanks MyDoggieJesse. I am pretty direct so I did discuss it immediately when I found out but no one would do anything. The wife screamed at me after hours when no one else was around and said no DBA had ever patched the DB servers much less installed the SQL instances (she called it "the database") wherever she had worked before. And she had worked in five (5!!) states while being "hit on" by Jake Gyllenhall in one of those states while she was trying to work. Recently a new server came in that her husband installed at their home because she's on maternity leave and it was purchased through his company (consulting business). I've only worked in two states but wherever I've worked the DBA did install SQL Server/Oracle and usually I had local admin access to the boxes as well unless there was a knowledgeable system administrator who'd work with me on things that I didn't have access to.

This story is a little hilarious if I didn't have to live through it. Not sure how many states you've worked in is the litmus test for authority but maybe I'm out of touch. In the short time I've been in the job I have a new boss now who may end up straightening things out but he's not technical so it's taking a while.
Post #1548957
Posted Saturday, March 8, 2014 5:13 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 28, 2014 10:52 AM
Points: 72, Visits: 448
Agreed Grant Fritchey. I've been about as direct as I could be without getting fired. My old boss was clueless about SQL and tried to get me to use Access instead. I explained how Access is fine for some things but not for the system they want now that the company has grown so much. I didn't show him this but I was tempted: [url=http://www.brentozar.com/archive/2010/02/top-10-reasons-why-access-still-doesnt-rock/][/url]

My new boss isn't technical but he'd heard about SQL Server at his last job and wanted it. I'm working on getting him to understand but it's taking time. I truly believe now that the ones who hired me as a DBA didn't know what that is. I believe they think a developer is always the DBA because all they've known is Access and it doesn't need administering or, say, replication.
Post #1548959
Posted Saturday, March 8, 2014 6:18 AM This worked for the OP Answer marked as solution


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:38 PM
Points: 3,931, Visits: 7,160
Here's a thought, play devil's advocate: go to the husband who set up and configured the server - Ask him how he configured the storage array: Ask how he aligned the disks? What block size was configured, which RAID type(s) did he choose? And why? If the answers aren't acceptable then take that to your boss and say "here's why "I" need to be taking the lead on this...etc" - if the husband has done a goodjob, then make him an allie (sp?) and say "hey I think we got off on the wrong foot here.." - because obviously had a decent idea of what he's doing ;)

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1548963
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse