Launch week: the Season Pass & Fundamentals Week are 50% off — ends in 3d 23h 16mSee the sale

News & Opinion

Contest: Write the Scariest DBA Sentence (10 words or less)

Warm up your keyboard, it’s time for a contest.

The challenge: Write the creepiest sentence you can come up with. You get 10 words max.

An example to get you started:

Oh, I’m sure someone set up the backups.

The rules:

  • Enter as often as you like (here on the blog, in the comments for this post)
  • The contest will close on Thursday, June 4, 2015

The prize:

  • Bragging rights. That’s sublime all by itself.
  • One free license for Goat Simulator from Steam – we’ll send the gift certificate to the email address of your choice. ($9.99 value USD.) http://store.steampowered.com/app/265930/

Update…. the winner has been selected! We had tons of great entrants, but I had to pick a winner.

Honorable mentions:

5. “Microsoft has released details of new SQL licensing model.” … Dorsey

4. “I wrote a trigger to prevent duplicate inserts.” … Chris Bergin

3. “We just make everyone a sysadmin so it’s easier.” … John Nelson #2

2. “The server room is directly below the men’s room?” … ScalabilityDoug

And the winner of the bragging rights AND the coveted free license of Goat Simulator is:

1. “Please keep this pager on you at all times.” …Tim Cockerham

Tim, we’ve emailed you all the info to claim your prize.

Free, 3× a week

Get my new posts by email

Three posts a week, plus a Monday roundup of the best database news from around the web.

