Yesterday we announced a new webinar series where we will review and demonstrate the features of StoragePoint 3.0. StoragePoint 3.0 is a highly anticipated release that provides significant advancement over our already robuts BLOB remoting capabilities for SharePoint 2007 and SharePoint 2010. New features like Intelligent Archiving, Multiple Storage End Points, and advanced reporting capabilities significantly reduces the total cost of ownership of SharePoint deployments while providing improved performance, reduced backup/restore time frames, and flexible storage options . StoragePoint 3.0 is a must have for organizations deploying any level of document management or enterprise content management solutions on SharePoint 20007 or SharePoint 2010. To register for an upcoming webinar please visit our Event Brite page at http://storagepoint.eventbrite.com. For more information on StoragePoint visit www.storagepoint.com, blog.storagepoint.com, or www.youtube.com/user/storagepoint.
It’s not uncommon to have multiple SharePoint content databases for a single SharePoint application. The separation of site collections into different content databases is typically done in an attempt to work around content database size recommendations provided by Microsoft (see Microsoft’s Plan for Software Boundaries document for more information). In many cases organizations have one content database per site collection. After deploying StoragePoint into your existing SharePoint farm the next logical step is to run the externalize job(s) which will relocate your existing content outside of the content database. Once completed you will be left with very small content databases that can now be merged (note that you will have to run the DBCC_ShrinkDB script several times to reclaim your unused database space or rebuild table indexes before running dbcc_shrinkDB. For more information consult the StoragePoint Administrator’s Guide). Merging SharePoint content databases can be done using the stsadm command. Execute the steps below to merge your content databases.
- **** Important! Microsoft recommends applying the April Cumulative Update before you merge content databases. There are known issues with this merge database command prior to this update.
- Even though your content databases will be very small after relocating BLOBs with StoragePoint’s externalize job, you must make sure you have enough free space to merge content databases. The general rule is that you must have at least three times the size of source site collections database size. *** Note: Do not use the value returned for the StorageUsedMB property when running the stsadm -o enumsites -url webappurl to determine your database size. With StoragePoint deployed this property will reflect the total space used by content in SharePoint but not the actual size of the content database.
- In order to execute the following STSADM command you must be a member of the Farm Administrators group and be an Administrator on the local computer. Additionally you need to have Full Control permission for any site collection being moved. For SQL Server, you must be a member of the db_owner database role.
Steps to Merge Content Databases
- From a SharePoint server in your farm, open a command prompt and navigate to %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin
- Type the following STSTADM Command
STSADM –o mergecontentdbs –url <url of web application> –sourcedatabasename <source db name> –destinationdatabasename <dest. db name> –operation2 Note that the URL is the URL of the web application that contains the site collection. This is not the URL of the site collection itself.
Operation2 = full database merge
- Restart IIS by running iisreset/noforce from a command prompt.
This pertains to Windows Vista and Windows 7 only. If you are running Windows XP then stop reading.
If you are running Vista or Windows 7 and you are attempting use the “Upload Multiple Documents” feature of MOSS 2007 or WSS 3.0 to upload zip files you have probably noticed that zip files do not show in the upload explorer window. The “Upload Multiple Documents” feature is an ActiveX control that installs with Office 2003/2007 so if you aren’t running either Office versions then the option won’t show up in SharePoint. The problem with zip files and the ActiveX control has to do with how Vista deals with zip and CAB files. By default Vista is configured to show zip and CAB files as folders allowing the user to drill into their contents within Windows Explorer. For this reason they do not show up in the ActiveX control that handles multiple file uploads for SharePoint. To fix this problem you need to delete the following registry keys. WARNING! Backup your registry before making any changes!
Now deleting the above registry keys is a bit more involved than running RegEdit, finding the keys, and deleting them. Both keys above are protected keys and are own by the SYSTEM account. In order to delete the keys you need to change ownership of the keys, delete sub keys first, and then delete the root key. To do this you need to download the PSExec utility from Microsoft that is part of the Sysinternals tools. The download is located here http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx . Once you have downloaded the tools and extracted the PSExec utility from the zip file, you need to then start a windows command prompt as the local machine administrator (if you are not logged in as the administrator then run the following from the RUN dialog: runas :user/localhost\administrator CMD ). Once the command window launches navigate to the directory where you unpacked the contents of the zip file that you downloaded earlier and execute the following command: psexec -i -d -s c:\windows\regedit.exe. At this point you are now running RegEdit as the SYSTEM account and will be able to change ownership of registry keys. It is important to note that you have to delete child keys before deleting the root key.