(Wobbly BlokeHello, did I miss anything on,
Thu 22 Apr 2010, 17:08,
archived)
I just got called into a meeting with the head of IT and a digital project manager
They wanted my opinion on moving a website from one server to another. They had logged in and copied down all the files, and had them ready to upload to the new server, including the CMS files. "CMS?" I asked. "Have you copied the database as well?" "What database?" they replied.
I am beginning to wonder if I'm the only person in the company who understands anything. Needless to say, it's fallen to me to download and store an entire database so it can be uploaded to the new SQL Server. I'm halfway through doing this (I've copied down the table structure and field names etc) and the head of IT tells me he's going to switch off the old server as we don't need it any more...right? After all, why would we need any of the data?
*bangs head on desk*
(emveecruor deo cruoris,
Thu 22 Apr 2010, 17:11,
archived)
Good grief
(mediocreha ha ha, you're reading this,
Thu 22 Apr 2010, 17:12,
archived)
Apparently they're building a new digital team
I have to decide soon if I want to be a part of it...which translates to "do all the work because no-one else seems to have a scooby doo what they're talking about"
(emveecruor deo cruoris,
Thu 22 Apr 2010, 17:15,
archived)
ouch......
(theoriginalsteve<this space intentionally left blank>,
Thu 22 Apr 2010, 17:14,
archived)
(emveecruor deo cruoris,
Thu 22 Apr 2010, 17:28,
archived)
D'oh.
Do you call SQL 'ess que ell'? Or squirrel or sequel or something? I'm told a lot of IT people call it sequel but I don't want to use that term in case that's bollocks and I look stupid.