| Quote: | |  | |
| Most serious DotNet projects require access to the database and so a good knowledge of database suff is important. If I was interviewing you, you could expect at least 40% of the interview would be DB stuff, 35% DotNet specific and say 15% for deployment issues. Leaving 10% for general stuff.
Best Regards,
Jim. | |
| | |
Oh, I'm well aware of the kind of database stuff you need for a data driven .Net web application. I've been programming MS Access for 11 years, Coldfusion for 7, .Net for 2 and been a network admin for 3 also. I'd like to believe I know T-SQL fairly well, can write stored procedures and triggers, familiar with data architecture design, table normalization and all that but I don't believe I need to know how to do performance optimization and tuning of a SQL server box. If I have to do that than there is something wrong with that IT department. We have our DBAs for the admin tasks and hire consultants for tuning our server farms. You don't do that sort of stuff on a dailiy basis.
Anyways, I agree with your percentages but for DB stuff not DBA stuff. I think there is a difference.