|
To actually do a move, probably a day or so to get the new environment (machine, memory, etc.) set up and tested. Give a day to actually copy the data over. Minimally a day or two to write, prove, and run code to demonstrate to management that the data did, in fact, make it over intact (although that can then be used for other moves, so don't lose it). Going out on the proverbial limb here ... a week?
|
|
|
|
|
day 1: get sql 2016, install. oh which version did you want?
day 1-5: figure out licensing model.
day 5: ok, i think i know which licenses we need. let me raise purchase request with accounting.
day 10: oh, no we need a License advisor to come in and assess.
day 30: license advisors came yesterday. now i can raise purchase.
day 56: purchase approved
day 60: acquired licenses. now can install.
day 61: oh, we need that feature that was in enterprise edition. Ok, i will just install, oh, need different licenses.
day 62: seek payment reimbursement from License Advisor for poor decision.
day 90: all license correct. install, upgrade database. done
you getting core or user license for that machine? and if core, damn, which my company that easy with money. What over $100k.
|
|
|
|
|
I have 2 answers. Either build it yourself, or outsource it.
Now, if this was Oracle. I would say he is insane. You could restore that in oracle pretty easily and copy the config settings over pretty quickly. (restoring 10TB of data will take a while).
With that said, it always depends. Is it one schema or 200? Do they all talk to each other. When they are done, do they have to sync the stored procedures from a repository? Is it all data or data and code?
You have to cut them a little slack. 3 months seems long. Too long. Okay, way too long. I would agree with Days. I might give them a week.
But I would certainly consider hiring an outside resource to come in and do it, and also AUDIT your DB guys for best practices. I find a good Audit shakes things up a bit, and puts people on notice. It also brings in a second pair of eyes which can be very helpful, and management gets around the competing groups complaining. Hard to defend the DB guys when the outside guys say they suck!
I have done a few IT audits and it is always scary what you find. The great thing is that SOME stuff gets fixed while you are there (like default passwords on wireless routers, OMG).
BTW, it looks like you are throwing hardware at your performance problems. Usually a good sign of a design flaw.
|
|
|
|
|
If the install was clean and easy - an hour or so
If the DB files could simply be detached, XCOPY'd, and reattached, and if the data could be copied over gigabit ethernet or USB3 or something fast then it's probably a day just to copy the data over, and anything from 5 mins to hours depending on how many physical database files you had.
If you were doing a straight upgrade, all security settings were the same (and scripted to allow easy setting up) then add another half hour of faffing around to get that setup (depending on how many databases)
But no. Not three months. Unless that's "2 months and 28 days waiting in our TODO queue because we have a ton on our plate, and 2 days to get it done".
cheers
Chris Maunder
|
|
|
|
|
They have to "verify" your current schema.
I'm betting on 6 months.
|
|
|
|
|
Yup. That's what they say. That they want to verify everything. These are the same people that write stored procs with spaces in the column names, # signs, etc. We once spent a day tracking down a crash because the SQL dev "accidently" put a trailing space in the column name "ColumnName ". He swore up and down that he didn't change any column names and dev swore up and down that he did.
Like I said before, I'm not a SQL expert and database doesn't interest me that much in general, so I'm not up on all the latest & greatest best practices, but I still know you shouldn't put spaces in column names, keep everything consistent, etc. Not have 11 copies of the same data copied all over the place, etc.
|
|
|
|
|
It used to be harder in the past, but it's rather easy to "parallel" the "thinkers" in DBA and QA with Express and Trial Versions of most anything; so when they do finally say "OK ... Do it your way!" (due to some pressure from "above"), you've already been up and running.
|
|
|
|
|
LOL, Spoken as someone who sees it as a simple badge swap. While 2016 is new you can't NEED it - It offers new features that you may want to use, but it also stops functionality that currently exists (deprecated & discontinued features - some real gotcha's moving 2008R2 to 2016.) You also trivialise (or rather don't mention at all) the organisational significance of the database. It this a production system running 24x7 @ 999999.
Any DBA can update the "SERVER" in ~30min (with outages), this doesn't mean the database(s) will work on the other side, or that all the attached applications will be able to reconnect and use them. So much has been glossed over with the vision of a new toy to play with...
|
|
|
|
|
Actually, it does have a killer feature for us: native spatial processing. That will cut our processing times by a huge amount.
|
|
|
|
|
I know I am late to the party, but my first question to these requests is always "What are you REALLY trying to do?".
Most people come at you with a problem to their solution instead of asking you for a solution to their problem. Once I sit someone down and have them tell me exactly what their problem is there is always a much simpler path to take instead of the putting the square peg in the round hole. In this situation you are describing I would be asking them what are you going to use this for? Are you expecting a handful of engineers on the enterprise hitting it? Or are you going for a web facing portal audience. How you plan to implement a SQL database really starts there.
|
|
|
|
|
|
/ravi
|
|
|
|
|
|
"Her blonde mohawk glistening in the sun, legs bowed out like a frog, SweePee was a crowd favorite at the Sonoma-Marin Fairgrounds:" [^].
Stories like this give me the courage to go ... on.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
I'm pretty sure that's a Gremlin
You always obtain more by being rather polite and armed than polite only.
|
|
|
|
|
I think it's disgracful!
They're treating them like dogs!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Worse, they're treating them like people!
Dogs don't care about looks, they hump everything
|
|
|
|
|
|
Yah I've seen some anomalous behavior from VS15 including locking up the entire computer so the only option is to pull the power.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Describe the steps to reproduce exactly, because our team uses Visual Studio 2015 every day on three of our enterprise apps, and we have never encountered an issue that required pulling the power due to a "lock-up". I would like to document this for my team.
|
|
|
|
|
I suspect it is either a major memory leak (multiple event assignments) or VS does not play happy with the corporate environment. I do know it gets reduced by cleaning up the memory leaks but still happens occasionally.
As I have the first 64bit OS in the building it is a bit of an experiment as they don't have all the policy delivery systems ironed out, I get a command window randomly open as they try and push down policy changes. They failed utterly to install VS2013 but I managed to install vs2015 and am reluctant to fiddle with it.
It regularly glitches for short periods as it deals with background process and compiles can be more like piles, bloody painful.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
We install our own software at our shop. IT is never allowed to install our development software for us. Lucky me, as I used to work at other places where that was the contrary.
I have 64 bit system (personal and work) and have not had many issues that I can think of, but you are dealing with corporate/IT security policies now, and I am not.
32 bit OS, on a box with great performance and memory is just as good, if not better than a 64 bit system, running 64 bit software, IMHO.
Interesting link for you, maybe: Why is Visual Studio 2015 still a 32-bit application? - Quora[^] has some compare and contrast of opinions on this in the comments.
|
|
|
|
|
I don't know when the last time I clicked "I'm Feeling Lucky" on Google Search, but I was writing another post and moved my mouse out the way and it just happened to stop on another browser window on the button. I only noticed because the text changed and caught my eye (only about 5 leters were visible).
So I took a look, and sure enough they have a rotation on the text options;
I'm Feeling Doodley
I'm Feeling Artistic
I'm Feeling Hungry
I'm Feeling Puzzled
I'm Feeling Trendy
I'm Feeling Stellar
I'm Feeling Playful
I'm Feeling Wonderful
I'm Feeling Generous
I'm Feeling Curious
No idea when that was introduced or if it makes a difference.....
|
|
|
|
|
Cool! I never click on that. Just tried 'Puzzled' and found something interesting.
"Go forth into the source" - Neal Morse
|
|
|
|
|
code for issue a book.........
|
|
|
|