Image storage: Database or File system? From my experience, storing images in a database is a lot easier to manage than storing them in the file system.
Here are a few of the benefits that I love the most: Related information is automatically kept in sync. It’s easier to backup your data when it’s all in one place.It’s easier to maintain an independent development environment.You can add additional file servers without having to deal with on-the-fly file replication. Of course, the classic argument against storing images in a database is that it is slow. Retrieving images from a database takes longer than retrieving an image from the file system. I decided to do a benchmark test for myself to see just how much of a difference it makes in performance. First, I created three different sized thumbnails of this picture and stored them in a directory on my file system.
Here are the results: File system Large – average of 7.87E-05 secondsMedium – average of 7.77E-05 secondsSmall – average of 6.65E-05 seconds Database Wow! Documentum vs SharePoint. I was looking for some info on how SharePoint stacked up against Documentum, and came upon Johnny Gee’s article titled Documentum vs SharePoint – Round 2.
First I wanted to thank Johnny for a great post and Eric Crone (of ForeFront Partners LLC) for a good comment that greatly expanded the post. I learned a lot about Documentum’s eRoom. However, I saw a few things that were not quite accurate from the SharePoint perspective. This post is my response to some of the points in Johnny’s article and Eric’s comment… Documentum vs Sharepoint – Round 2. I was planning to high-light the differences between Documentum and Sharepoint, but after coming back from EMC World, I was to very surprise to see that the lines between the two are quickly disappearing.
In fact, EMC was actively promoting their Content Services for Sharepoint. The proliferation of Sharepoint sites in the enterprise has driven EMC to address where Sharepoint and Documentum fit in the enterprise. Sharepoint (like eRoom) is great for collaboration. However, once collaboration is done, the information and documents stored in Sharepoint site are siloed from the rest of the enterprise. Since these Sharepoint sites are disconnected from the enterprise, there is no OOTB way to have users interact in enterprise business process. Even with these challenges, EMC recognizes that Sharepoint does have a place in the enterprise. Documentum vs Sharepoint – Round 3. You’ve asked for it, so here is a short-list of the differences between Sharepoint and Documentum: Sharepoint 2007 is tightly integrated with Office 2007.
Documentum has some light integration with Office through Webtop Application Connectors. Documentum has stronger integration with other authoring applications including Dreamweaver, QuarkXPress, and Adobe InDesign.Sharepoint provides various mechanisms to access and modify content when offline (eg Outlook, Access, etc). Documentum only supports offline editing if you install Documentum Desktop application.Sharepoint 2007 supports rights management with Office 2007 natively. Documentum requires you to install Information Rights Manager to have this feature.Both Documentum and Sharepoint provide the ability to create custom object types. Please feel free to comment on any other feature differences.
Like this: Like Loading... These are the Top 25 Microsoft SharePoint Influencers for 2012. How to Improve Speed in SharePoint 2013. You may also be interested in: SharePoint evolution conference 2013 Editor's note: Contributor Gokan Ozcifci is a SharePoint Consultant at Vision IT Group.
Follow him @gokanozcifci I feel like it’s always the same discussion about why SharePoint is slow, extremely slow. In previous articles, I explained how to perform with your environment or how to manage your environment. Recently, I received several calls from the Helpdesk that the search results were slow for the first time and that they had to wait one minute before seeing anything in the Search Center. If it’s not enabled, you can enable this under Application and Services Logs -> Microsoft -> CAPI2 by left clicking “Operational” and pressing “Enable Log”. After searching on what this event was, I found this on TechNet:“The Automatic Root Certificates Update component is designed to automatically check the list of trusted authorities on the Microsoft Windows Update Web site. Download the CRLs and add them to the server manually: