<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SQL Server Express: Dev or Prod?</title><link>http://blogs.msdn.com/b/dtjones/archive/2010/12/12/sql-server-express-dev-or-prod.aspx</link><description>Most people I’ve spoken to have at least heard of the Express edition. The next question I ask is where they’re running it: development or production? The answer is usually both . But when I drill into the production use it turns out that most of the</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: SQL Server Express: Dev or Prod?</title><link>http://blogs.msdn.com/b/dtjones/archive/2010/12/12/sql-server-express-dev-or-prod.aspx#10113183</link><pubDate>Fri, 07 Jan 2011 23:08:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10113183</guid><dc:creator>Papy Normand</dc:creator><description>&lt;p&gt;Excellent article by a person who know Express Edition&lt;/p&gt;
&lt;p&gt;For the limits : 10 GB yes for data and indexes but with the use of Filestream, you may limited only by the drive ( to read and write Filestream data, it is not simple by program, but with some spent time, it is not a real problem ).&lt;/p&gt;
&lt;p&gt;The unique feature which might give problem is maybe the user instance which is not clear for many people.A good idea which will disappear maybe because it has not been used as the SQL Server Express team has foreseen it&lt;/p&gt;
&lt;p&gt;Anyway, i will have a look on your blog which seems really interesting&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10113183" width="1" height="1"&gt;</description></item></channel></rss>