- Thanks received
- 16
Way back in the olden days, programmers designed queries, not DBAs.
some of us are dedicated database developers, having said that, after a certain point knowledge of how to be a DBA is important as you need to know what is happening under the hood to really get the most out of a database.
Indeed, writing good SQL requires being able to think in terms of interacting sets of data rather than repeatable actions.It is a different skill to designing code.
Many a time I've rewritten other peoples code to remove cursor loops which although functionally correct are very inefficient and go against the whole ethos of SQL query writing. Typically a stored procedure which uses a cursor and takes 10 minutes to run can be rewritten as a single query which will run in a fraction of a second.
I should hope so!Do they still teach students stuff like 3NF at college?
It really is worth learning the basics of how indexes work and how to read a query execution plan - it will make a huge difference to how your queries run.


