October 26, 2008 at 8:39 pm
I certainly can, and will. Give me until tomorrow, or perhaps the next day to provide an example of what I am talking about, and maybe find the right BOL entries to support it as well.
LINQ isn't my strong point, but in order to object to its use against SQL Server, I felt I had to at least know a basic amount of how it worked, so I played with it a few months back. I like LINQ to entities a lot, and am a big fan of that, just not LINQ to SQL. I can't get past the lack of security that comes with something having direct access to my tables. I know LINQ to SQL can use stored procedures, but at the point that we did all the work to bring them into LINQ the way I would want them used, we removed the point of using LINQ to SQL which is rapid development.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
October 26, 2008 at 9:58 pm
Thanks, Jonathan
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply