April 27, 2016 at 2:36 am
Hello,
We have sql server 2008 R2 with ssis, ssas and reports...
I would like to write-up a document on upgrading to sql server 2014.
In the document I would like to have plans for having the right hardware as well as the software specifications. and having a Dev server also as we do not have one.
For example:
memory, disk space, list of benefits and disadvantages, issues when upgrading i.e. ssis 2008 packages to 2014 , t-sql upgrade, what tests to carry out, etc...
So then I can hand this to the head of the department so that they understand it.
Do you know if there is a document or a link I get use for this plan?
many thanks
April 27, 2016 at 11:02 am
arkiboys (4/27/2016)
Hello,We have sql server 2008 R2 with ssis, ssas and reports...
I would like to write-up a document on upgrading to sql server 2014.
In the document I would like to have plans for having the right hardware as well as the software specifications. and having a Dev server also as we do not have one.
For example:
memory, disk space, list of benefits and disadvantages, issues when upgrading i.e. ssis 2008 packages to 2014 , t-sql upgrade, what tests to carry out, etc...
So then I can hand this to the head of the department so that they understand it.
Do you know if there is a document or a link I get use for this plan?
many thanks
No document will help you because you know your environment better than others. You need to capture a baseline of all the metrics which you described in your current environment and project expected usage for next 6 months or so.
April 27, 2016 at 11:19 am
Does your current hardware run well? If so, you have an idea of what's needed. For Dev, I'd try to get close to prod, maybe half (or quarter) size so you can extrapolate performance. It's very rough, but it's better than nothing.
CPU/RAM/disk are based on what you have, size of db, and current workload performance. There's no way to say a database server should have xx cores/ram/disk because workload can dramatically affect this, regardless of database size.
If you post info on what you have, we can help, but you need to capture some baseline of what the current load is. This might help: http://www.sqlservercentral.com/articles/baselines/94657/
April 30, 2016 at 2:00 am
Thank you.
Are you able to refer me to a link which has proper project plan like resources, timing for testing and migration, etc. document...?
April 30, 2016 at 11:13 am
I doubt there is anything that complex written. There are variables for your environment, and most people don't do upgrades across three versions and document this. They usually do one.
You can look here: http://www.sqlservercentral.com/search/?q=upgrade+checklist&t=a&sort=relevance
There are some pieces you can use to examine this, but you'll need to do work. For the advantages and disadvantages, you'll need to look at changes in R2, then 2012, then 2014 to get a complete list. Some of those will matter for your environment, some won't.
For hardware, you need a baseline, though the versions will alter that slightly, it's good enough. Get performance on current hardware, and then make some guesses on extrapolation with new hardware. That's really hard, and I don't have a good way to do that. I'd guess you want a similar number of new cores and more RAM if you can, and as fast, or faster, disks.
Do you test now? If you don't have a test plan for patches, service packs, app upgrades, how could anyone spec out a test for the next version? You should have this in place. What needs to work? Everything you run, all packages, reports, etc., you should have a way to test those. If you don't, you'll have to do that. What I'd recommend is that you load a backup of production, and then have a script that adds 20-50% (or more) data to the database. That gives you load and performance. After all, data grows.
This should be some plan that your organization maintains over time, for all patches and upgrades.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply