T-SQL Tuesday – Assumptions

pere cherche sa fille This is my first attempt at contributing to T-SQL2sDay. The topic of the month is Assumptions. 

http://miroironeline.com/?pridew=rencontre-celibataire-gratuit-sur-vierzon&e5f=62 Assignment – Write about a big assumption you encounter at work, one that people are uncomfortable talking about.

I work for a vendor and our application(s) don’t live on a single server but on many different servers. We have message boxes, SQL servers, application servers, and so on.

When we get a call/email about our applications being slow or timing out, we usually log into the server and try to take a look and see where the pain point is. A lot of the blame is usually put onto SQL or the application.

Here is where the assumption comes in.

As a database administrator working for a vendor who deals a lot with the support team, we assume that the hardware was specced out and properly configured. Many times during conference calls this unease topic comes up. Sometimes these conversations go something like:

“Your application isn’t working, it’s so slow. We keep getting timeouts”

“We might need to give it a bit more memory, my laptop has more resources than the database server”

It’s not a conversation a lot of people want to have but sometimes it really isn’t the application or it really isn’t SQL’s fault.

Many users of the system, the administrators, engineers, and executives all assume that all the magical hardware is the appropriate speed, size, etc. But is it really? Is your hardware adequate for what your application is trying to do?