340 Views
I am a strong believer that a Developer should understand the databases and network he/she is interacting with. As a .NET Developer, having TSQL and SQL Server Administration knowledge to some degree of depth, really helps to design and develop your applications as well as communicate with the DBAs and admins you work with.
If a developer uses an ORM framework like Entity framework, is it still important for the developer to understand the TSQL fundamentals?
Personally, I don't think there's any excuse for a developer working with databases to not have a solid grasp of SQL as well as intimate knowledge of the database schema they are working with.
It's also possible to use the queries that were logged to do performance tuning on your database, using those queries as the workload file. It's very important to understand the design and purpose of your database when doing any sort of performance tuning, as it's possible the profiler may suggest deleting an index to improve write speeds, even though that index is very important for read performance. The profiler is only as informed about what your database is used for as what is in the workload file, and knows even less about the reasons for where to choose read speed over write speed and vice-versa when it comes to indexes.
hxxp://www.dotnetcurry.com/ShowArticle.aspx?ID=647