SQL-LIBS #1: I’m Just A Sheep Following Orders
Why should Fridays be reserved for fun and office hi-jinx? I’ve been threatening to do this for quite some time, but starting today I will be converting a legitimate piece of email or vendor documentation I’ve encountered into a fill-in-the-blank-style-rhymes-with-ad-lib form (don’t sue me you-know-who-you-are) for you to use as a stress breaker with your co-workers and friends.
Names will be ommitted to protect my job the guilty and innocent alike. As will company and product names, though one may be able to draw conclusions since bad software development seems to be prevalent in our line of work.
A little background on this first one: the vendor could not remotely support our database; sending it via secure FTP was their requirement. So, we packaged up our SQL 2005 database (that they originally set up on-site for us) to them – all 15GB of it – and they proceeded to take a couple weeks (resulting in a couple weeks of downtime) to fix the issues and send it back to us. The end result was that they also tossed in a SQL 2008 upgrade for free. Oh, did I fail to mention that they did the original installation on a SQL 2005 instance for us? Did I fail to mention at the time we did not have a host SQL 2008 instance for this database and that we ended up sending the original backup to them to re-do their work? I do believe I blogged about this transgression over the summer. Please provide back in comment form your completed SQL-LIB to this post as a way to share with the community!
Anyway, now that you have the background story, I give you…
SQL-LIBS #1: I’m Just A Sheep (Following Orders)
We ( verb ending in -ed ) your database to SQL Server 2008 while we had the opportunity. The SQL Server is now 2008; the compatibility level is SQL Server 2005(90). You are ( adjective past-tense ) even though the compatibility level is 90, you will not be able to ( verb ) the database to a SQL Server 2005 instance. We ( verb ) you secure a copy of ( name of software product ) and ( verb ) your SQL Server or ( verb ) SQL Server 2008 on new ( noun ).
All I am doing is what ( name of incompetent manager ) had asked me: ( verb ), ( verb ), and ( verb ) the already upgraded database onto the ( random acronym of choice ) server. I wasn’t aware that the ( noun ) you ( pural noun ) were ( verb ending in -ing ) was SQL Server 2005
( same name of incompetent manager ) is not here right now, but should be back ( time in the future ), I think.
I am ( any emotion other than “sorry” ) for the terrible ( noun ), and the best I can ( verb ) to do is to have the ( noun ) ( verb ending in -ed )on a SQL Server 2005 instance and that’ll take some time – a (datepart parameter from datepart() function) or thereabouts. So I’ll proceed with that, and I’ll have ( same name of incompetent manager ) ( verb ) with you ASAP.
If there is anything else I can ( verb ), please let me know.
Sincerely,
(name of bag boy at favorite grocery store).
SMALL PRINT:
Grammatical errors were directly from the original email. This is a work of parody; fiction perhaps if it alleviates me from any threats of litigation. Offer void in Rhode Island and The District of Columbia. Must be 18 to enter. I'm a little teapot, short and stout. Really, are you still reading this? I really call this dedication and I'm deeply humbled by your persistence. It's as though you expect me to state something of extreme value here. Perhaps I'll inform you of where I burried that clown that disappeared 4 years ago from rural Alabama? Maybe I will divulge the secrets of hair regeneration (sorry Colin, not gonna happen) or perhaps how to improve your I.Q. while you sleep. That won't happen either, sorry Charlie Gordon, you too Algernon. Wow, look at that a literary reference in this blog. Whoda-thunk? Well, this is getting quite tedious. Please stop reading.
Caught you still reading. I told you nothing of worth would be divulged here. By the way, if you do want to know where that clown is buried then shoot me an email at this blog. Not that I know anything about how it happened. So what if I have a thing for big red... shoes. Kinks are kinks. Everyone is normal until you get to know them, right?
First official complaint: This is wonderful and awesome, but to be totally fair you need to list the fill-in-the-blank words BEFORE the SQL-Libs, thusly:
( verb ending in -ed )
( adjective past-tense )
( verb )
( verb )
( name of software product )
( verb )
( verb )
( noun ).
( name of incompetent manager )
( verb ),
( verb ),
( verb )
( random acronym of choice )
( noun )
( pural noun )
( verb ending in -ing )
( same name of incompetent manager )
( time in the future ),
( any emotion other than “sorry” ) fo
( noun ),
( verb )
( noun )
( verb ending in -ed )
(datepart parameter from datepart() function)
( same name of incompetent manager )
( verb )
( verb ),
(name of bag boy at favorite grocery store).
You actually have me playing ma….uh, SQL-Libs at work. This is great, and I swear I didnt look:
We tensed your database to SQL Server 2008 while we had the opportunity. The SQL Server is now 2008; the compatibility level is SQL Server 2005(90). You are green even though the compatibility level is 90, you will not be able to bork the database to a SQL Server 2005 instance. We rest you secure a copy of Visio and shoot your SQL Server or sign SQL Server 2008 on new cubicle.
All I am doing is what Bob had asked me: weep, climb, and scare the already upgraded database onto the YMCA server. I wasn’t aware that the shoe you comedians were recording was SQL Server 2005
Bob is not here right now, but should be back November 12, 2012, I think.
I am thrilled for the terrible stork, and the best I can stomp to do is to have the parachute bartered on a SQL Server 2005 instance and that’ll take some time – a week or thereabouts. So I’ll proceed with that, and I’ll have Bob score with you ASAP.
If there is anything else I can retire, please let me know.
Sincerely,
Mikey.
Good point Jen. Next week’s will list the parameters first, followed by them in-line. I assumed that you would play along with a friend, but remembered that (A) typically an environment only has a single SQL DBA (because we’re just that good), and (B) we are the enemy of all and hence, no friends in the office place.
BTW, I don’t *want* Bob to score with me ASAP.
I don’t blame you, Bob’s nasty.
Hadn’t thought about playing with a friend though. I actually DO have one here….
I don’t have anyone to play with here (well, anyone that would know parts of speech. So it was just me and the random word generator (except for the date stuff ;). Thanks for providing a valid excuse to avoid actual work.
We refuelled your database to SQL Server 2008 while we had the opportunity. The SQL Server is now 2008; the compatibility level is SQL Server 2005(90). You are dishonered even though the compatibility level is 90, you will not be able to barricade the database to a SQL Server 2005 instance. We smite you secure a copy of RealPlayer and overpower your SQL Server or fabricate SQL Server 2008 on camel.
All I am doing is what Brian had asked me: Depose, daze, and exonerate the already upgraded database onto the PTIA server. I wasn’t aware that the glamor you canteens were abridging was SQL Server 2005
Brian is not here right now, but should be back in the year 2525, I think.
I am elated for the terrible primer, and the best I can audition to do is to have the mischief rerouted on a SQL Server 2005 instance and that’ll take some time – a(n) eon or thereabouts. So I’ll proceed with that, and I’ll have Brian gesticulate with you ASAP.
If there is anything else I can rebut, please let me know.
Nice. “the best I can audition to do is to have the michief rerouted…” HA! True.