<?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>To FILESTREAM or not to FILESTREAM... That is the question.</title><link>http://blogs.msdn.com/b/zowens/archive/2008/03/03/to-filestream-or-not-to-filestream-that-is-the-question.aspx</link><description>Roger and I have been delivering a demo which highlights Spatial and FILESTREAM features of SQL Server 2008. One of the common things we've heard from developers is... For years we've been told that large binary files should never be stored in the database</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: To FILESTREAM or not to FILESTREAM... That is the question.</title><link>http://blogs.msdn.com/b/zowens/archive/2008/03/03/to-filestream-or-not-to-filestream-that-is-the-question.aspx#9589064</link><pubDate>Tue, 05 May 2009 18:38:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9589064</guid><dc:creator>ZachSkylesOwens</dc:creator><description>&lt;p&gt;Clement,&lt;/p&gt;
&lt;p&gt;That's an interesting perspective... &amp;nbsp;Which features are you referring to that aren't available when using FileStream?&lt;/p&gt;
&lt;p&gt;FileStream isn't really targeted at avoiding the need for a file server... &amp;nbsp;It's all about managing binary data alongside relational data when consistency and manageability are important. &amp;nbsp;Building a content management system is a classic example where developers have had to decide to store the binary data in the database or out in the file system with a pointer to its location stored as text in a table. &amp;nbsp;Maintaining consistency is then up to the application which isn't always a viable option when it comes to database backups, restore, etc.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9589064" width="1" height="1"&gt;</description></item><item><title>re: To FILESTREAM or not to FILESTREAM... That is the question.</title><link>http://blogs.msdn.com/b/zowens/archive/2008/03/03/to-filestream-or-not-to-filestream-that-is-the-question.aspx#9589062</link><pubDate>Tue, 05 May 2009 18:38:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9589062</guid><dc:creator>ZachSkylesOwens</dc:creator><description>&lt;p&gt;Clement,&lt;/p&gt;
&lt;p&gt;That's an interesting perspective... &amp;nbsp;Which features are you referring to that aren't available when using FileStream?&lt;/p&gt;
&lt;p&gt;FileStream isn't really targeted at avoiding the need for a file server... &amp;nbsp;It's all about managing binary data alongside relational data when consistency and manageability are important. &amp;nbsp;Building a content management system is a classic example where developers have had to decide to store the binary data in the database or out in the file system with a pointer to its location stored as text in a table. &amp;nbsp;Maintaining consistency is then up to the application which isn't always a viable option when it comes to database backups, restore, etc.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9589062" width="1" height="1"&gt;</description></item><item><title>re: To FILESTREAM or not to FILESTREAM... That is the question.</title><link>http://blogs.msdn.com/b/zowens/archive/2008/03/03/to-filestream-or-not-to-filestream-that-is-the-question.aspx#9584603</link><pubDate>Sun, 03 May 2009 16:16:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9584603</guid><dc:creator>Clement</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I do not see much good in Filestreaming or maybe for small companies, to avoid to deal with file server, San and all.&lt;/p&gt;
&lt;p&gt;I see so many features that are not available when using filestreaming...&lt;/p&gt;
&lt;p&gt;SQL server should handle data, not files!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9584603" width="1" height="1"&gt;</description></item><item><title>re: To FILESTREAM or not to FILESTREAM... That is the question.</title><link>http://blogs.msdn.com/b/zowens/archive/2008/03/03/to-filestream-or-not-to-filestream-that-is-the-question.aspx#8344925</link><pubDate>Mon, 31 Mar 2008 05:54:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8344925</guid><dc:creator>David</dc:creator><description>&lt;p&gt;Correction - Make that ADO.NET Data Services/Astoria for Q3...too many data services to keep track of these days. :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8344925" width="1" height="1"&gt;</description></item><item><title>re: To FILESTREAM or not to FILESTREAM... That is the question.</title><link>http://blogs.msdn.com/b/zowens/archive/2008/03/03/to-filestream-or-not-to-filestream-that-is-the-question.aspx#8344906</link><pubDate>Mon, 31 Mar 2008 05:31:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8344906</guid><dc:creator>David</dc:creator><description>&lt;p&gt;Hi Zach,&lt;/p&gt;
&lt;p&gt;To add to the questions you've addressed here: Will we be able to access FILESTREAM blobs through 1) the Entity Framework, 2) LINQ to Entities and/or 3) SQL Server Data Services? &lt;/p&gt;
&lt;p&gt;If 3) is true, then &amp;quot;the concept of OpenFile(&amp;quot;C:\Path_To_My_File\File_Name.docx&amp;quot;)&amp;quot; would be baked in, no?&lt;/p&gt;
&lt;p&gt;Lastly - if so, when?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;David&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8344906" width="1" height="1"&gt;</description></item></channel></rss>