Tag Info

New answers tagged

0

Shrinking the Database is not big problem, we had issue in past where a content DB grew upto 600GB(due to audit log) then we trim the audit log and shrink the DB to get the space back, so shrinking 200 GB is not an issue. You can refer this white paper to DBA Their is another way without involvement of DBA. If you browse Central admin and check the health ...


1

Before answering your questions, i want to recommend the following excellent technet article: Deciding to use RBS in SharePoint 2013 Just because you have a content database growing larger than 200GB, you do not have to implement RBS. RBS is mainly a feature to reduce storage-cost by getting BLOBs away from expensive SQL-Storage (like SSDs). RBS adds a lot ...


0

Back when I was testing StoragePoint before they were acquired by Metalogix, I was seeing anywhere from 97 to 99% Content DB size reduction. The tool allowed for a lot ot flexibility in determining what types and size limits of fiels that should be offloaded. The more aggressive the file size limit you made, the more was offloaded and the smaller your ...


0

I am still researching how this works myself, however: The "shredding" term refers specifically to the methodology for storing the portion of the BLOB which has changed - therefore, it would not make sense for un-editable files to change. Since we are investigating utilizing this functionality at my company, I'm curious if someone else has encountered this? ...


0

Here are the steps which you need to perform. Stop Content Db to use RBS and Move in all the Files inside the DB from Blob Folder. Verity that files are inside Sql DB by running query. Test by uploading file to Site and verify it stores in sql DB. backup and restore the DB to your new SharePoint 2013 environment. If its a classic mode web app in 2010 then ...



Top 50 recent answers are included