November 1, 2008 at 5:51 pm
Comments posted to this topic are about the item Dead LINQ - Database Weekly (Nov 3, 2008)
June 12, 2009 at 2:31 pm
I originally posted this here (http://www.sqlservercentral.com/Forums/Topic734068-361-1.aspx), but this seems like a better place for it...
Developers at my workplace are pondering use of LINQ for their upcoming projects.
How much should I, as a DBA, be worried about this?
From the little I have read about LINQ, it seems like it makes life very difficult for DBAs who are in charge of controlling database access, monitoring database performance etc.
LINQ facilitates the use of ad-hoc queries in application .NET code, something that flies in the face of MS best practice recommendations about using stored procedures to run T-SQL code.
In the face of determined developers, what can I, as a DBA, do to reduce the risks (security and performance-related) that will come from use of LINQ in application code?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply