<?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/"
		>
<channel>
	<title>Comments on: Q&amp;A: SharePoint Webinar and Whitepaper (Part 5)</title>
	<atom:link href="http://www.informationarchitected.com/blog/qa-sharepoint-webinar-and-whitepaper-part-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.informationarchitected.com/blog/qa-sharepoint-webinar-and-whitepaper-part-5/</link>
	<description>Information Architected is a consultancy focused on the intelligent use of content, knowledge and processes to drive innovation and thrive in a digital world.</description>
	<lastBuildDate>Thu, 22 Jul 2010 07:17:10 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Q&#38;A: SharePoint Webinar and Whitepaper (Part 5) &#124; Information &#8230; &#171; Social Computing Technology</title>
		<link>http://www.informationarchitected.com/blog/qa-sharepoint-webinar-and-whitepaper-part-5/comment-page-1/#comment-628</link>
		<dc:creator>Q&#38;A: SharePoint Webinar and Whitepaper (Part 5) &#124; Information &#8230; &#171; Social Computing Technology</dc:creator>
		<pubDate>Sat, 15 May 2010 03:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=363#comment-628</guid>
		<description>[...] post: Q&amp;A: SharePoint Webinar and Whitepaper (Part 5) &#124; Information &#8230;     innovation, knowledge, law-microsoft, strategy, [...]</description>
		<content:encoded><![CDATA[<p>[...] post: Q&amp;A: SharePoint Webinar and Whitepaper (Part 5) | Information &#8230;     innovation, knowledge, law-microsoft, strategy, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bradteed</title>
		<link>http://www.informationarchitected.com/blog/qa-sharepoint-webinar-and-whitepaper-part-5/comment-page-1/#comment-69</link>
		<dc:creator>bradteed</dc:creator>
		<pubDate>Mon, 06 Apr 2009 17:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=363#comment-69</guid>
		<description>So the important thing to remember is that the EBS (Extended Blob Storage) takes the content out of the database.  This makes the operational management easier to perform and content databases don&#039;t get large as fast.  There is no usability differences in this case.  Furthermore, many of the mainstream ECM vendors have integrated into the EBS API to facilitate the storage of the content directly into their Applications.  While it does complicate the architecture, it allows the typical &quot;storing blobs in the database&quot; complaint to be mitigated. 
 
Operationally, with native SQLServer tools, the &quot;best practices&quot; recommendation for content databases is 100Gb.  With enterprise tools, these databases can be much larger as it depends on the comfort of the support organization. </description>
		<content:encoded><![CDATA[<p>So the important thing to remember is that the EBS (Extended Blob Storage) takes the content out of the database.  This makes the operational management easier to perform and content databases don&#039;t get large as fast.  There is no usability differences in this case.  Furthermore, many of the mainstream ECM vendors have integrated into the EBS API to facilitate the storage of the content directly into their Applications.  While it does complicate the architecture, it allows the typical &quot;storing blobs in the database&quot; complaint to be mitigated. </p>
<p>Operationally, with native SQLServer tools, the &quot;best practices&quot; recommendation for content databases is 100Gb.  With enterprise tools, these databases can be much larger as it depends on the comfort of the support organization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Keldsen</title>
		<link>http://www.informationarchitected.com/blog/qa-sharepoint-webinar-and-whitepaper-part-5/comment-page-1/#comment-68</link>
		<dc:creator>Dan Keldsen</dc:creator>
		<pubDate>Mon, 06 Apr 2009 16:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=363#comment-68</guid>
		<description>Brad - ah, interesting, and not commonly known. The question at that point, however, is whether it actually makes sense to break apart management and storage - what you gain or lose by doing so. 
 
Any common scenarios that you (or anyone else reading?) see as far as SharePoint as management layer, and storage elsewhere? 
 
Have seen Documentum and Open Text in some scenarios - more from a records standpoint. Nothing else that I&#039;ve personally seen with our clients. 
 
Anyone else? What have you used for this separation of duties? And why? </description>
		<content:encoded><![CDATA[<p>Brad &#8211; ah, interesting, and not commonly known. The question at that point, however, is whether it actually makes sense to break apart management and storage &#8211; what you gain or lose by doing so. </p>
<p>Any common scenarios that you (or anyone else reading?) see as far as SharePoint as management layer, and storage elsewhere? </p>
<p>Have seen Documentum and Open Text in some scenarios &#8211; more from a records standpoint. Nothing else that I&#039;ve personally seen with our clients. </p>
<p>Anyone else? What have you used for this separation of duties? And why?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Teed</title>
		<link>http://www.informationarchitected.com/blog/qa-sharepoint-webinar-and-whitepaper-part-5/comment-page-1/#comment-67</link>
		<dc:creator>Brad Teed</dc:creator>
		<pubDate>Mon, 06 Apr 2009 16:10:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=363#comment-67</guid>
		<description>You state that SharePoint content must be stored in the content databases.  I believe it would be a more accurate answer to suggest that the content must be managed in SharePoint, through the content databases; however as of SP1, there are capabilities that allow content binaries to be stored externally 
 
:   Is it true that all documents must be stored into a database? 
 
A:  Yes, in order for the documents to be managed within SharePoint they must be stored in the  content databases. 
 
 </description>
		<content:encoded><![CDATA[<p>You state that SharePoint content must be stored in the content databases.  I believe it would be a more accurate answer to suggest that the content must be managed in SharePoint, through the content databases; however as of SP1, there are capabilities that allow content binaries to be stored externally </p>
<p>:   Is it true that all documents must be stored into a database? </p>
<p>A:  Yes, in order for the documents to be managed within SharePoint they must be stored in the  content databases.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/


Served from: www.informationarchitected.com @ 2010-07-29 16:47:03 -->