<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: LINQ to SQL problems</title>
	<atom:link href="http://freekleemhuis.com/2008/03/26/linq-to-sql-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://freekleemhuis.com/2008/03/26/linq-to-sql-problems/</link>
	<description>SoftWear 'n Tears</description>
	<lastBuildDate>Fri, 13 Nov 2009 03:42:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: SamCPP</title>
		<link>http://freekleemhuis.com/2008/03/26/linq-to-sql-problems/#comment-114</link>
		<dc:creator>SamCPP</dc:creator>
		<pubDate>Fri, 13 Nov 2009 03:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://freekleemhuis.wordpress.com/?p=36#comment-114</guid>
		<description>&quot;Why are people so fond of stored procedures? In most stored procedures that I review there’s way too much business logic, and no kids, that’s not the right place for it.&quot;
Another point of view is it is the perfect place for it. If you use SPs as the interface to the database, you can guarantee database data integrity. If you run 2 versions of an application and one applies old database relationship rules and the other applies the new, you have database integrity issues. Stored procs are the perfect way of policing the use of the database. And from a security perspective, you can lock the database down at object level.</description>
		<content:encoded><![CDATA[<p>&#8220;Why are people so fond of stored procedures? In most stored procedures that I review there’s way too much business logic, and no kids, that’s not the right place for it.&#8221;<br />
Another point of view is it is the perfect place for it. If you use SPs as the interface to the database, you can guarantee database data integrity. If you run 2 versions of an application and one applies old database relationship rules and the other applies the new, you have database integrity issues. Stored procs are the perfect way of policing the use of the database. And from a security perspective, you can lock the database down at object level.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
