kevaburg (6/20/2013)
Einstein once said: If you can't explain a subject in simple terms to a layman, you don't know enough about the subject yourself.Your DBA has mastered that concept and is the DBA every company "should" have. But then, I am sure he keeps himself abreast of developments, makes sure those less skilled have the answers to questions they need in a manner they can understand and realises the importantance of continuation training. That guy deserves that pat on the back but then companies that have that sort of professionalism take it for granted and reason that "he is only doing the job he is paid for".
Easy to use software, less complex practices, the ability to say "well, it isn't my job anyway": What ever happened to good old-fashioned workplace-pride and standards where the individual knew what needed to be done and simply did it?
(Disclaimer: Not in a good mood this morning and feeling very cynical....)
I can relate to that final sentiment after flying all night to the UK 🙂
I only quoted one of your replies, but I'd like to address them all here. I do appreciate your view, and I agree with it somewhat, but it's not as simple or straightforward as you note.
I do agree that people working with SQL Server should strive to understand more and improve their knowledge of the platform they are responsible for. However asking for better tools doesn't preclude that. We are all on a journey from beginner to expert, and at a point in time we are somewhere along the way. Plenty of developers, Windows (or Exchange/Sharepoint) admins, or others are tossed into the pool with their initial responsibility for managing a SQL Server. The platform should help support them, and also teach them. It's one of the reasons I try to always encourage people not to click "OK" in SSMS, but use their little friend[/url], the script button. I do that constantly to learn more.
However let me ask you this. When I started working with SQL Server, we had to track the growths of our database files. The reason is that when we restore a backup to a new database, we had to create the segments in the right size and right order. That required some knowledge, but it was a little silly to ask humans to do this when software could. SQL Server evolved so that it would manage this process itself. It also evolved in SQL Server 2012 to automatically build the "WITH MOVE" statements to the default file locations with a checkbox in the restore dialog. Is that addition, which is incredibly ergonomic, and long overdue (IMHO), a "dumming" down of the tools? Or is it something that helps the ignorant and eases the workload of the expert?
I disdain the need for this tribal knowledge, like knowing the maintenance plan log is needed, not the job history log. To me this isn't the sign of an expert, but someone that's encountered a flaw/bug/issue in SQL Server's toolset and knows to skip by this.
Making tools better, and easier, to me, is a way to ensure the platform is more efficient, and doesn't waste one's time, beginner or expert.
Probably should have written more of this in the editorial. My apologies for not clarifying things better in the piece.