Tips and Tricks to Growing Your SQL Server Estate from SMB to Enterprise Scale
Thursday, June 28, 2018 - click here to learn more
The Enterprise has embraced SharePoint technology and generates a large amount of data on the server. As disk space is consumed, at times, content size might exceed the maximum storage limit of a site collection. At such time when any user attempts to create/upload the content, there are probable chances of loss of data.
For such a scenario, SharePoint provides Locks which would prevent all users to make any kind of additions to the site collection. Not only that, but with proper privileges one could prevent users to change the content or even can prevent access to all users of the site collection. For our scenario, we would prevent all the users to add content to the site.
To do so in SharePoint 2010, open SharePoint Central Administration. Click on Application Management.
Click on "Configure quotas and locks".
Choose the appropriate Site Collection. For achieving our purpose, select "Adding Content Prevented" which would not allow any user to add content to the site collection.
The SharePoint Administrator can also use Windows Powershell as follows:
Go to Start menu -> All Programs -> Microsoft SharePoint 2010 Products -> SharePoint 2010 Management Shell.
At the command prompt type...
Set-SPSite -Identity "<SiteCollection>" -LockState "<State>"
...where <SiteCollection> will be the url of site collection and <State> will be one from Unlock, NoAdditions, ReadOnly and NoAccess.
Now try to add content to the site collection and you would face the below error.
We can respectively change the values of the locks depending upon the requirement.
- Use Locks to prevent all users from any kind of changes to the site collection.
- Use Locks event to prevent all users to access site collection at times like migration of servers, changing site hierarchy, performing backups, system upgrade and others.
Last Update: 2011-02-16
About the author
View all my tips