The ASP .Net 4 in C# and VB
book was great for me. It let me successfully complete my first web-based project, launch the next phase of my career, and should give me the tools I need for many more years.
I am starting a new project and have the great luxury of some time to work on the structure, plus a little experience to perhaps use this time wisely. I started looking at how the Microsoft Membership code works, and was thinking of writing T-SQL queries, coupled with C# Stored Procedure commands:
cmd.CommandType = CommandType.StoredProcedure;
I started reviewing the WROX book "Beginning T-SQL". The first thing I noticed is that the author mentions LINQ as a reasonable alternative for "small" projects. It's quite something to pick up a book on something new, and find the approach I've been using mentioned in Chapter 1. (Yes, I always read Chapter 1!)
This is an "intranet" application with less than 20 users. It's replacing an Access database of about 15 MB (after 5 years of collecting data) with a Visual Basic 4 front end. It's a pretty small application.
Here's my question. For this project, is there any real advantage to T-SQL, or should I just go down the road with LINQ? How about the next project after this one, which should have about 100 users and a database about 2 to 4 times this size? When do the advantages of T-SQL become significant? It's always nice to expand my took kit. But I don't want to over-burden these projects with complexity they don't need.