Helpful hint for IT managers...

What's the hint?

Don't tell your SQL Server guy who, while new, *IS*, nevertheless, a genius, to start checking his work through someone whose only suggestions to date were

1) when a server's four processors were overloaded, stop using one for the busiest process

2) rather than setting up SQL to use all the memory it can, set it up to use only a specific amount, and

3) instead of getting decent performance out of four disk, set up 18 (!) disks for what is unlikley to be a major performance gain.

*ESPECIALLY* don't do this when your SQL Server guy wants to do NOTHING except BUILD A FEW FUCKING INDEXES.

(It is possible to have too many indexes, and a bad index is worse than no index, because each index slows down each record you add (because the index has to be updated with the new database record), but even a slow witted DBA who deserves the title DBA can handle adding indexes.)

I'm not really upset; I think I'm just low on patience, and tired, and over-busy because there's too much crap going on in my life right now.

(In addition to the database maintenance, I'm trying to write up docs for our backup procedure, trying to set up a new server, and trying to set up new services on our old servers)

But, for not being really upset, I'm moderately upset over this.

Helpful hint for IT managers...

What's the hint?

Don't tell your SQL Server guy who, while new, *IS*, nevertheless, a genius, to start checking his work through someone whose only suggestions to date were

1) when a server's four processors were overloaded, stop using one for the busiest process

2) rather than setting up SQL to use all the memory it can, set it up to use only a specific amount, and

3) instead of getting decent performance out of four disk, set up 18 (!) disks for what is unlikley to be a major performance gain.

*ESPECIALLY* don't do this when your SQL Server guy wants to do NOTHING except BUILD A FEW FUCKING INDEXES.

(It is possible to have too many indexes, and a bad index is worse than no index, because each index slows down each record you add (because the index has to be updated with the new database record), but even a slow witted DBA who deserves the title DBA can handle adding indexes.)

I'm not really upset; I think I'm just low on patience, and tired, and over-busy because there's too much crap going on in my life right now.

(In addition to the database maintenance, I'm trying to write up docs for our backup procedure, trying to set up a new server, and trying to set up new services on our old servers)

But, for not being really upset, I'm moderately upset over this.