By the way...

Before uninstalling the Filestream provider, make sure that you have content migrated back in the content database. To ensure this, just open “AllDocStreams” in the SharePoint Content database and look at the “Content” and “Rbsid” columns. the “Rbsid” columns should be NULL and “Content” column should be filled with data. If you uninstall the RBS provider before migrating the data back in the content database, all the data will become unavailable/ inaccessible. Use following command to Migrate content back and forth from and to DB to Blob Store: $rbss.SetActiveProviderName(“”) $rbss.Migrate()

The scenario was, I installed the RBS with Filestream and uninstalled the RBS and realized that all the blobs are still out there on file system due to which the uninstall process failed. Now I tried to call $rbss.Migrate() in PS but it failed because the RBS was no longer installed! I tried to call $rbss.Enable() but it failed with an error saying “SQL Remote Blob Storage should be installed on the web front end and content database before your can enable it” something like that. I re-installed RBS and filestream provider but it didn’t let me enable it and kept giving error. RESOLUTION and Lesson Learnt: To resolve the error, I re-booted the server and it worked. It is important to note that after installing RBS, it is required to restart the windows if are failing to “Enable” it on the content database.

If you want to move a MOSS 2007 databases over to a new DB server, do the following: 1. Run SharePoint configuration wizard (on the web server) 2. Disconnect from existing configuration database (on web server) 3. Move the SITE database over to the new database server (on DB server) 4. Run configuration wizard again and create a new farm (on web server) 5. Give NEW database server and NEW configuration database (on web server) 6. After configuration wizard is finished, create web application by going in the SharePoint Cetral Admin (on web server) 7. Give it any web site name. Here you'll specify the New database server and OLD SITE db name. Hit OK. That's it. So only the combination of New DB server and Old Database name are important to specify in all this scenario. Now open web browser and open the site with same URL that it had been running before. You can also follow other processes like descriped on "Ron Grzywacz's Blog"

During database restore, I tried to rename existing database in SQL Server 2005 by simply trying following command: ALTER DATABASE mydatabase MODIFY NAME = mydatabase_OLD But it didn't work and gave following error: "The database could not be exclusively locked to perform the operation." In order to fix, I had to set it to single user for a while, change the name and then set it back to multi-user. I had to execute following commands to make it work: ALTER DATABASE mydatabase SET SINGLE_USER WITH ROLLBACK IMMEDIATE GO ALTER DATABASE mydatabase MODIFY NAME = mydatabase_OLD GO ALTER DATABASE mydatabase_OLD SET MULTI_USER GO