Every .NET Developer Should Know Their Database Well Enough(sqlservercurry.com)
sqlservercurry.com
Every .NET Developer Should Know Their Database Well Enough
http://www.sqlservercurry.com/2011/08/net-developer-database-knowledge.html
8 comments
Other than understanding SQL I think the #1 issue for most developers is understanding database preformance. The most basic understanding of indexes and how the database parses commands goes a long way.
PS: If you don't understand the value of 'Explain' or your local databases equivelent then a day or to is all it's going to take to save yourself from a world of pain.
PS: If you don't understand the value of 'Explain' or your local databases equivelent then a day or to is all it's going to take to save yourself from a world of pain.
Article assumes that a .NET developer will only be connecting to a MS SQL Sever database and not a third-party database like Oracle, Postgres or SQLite... Other than that it's not a bad article except the number one problem I see among developers that don't understand SQL Server is how and when to use indexes.
A related problem is developers who do have a decent understanding of SQL Server then going to something like Oracle and thinking that all their best practices are still correct. You not only need to know about database generally, but you need to be familiar with how your SPECIFIC database works and how it's different from others you may have used.
I agree to xradionut. The article has good information but only a couple of index related links. The how, why and when of indexes will complete the article
Surely every programmer should know their database well enough?
Or even "Surely every X should know their Y well enough".
Or even "Surely every X should know their Y well enough".
I think the same goes for a DBA too (unless very specialized and handling TB's). Having basic C# knowledge helps a DBA and with CLR based programming, it is recommended too.
Especially if they are using an ORM ironically.
If you consider NHibernate, a lot of time working with it is spent optimising criteria queries to ensure that the IO and CPU on the DB server are not spanked to death and that the loading strategy keeps the read count down.
If you consider NHibernate, a lot of time working with it is spent optimising criteria queries to ensure that the IO and CPU on the DB server are not spanked to death and that the loading strategy keeps the read count down.
One thing I've discovered over the years is that most .NET programmers - even seasoned ones with good programming knowledge - don't know squat about databases. In fact, I believe that's why so many programmers jump to something like Linq or NoSql, not because they think it's the best choice for the job, but rather because they simply don't understand databases.
It's my opinion that if you can't do most of your data manipulation in your data layer, and you really understand SQL (which is, quite frankly, cake compared to any other programming language except HTML), you are missing a huge chunk of knowledge that you really should have.