>>>
>>
>>I have to say if I was in your position I would do exactly the same. I think making changes to table structures just depends on the change and use in the application but would of course not always require an application change. Thanks for the input from your position and I agree. Stored procedures have always been a good idea but I am going to weigh this against EF. There are times of course where an application uses SQL Express data and there is no other access or use to the data where maybe it would be acceptible to skip the stored procedures assuming that does make it easier.
>>Thanks
>>Tim
>
>But, when it is LinqToEF would it matter? Same thing, you could use SP or not and still your code doesn't change. IOW you could do today without SP and then decide to use SP. Your Linq powered code would still be the same (you only update your EF model).
>Cetin

Excellent point Cetin! However if I was a DBA and responsible for the data I would most likely take the position that William indicates. That just adds that layer of protection between anyone else's access and my responsibility. But since I am not in that position, I am going to pick what makes the most sense. Your point is excellent because there is the EF layer between the application and the data.
Tim