Archives
- May 2018
- December 2016
- October 2016
- September 2016
- April 2016
- March 2016
- February 2016
- January 2016
- November 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- October 2014
- September 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
.net
appfabric
backup
BCS
beads
best practice
best practices
blog
blogs
books
c#
cache
Capacity planning
claims
Content Editor Web Part
cu
deployment
Diagnostics
Dialog
dialog framework
dlr
ECB
EWS
features
InfoPath
infopath2010
jQuery
license
Margriet
Margriet Bruggeman
maxer
migration
Monitoring
mvp pattern
Nikander
Nikander Bruggeman
NTFS Alternate Data Streams
Office 365
office365
Parallel
patterns and pratices
Performance
Performance counters
PerformancePoint
planning
Powershell
pps
rbs
REST
SAML
Search
security
service pack
SFWR
sharepoint
sharepoint2010
sharepoint 2010
sharepoint2013
sharepoint 2013
SharePoint Online
Silverlight
spd
spmetal
ssharepoint2010
SSRS
testing
Tools
tpl
upgrade
video streaming
wcf
whitepaper
wiki
WPF
xbap
Thanks for the post and the question about TITUS Metadata Security. I’m a Microsoft SharePoint Server MVP (1st time this year) and the product manager for TITUS Metadata Security. Yes, based on policies that administrators or site and library owners author with the product, TITUS Metadata Security can automatically apply item-level security to documents or any items in SharePoint, based on metadata related to those items or based on claims associated with users. As well though, the product can apply security permissions to folders and document sets as well. These features are very useful for our customers in the government, military and large commercial space when they have sensitive or confidential documents, mixed with non-sensitive documents in the same library. Or confidential folders mixed in the same library with non confidential folders.
Of course, you need to be careful with how far you take item level permissions in libraries in SharePoint because there are thresholds around item-level permissions in SharePoint. However, these thresholds are actually higher in practise than most people realize. We’ve worked heavily with Microsoft and our customers on this to demystify the thresholds around item-level permissions. In fact, in the last issue of the Dutch Information Worker User Group eMagazine (a great publication) an article that I wrote was published on this exact topic – Effectively Managing Permissions in Microsoft SharePoint 2010 which can be found here: http://www.diwug.nl/e-magazines/Pages/default.aspx. This will help your readers understand some of these thresholds around item-level permissions in SharePoint 2010 much better.
Since the time of writing that article we at TITUS have done meaningful performance testing of SharePoint 2010 with Service Pack 1 and the latest cumulative updates (Aug 2011 or later). We have found that performance on large libraries with many unique permissions has been improved significantly once upgraded service pack 1 and the latest updates. The SharePoint limitations/thresholds in this regard have not been removed entirely, but we have found that the threshold at which performance degradation starts to occur is an order of magnitude higher than previously. We have confirmed these findings with members of the Microsoft SharePoint development team. In confirming this, the team also mentioned that they were not altering their public guidance because they are completely focused on wave15 so we have not seen any official articles about it.
Overall, we’ve found that individual libraries with 50,000 to 60,000 items breaking inheritance from their parent library is now quite acceptable from a performance standpoint. This was confirmed by several of our enterprise customers in the field as well. This is of course dependant on server architecture, but we did see the before and after effects of the upgrade have a dramatic performance improvement in these cases.
Hope this helps your readers.
Antonio