Tuesday, May 19, 2009

Go Bother Ballmer

You have a car. The engine is knocking. It gets shitty mileage. It takes 40 seconds to get up to speed after stopping at a red light. All of a sudden you hear a bang and see a hole punched through the hood, the piston having been thrown. Do you then call Michelin to bitch about your problems? You do if you work for $PrivateFinanceAdvisors, with the logic that the tire company ought to be able to fix the problem that's causing the tires to turn too slowly.

SQL Server: Insufficient Memory Error

Insufficient Memory Error BPool: no remappable address found
Problem usaully resolves itself. When this error happens $YourBigApp users experience slow perf problem Sometimes SQL server fails over (this didn't happen today) This issue has been occuring for a while and it's random behavior.

One thing that it definitely isn't is "random", Sparky. The problem will completely disappear the instant you add the minimum spec'ed memory to the machine and move $OurBigApp off the fucking underpowered database server and onto a dual-proc box with more than 500MB of memory just the way we told you to eight fucking months ago.

I don't believe that memory is our problem we face. We need a solution to this error! $YourBigApp is too slow and databse failing over!

File a ticket with Microsoft and tell them they need to make SQL Server run your 380GB production database in under 100MB of memory. With what appears to be a 486 DX/66 processor.

I just dumped a fucking laptop last week which has more power than their rack-mount which is groaning under the strain of a SQL Server and a dozen enterprise apps. That DB server memory problem is clearly being caused by our software.

You know how this one's being closed: Seh. Venn. TEEN.

Labels: ,


Blogger greyrat pulled out a crayon and scribbled:

Oh come on! It's just a database!SQL Server ran just fine on this server when we bought it in 2000. And SQL Server is SQL Server! Regardless of the patches and service packs and other upgrades that have been applied! In fact, "upgrade" means that it should be faster, right? So it's clearly $YourBigApp! Escalate! Escalate! Escalate!

Sorry REC, I couldn't resist a cross-cross post.

19 May, 2009 15:51  

Post a Comment

<< Home

In compliance with $MegaCorp's general policies as well as my desire to
continue living under a roof and not the sky or a bus shelter, I add this:

The views expressed on this blog are my own and
do not necessarily reflect the views of $MegaCorp, even if every
single one of my cow-orkers who has discovered this blog agrees with me
and would also like to see the implementation of Root Cause: 17-Fuckwit.