Comments for SQL Dumbass

Comment on Ask A SQLDumbass by SQL Dumbass » Ask a SQLDumbass

SQL Dumbass » Ask a SQLDumbass — Mon, 01 Mar 2010 17:38:39 +0000

[...] Ask A SQLDumbass [...]

Comment on BizTalk was Built by a Dumbass by Phil Factor

Phil Factor — Wed, 18 Mar 2009 04:15:53 +0000

I believe we all come out with the mantra that we should put the data and logs on different drives just to shut people up. Has anyone tested this, and proved that it helps performance? If so, is it really worth the effort?

Comment on Turbo Button by Chameau

Chameau — Tue, 05 Aug 2008 20:28:21 +0000

Hilarious. I think you could swap out DBA with programmer, manager, CEO...the possibilities are endless.

I think you need to add in additional columns for things like "willing to work each and every night and weekend".

Comment on Sadly, this is true by Chameau

Chameau — Tue, 05 Aug 2008 20:21:45 +0000

Sounds like we hit a nerve. Try not to take everything you read here at SQLDumbass personally. Most of the DBA's that contribute here are very helpful, even if you are an idiot. They will go out of their way time and again trying to help those that want help, but that still does not stop us from shaking our heads in disbelief.

I am certain not all DBA's are perfect, but I am also certain not all developers are either. At the end of the day, if you cannot laugh at yourself, then you need a vacation.

You should also understand that stories being related in a blog do not always come through as well as if they are told personally. In other words, if we were at the pub having a beer we could swap the same stories and you would not come away with the same feeling as if you had read the story on a blog.

It sounds as if you are frustrated with your current DBA, but I am willing to bet if you spent more time together you would develop a strong working relationship. In the case here, what you are not aware of is that this developer routinely shuns details. For example, after filling up the log once, they demanded that their database be put into simple mode in order to avoid the disk from filling up again. We tried to explain what is meant by simple recovery mode to which they replied "I don't need to know those technical details, just make sure the disk doesn't fill up again." Now, this is a developer that walks around proudly displaying their MCSD designation. Sorry, but what solutions are they certified to develop such that they do not have an understanding of transactions, recovery mode, etc.?

We are not asking them to know everything, only a fool would expect someone to know everything. What we are asking for is that they have a desire to learn things, to not be stubborn, and admit mistakes when they happen. And yes, the same can be said of DBA's.

Enjoy the rest of the stories. If you would like to contribute, let us know. SQLDumbass is about anything related to SQL, so it can be a post about developers, Microsoft, or DBA's. It doesn't matter, we just want to protect identities, but share some funny stories. If you want to rant about your DBA, then this is the place to do it.

So, don't get your knickers in a twist about what you read here!

Comment on Turbo Button by Lens Ton

Lens Ton — Tue, 05 Aug 2008 18:33:45 +0000

Yeah we get this kind of crap from our DBA’s all the time. optimising a query required specialist knowledge that programmers just do not come across, or get trained in. We positively avoid the DBA at our place, he’s just an ogre that STOPS anything happening, so there are all sorts of ways to bypass him in the chain of things, The boss knows this and insists on having the sa passwords, which he gives to developers at his discretion because he knows there will be no help from the DBA

Comment on Sadly, this is true by Lens Ton

Lens Ton — Tue, 05 Aug 2008 18:24:35 +0000

This is Typical DBA response to a genuine problem – just mock the guy who doesn’t have your specialist knowledge. The guy had probably given up asking for real advice from a DBA years ago. I can imagine how this went: Q.”Why does my logfile keep growing and using up all the disk space” DBA gives no help, but offers to ‘truncate’ it. Q.”After you truncated the log, how come its still taking up 95% of the space it did before” DBA gives no help. Q.”Can’t we just delete it” DBA – no can’t possibly do that. Then one day – the DBA is on holiday, another contract DBA does what we want – detach, delete logfile, reattach. it seems to have no deleterious effects – so it becomes the “standard” solution to when the logfile has grown too big – developer goes away happy. The next time it happens, Mr original ‘no help’ DBA is back.

Comment on I geta call from Microsoft today by BillyGates

BillyGates — Tue, 22 Jan 2008 23:24:51 +0000

Yeah – sorry about that – we really should have dba’s doing the phone calls for our surveys rather than some $8/hr kid with a clipboard. I will try to get that fixed for you.

Comment on Why is the systems so slow??? by Bocho

Bocho — Sat, 15 Dec 2007 00:55:24 +0000

I wish it were that easy. However, we have allowed the operations folks the ability to create these individual rules, set the priority, and tackle each one as a single event. Hit the db, report back. repeat.
So, they cant be done in a set based approach….

Best we can figure to do is profile the data, organize the priorities, and hope that the least amount of rules are executed before finding a match. And hopefully this will speed it up.

Comment on Why is the systems so slow??? by SuttungrsMead

SuttungrsMead — Sat, 15 Dec 2007 00:03:19 +0000

Oh that one is special. Tell me, out of 139 individual checks, how many of them could have just been added to the WHERE clause of the original INSERT statement?

Comment on Locked out by bocho

bocho — Thu, 29 Nov 2007 00:25:26 +0000

So, i take it from your tale, that you can have a user that’s not a sysadmin? i didnt think that was possible… all users should be sysadmins… makes security a lot easier… hehe