Quote:
Originally Posted by Rams Fan
I deal with SQL tables every ****ing day for my job.
Do you realize how much manpower it takes to migrate from one environment to another? That's not even counting the hours of coding it takes by trial and error to figure out what works and what doesn't work.
On top of that, you're asking people who work actual jobs for a living to prioritize this over their work or to outsource (which leads to an entirely different set of possible issues with regards to security vulnerabilities)?
WTF
I'm not a software engineer nor a developer, so I won't tend to understand the technical aspects regarding migration to a new cloud or server, but I'd be happy to volunteer to help with any SQL related tasks (can write in MySQL/PostgreSQL).
|
The good news is that (as noted above), there are migration tools that should make SOME of the transition a little easier. But as you alluded to, there are endless little snags you tend to run into along the way, and it doesn't help that this isn't even a "pure" install of vB 3.8 - it's been upgraded like 10 times starting with 2.1 (I think), so there's all sorts of shitty code lying around that could cause issues along the way.
In the end, it's entirely possible that Kyle will choose to just migrate to a new server and keep vB 3.8 as is. It's old, and it's shitty, but in theory just getting onto a new box that keeps the db on an SSD would take care of most of our issues, so if that's the easy path forward compared to starting from scratch on new software, it is what it is.