Currently one of the SharePoint 2010 site collection Content Database size grown to 200 GB. We need help to reduce this database size where We can use MS recommended standard Import-Export, Backup-Restore methodology for subsites which can be moved under new site collection.What are the other options we will have in case Import-Export, Backup-Restore methodology is not feasible?Since currently we are facing some issues with Import-Export, Backup-Restore methodology. Is it reliable while working on Production with minimum downtime.Do you recommend any 3rd party tool to resolve this considering application customization, huge data, big file size etc. Regards, Nitin Patilnitin patil

first,you need to find out more about disk usage for the database in SQL Server Management Studio, right click the database, select reports->standard reports->disk usage. If the transacion log takes too much space, you can backup the log or just truncate it. The, you can shrink the database files, which will actually reduce the file size. If the database is still huge after all these, you can view the reports->standard reports->disk usage by top tables for the database. If you find that it is EventCache table that takes too much space, you can configure to keep it for a short period:http://blogs.technet.com/b/vinitt/archive/2010/01/01/how-to-clear-event-cache-table-in-supportable-ways.aspx . If there is too many old versions for documents in library, you can modify the setting to keep only recent versions. if there is too many site collections in a single content database, you can consider split them to other content database in the same web application.

first,you need to find out more about disk usage for the database in SQL Server Management Studio, right click the database, select reports->standard reports->disk usage. If the transacion log takes too much space, you can backup the log or just truncate it. The, you can shrink the database files, which will actually reduce the file size. If the database is still huge after all these, you can view the reports->standard reports->disk usage by top tables for the database. If you find that it is EventCache table that takes too much space, you can configure to keep it for a short period:http://blogs.technet.com/b/vinitt/archive/2010/01/01/how-to-clear-event-cache-table-in-supportable-ways.aspx . If there is too many old versions for documents in library, you can modify the setting to keep only recent versions. if there is too many site collections in a single content database, you can consider split them to other content database in the same web application.

first,you need to find out more about disk usage for the database in SQL Server Management Studio, right click the database, select reports->standard reports->disk usage. If the transacion log takes too much space, you can backup the log or just truncate it. The, you can shrink the database files, which will actually reduce the file size. If the database is still huge after all these, you can view the reports->standard reports->disk usage by top tables for the database. If you find that it is EventCache table that takes too much space, you can configure to keep it for a short period:http://blogs.technet.com/b/vinitt/archive/2010/01/01/how-to-clear-event-cache-table-in-supportable-ways.aspx . If there is too many old versions for documents in library, you can modify the setting to keep only recent versions. if there is too many site collections in a single content database, you can consider split them to other content database in the same web application.