1,284 comments

    1. Came here to leave that exact message, and see you beat me to it, let alone with the first post. WINNER!

      (And note that I’ve been responsible for this once upon a time.)

      1. I feel like that’s a DBA rite of passage. “Deal with everyone having sa that really, really, really shouldn’t.”

    1. In spite of what many believe, TRUNCATE in SQL Server is fully transactional and can be easily rolled back.
      Try it for yourself… CREATE TABLE Foo(Col1 INT); INSERT INTO Foo(Col1) VALUES (1); BEGIN TRANSACTION; TRUNCATE TABLE Foo; ROLLBACK TRANSACTION; SELECT * FROM Foo;

      1. Coworker asked Brent about something (AO on Windows 2008, I think), the response was “you can pay me 20k to get it working, or just use 2012”

  1. Just write “Drop Database [DBNAME]” and press F5

    (True Story… Senior Dev joking to the Jr Dev… the Jr Dev executed the query… Was 1 week full of nightmares… And no backup to restore…)

  2. Just offline/online the database, it should solve our deadlocks….

    **cries a little, actually happened to me today…**

  3. Oh my god! DBA executed delete statement without where clause in production database and there were no proper database backups.

    1. Oops, more than one sentence. I’ll just make those semicolons… yeah…

      The bug deletes random rows; nothing important yet; no worries.

  4. Latest update keeps copy of entire database on user machines

    (true story! — was supposed to help concurrency)

  5. “Hey, we’dlike to link some tables froms Access so our CRM team can run reports during business hours, is that ok for you?”

  6. Your I/O is not only taking longer than 15 seconds some of the time, it’s taking longer than 1 second most of the time- you either need to spend 50k to fix this or move your 5TB database to a diffetent server.

    1. I love this one- I heard this exact thing once a long time ago in a job interview. I had a really hard time figuring out if they were serious or if it was a trick question and they wanted me to argue.

      1. I’d assume the latter and argue. If they were serious then they can hire you to fix their issue or you don’t really want to be working there.

  7. Your manager comes up behind you and says: “Sooooo, I was in production, and…we have backups, right?”

    1. I think you just triggered a flashback– I found myself huddled in a corner, rocking back and forth.

    2. We had a vendor – self taught – knew EVERYTHING. Decided to build a two column table. One called ID, the other called data. Data was VARCHAR (7936). It utilised six bespoke nested delimiters (weird ASCII characters). And by the time the CEO wanted us to write reports out of it, it had 6,000,000 rows…

  8. Hey Developer – can you help me please [insert *every* Dba responsibility here] – I don’t know how to do that.

  9. LAN Admin to DBA, Hey we just lost two drives in the Production server, Did you have backup. Huh!

  10. We don’t have money in the budget for hardware. Lets load test against the production instance.

  11. Email from a co-worker – “Where do we keep the sys database backups for production?”

  12. 1) just tick the checklist box, the backups are always fine.
    2) run it now and cancel if it passes 28 seconds.
    3) Is max-memory in GB?, Ive set production at 128.
    4) You forgot to highlight the where clause on that statement
    4a) Why are all of our customers called Mrs Griffiths?

    1. I have done 4/4a. Luckily just on a report server, but I write update/delete statements within comment blocks now so I can’t be that dumb again.

    1. I worked at this company.

      “The most important transactional process we have is on a SQL 2000 box. Don’t ever touch that box. Unless something is broken. Then restart SQL Services on it to clear the error.”

    1. Oops. Maybe better this way

      ““Boss, i granted the consultant YOU found online full access.”

  13. But it was only a store procedure with 2 or 3 “delete” sentences without a “where” clause, how bad could it be?

    1. Ugh. I know at least one University department that thinks a flat file is a database,

  14. This is from an actual coding standards doc:

    “All table reads need to use the hint “WITH (NOLOCK)”. “

    1. OH yeah. Had that one recently: “You know how we said we always copy your backups? Well, we haven’t the last 3 months. We’re working on it”

    1. I once had to write a trigger that used the OLE xp_’s to call a component (which I also wrote) that used a vendor API to charge the credit card in the inserted row.

  15. This one happened for real, I was the one doing the ask:
    “Where are our lifeboat VMs? Not responding to ping/mstsc..”

    Turns out they were deleted by an admin without any prior notification :D.

  16. Oy…
    why did I click “Notify me of followup comments to this thread via email.”?!

    Goodbye inbox

  17. No-One can connect to the accounting db, do you know where the server is….Check under Bob’s desk.

  18. ‘So your backup tool didn’t copy open files?”

    But most scary to me: “Yes, I’m sure…”

      1. I really wish that line was made up. 2 TB log for a db that hadn’t been backed up in almost a year.
        I cried.

  19. We don’t need foreign keys on our tables – it’s all handled within the application by the developers.

  20. We don’t need foreign keys on our tables, it’s all handled within the application by the developers.

  21. Application team asked me to give rights for user to access db…to save time, I gave DBO rights…

    1. First day on the job at major online retailer…

      “What happened to those orders we asked you to drop?”
      “I dropped them.”
      “They’re not here any more.”
      “I know. You told me to delete them.”
      “NO. In retail, DROP AN ORDER MEANS “SET IT TO READY TO SHIP.””
      “Oh. Huh.”

      Always know your jargon… AND the jargon of your customers.

    1. Hey, far be it from us to tell the company how it spends its money if we advise them on cost.
      I think I’d be a little bit giddy if my company said that to me.

  22. Have a delete statement and select “Delete From Table” to change it for a select statement, and press F5 unconsciously.

  23. True story, word for word, referring to a critical database during a live deployment, spoken absent-mindedly by the DBA as he concentrated on his screen:

    “It is not as much there as it should be.”

  24. Here’s an older one … SQL Server 7.0 goes down, and we are standing in the server room after having tried everything possible to connect to the instance from application, Enterprise Manager, etc. This is the statement from the VP of development at the time …

    “What do you mean MSSQL and Sybase can’t be installed on the same machine!!??”

  25. (DBA Wanna-be):well its right 99.9% of the time-its only 1% loss of data
    Real DBA: WHAT!! Ever hear of Data Integrity?

  26. On a web connected server: “Who put EVERYONE in the sysadmin role”? (unfortunately, this actually happened)

  27. The CEO wants to know who can give permission to query the tables directly

    Alternate

    So you think it’s a bad idea to develop against the same database on the production server and the development server at the same time?

  28. After a data center outage caused by a faulty HVAC …

    “Yeah, nobody checked the backup battery in the fail-over unit.”

  29. Vendor Meeting @ 3pm: Our software requires sysadmin rights.
    Vendor Meeting @ 4pm: Our software requires sysadmin rights.
    Vendor Meeting @ 5pm: Our software requires sysadmin rights.
    Vendor Meeting @ 6pm: Our software requires sysadmin rights.

  30. The hardware technology has finally caught up with our advanced application.

    Translation: The new servers are finally powerful enough to offset the crappy, inefficient architecture of our application.

  31. I noticed our Replicated Subscription articles haven’t been filling with new data for awhile….

  32. Me: So, why is this synonym created and discarded at runtime?

    Me investigating a peculiar issue : This vwLamas view does exist…as a table.

    Me…again investigating a peculiar issue: This tblLama does exist…as a view.

    Developer: So, I used float to store the decimal values.

  33. That database can’t be that important (or complex), the mdf file is only 1.25GB.

  34. Lets create all the indexes suggested by the Database Engine Tuning Advisor in development on production DB.

  35. We can’t afford for you to take time off.

    Setup our new ERP system in NoSQL.

    Setup our new financial database in NoSQL.

    Our new database server was setup in the hall way.

    Help our new IT department migrate the servers.

    The CEO’s son will be job shadowing you.

  36. All of the important data is stored in one table.

    Was it wrong to email that confidential list of data?

    Setup a data transfer to this state agency…

    We only accept faxes.

    What is that noise coming from the server room?

    A wild animal ransacked the server room.

    The server room is flooded.

    We’re moving all of our confidential databases to the cloud.

    We are moving everything to open source.

  37. Did I just ran the Delete statement of PRD instead of DEV?
    Did I just ran the restore statement of PRD DB instead of DR DB?

  38. I would like to mention a couple :

    1. We always backup to ‘NUL’ device.

    2. The load test config file had PROD server details – Did we do anything wrong ?

    Kudos for steering our a great discussion !

    1. Nothing like frantically covering your cabinets because the CEO’s private toilet overflowed. Couldn’t be sure the color of the water was due to fireproofing foam between floors or something a bit more disgusting. ????

  39. DBA actually said to me once:
    We should try to keep our CPUs at 100% so they aren’t wasting cycles

    1. Customer “IT-Architect” told me the same, “why are we not utilizing our processors to 100%, fix that”.

  40. Dev guy: “Could you please script out all objects from prod?”

    Yes that means he didnt have any idea what he deployed a few weeks ago …

    1. lol!! i worked at a company once that went public and bunch of folks were suddenly very well-off. People were very scared who was going to not show up for work again

  41. I checked the box to be notified about followup comments, and changed my mind after so many came in…I’ve tired suspending it and finally deleting it in your subscription manger, but it’s not working, I’m still getting emails. Can you do some behind the scenes magic and get the update notifications to stop!!!!????!!!! Please and thank you!!!!

  42. Promise this is my last one and I actually overheard this last week:

    “So it’s a SQL Server back-end with Access front-end” :o0

  43. don’t need a DBA to install SQL, just click ‘next’ — actually heard during a project startup meeting.

  44. The transaction log grows 40GB every month, so we just set the vdisk to 4 TB thin allocation. Should be enough.

  45. What do you mean the fire alarm test tripped the breakers for the computer room?!?

    – True story…

  46. When talking to a customer who is self hosting the software (which is their line of business\crm software) and the sql database has corrupted due to a power failure: “Backups? Doesn’t your software back itself up?”

    1. Yep – I’ve even been asked if we can just not patch the servers so the servers aren’t rebooted ever. The scary thing is that the business succeeded in that request for 6 months before someone just did it anyway. It was a cluster too, not sure why everyone was so worried!

      1. Sadly, that is my company’s standard policy.

        “We can’t afford to do OS or SQL patches. We can’t afford any downtime.”

        When I looked at some of my SQL servers for the first time, the OS was literally 3-4 years behind on updates. care to guess how long THAT took to patch?

        I’m just waiting for this boat to hit land!

  47. When referring to a public facing SQL server: “Hang on, I’ll just email you my password [from my personal email account]”

  48. “Our data loading process is to drop all indexes and foreign keys in the database, load the data and then recreate the indexes”

    1. My first gig as a database developer, the guy who I eventually replaced thought that was the ONLY way to perform ETL. Not only indexes and FKs but a boat-load of indexed views got dropped, data loaded, then about a 3-hour process to rebuild everything including the indexed views.

  49. Is that smoke coming out of the tape drive?

    and

    But I deleted the table BEFORE the backups ran!

    (Personally, I’m probably buying the goat simulator tonight, that’s just too weird! And I originally misread the title as Goat Stimulator, that’s a whole different game.)

  50. Cool! I found a flash drive in the parking lot!

    What does “Repair_Allow_Data_Loss” mean?

    Why is the Client table’s record count zero this morning?

    Why are there no tables in the payroll database?

  51. I didn’t know sp_Blitz could produce so many rows!

    SQL Server has service packs? (true story)

    Why is Celko turning so red?

    I got this script from a Russian web site!

  52. “We didn’t make any changes, but this replication is very slow today” – 6 days, 2 hours and 23 minutes later……..

  53. “Surely the DBAs can create a job to recompile that function every hour” – actual suggestion at a workshop concerning Server CPU Utilisation

  54. Out of curiosity – did anyone check the free space on the db server before we posted that question that got nearly a thousand comments?

  55. Once we upgrade to SQL 2012, we’ll be able to have an Active/Active cluster, and we can replace replication!

  56. None of our indexes has more then one field!

    (saw this really – PK on the UNID, idx1 on deleted, idx2 on created by, idx3 on the customerid … and this in the whole db in the hope that (SQL 2000 to 2005 (depending on the customer)) will combine all the single column indexes)

  57. “Why wasn’t the external storage on the UPS too?” (true story)

    Phone call from customer: “I made a booboo…” (thought the WHERE clause for the “DELETE FROM Customer” statement was a separate statement to run aftwards. Also a true story)

  58. Actual event:

    ” that’s funny. When I pull the cables from the test server, the lights keep on burning”

  59. The database is down! Where is the server?!?

    (A huge telecom company had a Sybase SQL Anywhere running an invoice system. It was found in a small storage room for papers, pens and stuff. It had stopped because logs filled all avaliable disk.)

  60. 1. I’m sure you’ll love working here…it’s always so busy.

    2. Get ready !! James Bond’s infiltrated the base !

    3. Remember ‘Drop database good, drop table bad’

    4. Grant Fritchey is coming to audit the databases…..

  61. Actual event:
    ” That’s funny. When I pull the cables from the testserver, the lights keep on burning”

  62. I scheduled job to shrink log file every 10 minutes.
    Nothing on the internet says it’s bad practice.

  63. ” Not really sure what this “SP_OLAPDance_AnaLZR” did, but I am pretty we are gonna need a really good PROC to fix it?

  64. Text files? Just dump your debug text into a column.

    (We discovered this little vendor gem when Replication started choking on a row with 2+ GB of text in a single column.)

  65. I thought of another one that I don’t think has been mentioned yet.

    “Good news, you’ve been promoted to manager!”

    soon followed by

    “Unfortunately we’re unable to backfill your role at this time.”

  66. I thought a clustered index was only used in a Windows cluster, why are we using it on a standalone server?

    1. What would have been scarier to say is… some guy in our company said… “I’m the Data Scientist.”

  67. A struggling small company let the IT hardware guy go without assigning duties to anyone else. I was the report writer and this is what I heard when I walked in one morning:

    “I got in here early this morning and there was an alarm going off in the server room that seemed to be coming from the AC system so I flipped the breaker for it and closed the door to keep the noise down.”

    That company is no longer in business.

  68. true story from team member – i restarted the db, it’s recovering, 4 day estimate.

  69. There was a restored db (we’ll call it test) on a production instance… this is from IT Director.

    “Run the query on TEST, should be done by tomorrow.”

  70. End users have SYSADMIN rights on production.
    (True story – this is 3 years later and can’t get it changed)

  71. Change directly in production, copy the DB to test.
    (That was the change control proposed)

  72. What do you mean you won’t give that vendor sysadmin to the production Server ? They say they require it to install the latest version of their software! And no, we did not test this, they are an international company …
    (true story)

  73. I have a few of them that popped up in my head right away

    Situation: All hell broke loose
    Sentence: Are you sure you dropped the TEST database

    Situation: Vendor comes to install product
    Sentence: Just make the service account sysadmin, that way it works

    Situation: Me asking the former DBA why the SQL 2000 servers are the RTM versions (its 2015 now)
    Sentence: Oh we didn’t have time to update the servers

    Situation: A developer made an adhoc change and wants to deploy it
    Sentence: Oh sure just deploy right into production without testing

    Situation: All hell broke loose version 2
    Sentence: I’m sorry the last good backup is 4 weeks old

    Situation: Missing disk on production cluster
    Sentence: I’m sorry I deleted the wrong LUN

  74. “These features are scheduled to be removed”

    — I tried to think of the 10 word authored by MS itself.
    Mirroring and Trace come to mind. I’ve got AGs down but I am so attached to SQL Trace/Profiler etal. I just resist Extended Events.

  75. Tge phone rings, the GM is on the other end of the phone and says, hey did backups complete last night? Hood, then can you come to my office? Oh, and on the way, grab the tapes and bring them with… minutes later, after arriving at the Casino GM’S front office, he appears with a rather large police presence. Curious, I ask what’s up and the Sherri informs me of the bomb threat we just had. Apparently it was supposed to be located in or near the boiler room adjacent to the server room. It took me a few moments before I realized that we took our time gathering tapes, then we realized we were asked to gather tapes… not just get the hell out. Well, we know where his priorities were.

  76. Priority- 1:
    Hey DBAs, We are having timeouts. Please do the needful.

    *and then this person never replied after you start asking questions*

  77. From the SQL developers:
    No, we fix everything directly in prod, we don’t have time to test!

  78. After initial, deep review of production OLTP financial database, which fed every other database in company, I had to meet with CIO to let him know that there was close to 60% data corruption. His response? “In my opinion, accuracy is overrated…”

  79. My SAN can handle 200K IOPS, far from your poor 500 IOPS, so do not complain about latencies, this is not a problem, and please do not make IO that size more than 4KB if you want good performance.

  80. That scripted change you ran had a DROP and CREATE.
    Also true story. Scripted change from dev being put into production. Dumped ALL of the data out of the table 🙂 Followed shortly by my previous entry

  81. All true stories i’ve come across as a DBA.

    – “We have backups!…from 2013….”
    – “we can’t remember the SA password, but all jobs depend on it”
    – “we changed the SA password, now we can’t get in”
    – “let me get back to you about this query… i’m still waiting…”
    – “The backup tapes are…empty ”
    – “disk is full, let’s shrink the log files”
    – “what’s wrong with 100 joins in a joins, I made it easy to the eye.”
    and my favorite
    -“you’re the DBA, make it run faster!”

  82. “We host production, acceptance, test and development databases all on the same server instance here”

  83. from developer…
    I’m not sure what is causing the problem. Can you look through my code and see if you can find it?

  84. The server is upstairs, in the loo.

    True story, unfortunately. Conversation was between the local manager and the corporate CIO. Server was relocated posthaste.

  85. We’re going to be hiring an additional DBA to offload some of your extra work, can you recommend what training classes we should send them on to learn about database administration?

  86. Script sent from a dev (true story):

    Delete from Orders
    Select * from OrdersHistory
    where Date <'12/31/2012'

  87. Give the end users full admin rights, we trust them.
    (That’s the CIO at a former company in 10 words too! Wooo-Hoooooo!)

  88. “There are no SQL Server DBA’s out there!”

    Statement actually made to me by my clueless former CIO while pointing out the window and asking me if I knew how many SQL Server DBA’s were out there!

  89. I was testing out this truncate script but forgot to change the server to test which began truncating all of the production tables as I stepped out to lunch…

  90. Vendor: “Whenever that happens just reboot the SQL Server.”

    This was how one of our third party software’s help desk suggested fixing an error within the application.

  91. Manager for a related helpdesk: “We need you to take calls from the [Customer Service Helpdesk] queue.”

  92. In Production, I implemented a SQL Agent job to truncate Error Log every five seconds.

  93. “I believe it is working.”
    “We are having some issues with the backup software.”
    “Don’t worry about it, we take OS-level backups.”

  94. I’ve got 2 here:

    from dev: “we want to do data encryption using CLR”

    from SAN admin: “the RAID 10 array has 2 physical disks in it”

  95. I went to restore that database from last week and realized the SQL Agent had been stopped for the last 2 months…no wonder I wasn’t getting notifications from that server.

  96. “8 Node SQL Cluster is down” DBA-Node name??..L1 –Next update in 30mins”

    This is really scaryyyyyyy……

  97. “I prefer Count Star to Count Dracula, because I don’t like having to consider which Draculas are NULL.”

  98. “I don’t see anything better in SQL Server 2012 than what we currently are using in SQL Serer 2005”

  99. We need to hire (Consulting hours will not be sufficient) folks from Brent Ozar Unlimited to fix these issues!

  100. The Production database just went offline! Did you unplug the external USB drive from that computer?

  101. “Oh, I saw that CXPACKET were top 1 waitstat so I just changed maxdop to 1 to optimize performance on the production instance ! :)”

  102. Run this for me real quick in production:
    UPDATE hugeCriticalTable SET colName = CASE WHEN colName = ‘value’ THEN ‘newValue’ ELSE colName END

  103. “Yep, the backup tapes should be fine. We keep them in a fireproof safe in the server room” — the IT Director said after his server room burned.

  104. I have two entries. In general:
    “ooops”
    and in the DB-world:
    ” Hey guys, how, em, do I undelete a table?”

  105. Replicated prodution to test, without changing vendor PO mail addresses.

    (true story… vendors started calling to verify they really needed that order 5000 times)

  106. True story. This was said to me by the VP of engineering with no further context.
    “I need an analysis of our database”.

  107. I heard 4 out of 5 at my last job, makes me glad I left. There was a plastic lined box on top of the mainframe in the data center because the bathroom directly above it had leaked

  108. Put this on my resume? Why would I even need a resume? They LOVE me here! Luckily I saw this in between meetings about Sql Server licensing costs and reducing developer privileges.

  109. I promoted the TEST Db to PROD.

    (Yep, another true one, the numbnut next to me informed me that is how he promotes his changes…Jesus wept)

    1. Yes! The post is updated way up above. I realize that once you get down here in the comments it’s hard to notice that though 🙂

  110. http://bit.ly/1CwxYNI

    Ivan Krechetov ?@ikr wrote “Never let a colleague’s vacation go to waste. Act now! Rewrite everything!”

    And he didn’t even know he was entering.

    Matt Velic ?@mvelic replied “Oh, the coworker is that DBA you don’t like? DROP all the databases to make their vacation more interesting. ”

    Neither did Matt.

    My entries: “Look what we did on your vacation!” or “We had a slight problem while you were gone.”

  111. “Why’s it doing that?” – I overheard our our Junior DBA saying that while he was working in production, bout gave me a heart attack.

  112. Everything here runs as \admin. You can’t change the password because it’s hard coded in most of our production applications.

  113. Database has corruption! So is the database down, no, then let the business continue processing while you fix it on the test environment.

  114. There was no change to the proc but its started failing suddenly… well we just added CTE only but that shouldn’t cause anything…

  115. #1 – Backups? I’m not responsible for those.
    #2 – Why would you use compression? Doesn’t that make it slower?
    #3 – The SQL account has had domain admin access for the last 10 years – we’re going to change that – but we’re not sure if anything will stop working…

  116. This actually happened to me. The CTO of my company was working in the data warehouses on the weekend. He calls me up and asks, “Quick question: does Linux have a recycle bin like Windows?”

  117. Since this is super old and no one will read it.

    “We backup to tape!”

    The reasoning:
    No magic dust in those words so nope, no magic fix.
    Usually rotate the same tapes.
    They have used the same tapes for years to save money.
    No one checks the tapes for hard read errors.

    Further thoughts:
    It was not configured using the proper Microsoft way so they will not troubleshoot it till the end.

Leave a comment

Your email address will not be published. Required fields are marked *

Email me about new comments: