October 26, 2016 at 1:38 pm
I'm considering upgrading our production server from 2005, at the same time we upgrade servers. I have not kept up on the most recent versions. No specific need to upgrade SQL, but Windows 2012 will not support SQL 2005, and I like to be as current as possible (within budget).
What's a good resource to evaluate options, and complexity of upgrade ?
Is the cost the same if I go to SQL 2012, 2014, 2016 ??
It's a fairly lightweight environment, supporting a website.
The main upcoming project is setting up a summary table from multiple production tables that will be heavily using full-text search. But still, pretty lightweight compared to many heavy traffic sites.
October 26, 2016 at 1:46 pm
homebrew01 (10/26/2016)
I'm considering upgrading our production server from 2005, at the same time we upgrade servers. I have not kept up on the most recent versions. No specific need to upgrade SQL, but Windows 2012 will not support SQL 2005, and I like to be as current as possible (within budget).What's a good resource to evaluate options, and complexity of upgrade ?
Is the cost the same if I go to SQL 2012, 2014, 2016 ??
It's a fairly lightweight environment, supporting a website.
The main upcoming project is setting up a summary table from multiple production tables that will be heavily using full-text search. But still, pretty lightweight compared to many heavy traffic sites.
Recommend that you go straight to 2016, best one so far.
😎
October 26, 2016 at 1:55 pm
Eirikur Eiriksson (10/26/2016)
homebrew01 (10/26/2016)
I'm considering upgrading our production server from 2005, at the same time we upgrade servers. I have not kept up on the most recent versions. No specific need to upgrade SQL, but Windows 2012 will not support SQL 2005, and I like to be as current as possible (within budget).What's a good resource to evaluate options, and complexity of upgrade ?
Is the cost the same if I go to SQL 2012, 2014, 2016 ??
It's a fairly lightweight environment, supporting a website.
The main upcoming project is setting up a summary table from multiple production tables that will be heavily using full-text search. But still, pretty lightweight compared to many heavy traffic sites.
Recommend that you go straight to 2016, best one so far.
😎
+1
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 26, 2016 at 2:40 pm
Go to 2016.
The testing you will need to do (and yes, you do *need* to test) will be the same for 14 or 16. As for licenses, at this point afaik, you would buy SQL 2016 licenses with downgrade rights.
2016 is very nice, the Query Store alone is worth the upgrade.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 26, 2016 at 3:11 pm
Can I install SQL 2016 on a new server, and just restore 2005 databases to it ??
October 26, 2016 at 3:14 pm
Yes.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply