January 4, 2011 at 9:24 am
For those who do not know I am a 3 month old SQL DBA newbie. As a result I have been doing a lot of reading on best practices such as (seperate service accounts, seperating tlogs/tempdb, pre-installation setup procedures, HBA caching, offset alignment,etc). My company uses a lot of vendors who do not seem to be following these practices and from what I understand once SQL is installed its too late or becomes exponentially more difficult to the point where there is no way in hell i'd ever get support from my co-workers (network,storage,systems engineers) to fix/address these issues. How do I go about overcoming this?
Also, I know there is talk to install a new vendor supported application that will be using SS2008 and I feel like this would be a good opportunity to apply or make sure certain pre installation technics are used. However, I feel that is not going to be what happens. Advise?
January 4, 2011 at 10:09 am
Sometimes, with 3rd party software, you really don't have the option of making it be sane. Some of it, often from the biggest software companies, ones that really should know better, is beyond irrationality into the realm of just full-on psychosis, when it comes to complying with best practices.
So, in many cases, you do the best you can and then you live with it.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
January 4, 2011 at 12:13 pm
I'm with Gus. You follow every best practice you can, enforce them as tightly as possible, and then, when the boss says to throw them out the window because of the nifty new software package he bought... you toss them out the window.
Best thing you can do though is document WHY you're saying that you should or should not do something on the servers. Document the problems that the choices being made will cause. That way, when the problems start, you can point to the documentation and say, "I'll do my best, but as I said, this was going to happen when we violated X"
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2011 at 2:31 pm
I agree in both cases and responses above. My situation is similiar while coming into a position/place where the standards were minimal and the lack of that drives me to the edge. So you can look at the entire environment and slowly yet surely make changes in small chunks... ie.. new servers coming in (hopefully you can apply the best practices to those) and gradually work on the existing servers. Its not a situation that changes over night so knowing ahead of time that this is a long process that may or maynot ever be completed but at least you tried =] then when things go bad (hopefully not) you can go to your manager with a explaination of due to lack of standards it makes tracking the issues exponential harder to trace and hopefully using the thought process of looking at the failed opportunities to better your chances of "standardizing" your environment...Good luck =]
DHeath
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply