CodePlex has two great tools to query your SharePoint 2007 or 2010 search which return raw XML so you can see exactly what is going on in your results.
Fast Search For SharePoint MOSS 2010 Query Tool – Ok, they need to work on the title a bit and the background is just a terrible idea but the thing works for both FAST and Enterprise Search on 2010. It allows you to choose Scope, edit the Default Columns, and a lot more. It’s mostly intuitive to use. Just make sure to change your “Results Provider” to “SharePoint” if you’re using Enterprise instead of FAST.
SharePoint Search Service Tool – This is for SharePoint 2007 and works just as well as the previous one. It has less options but gets you your XML results quickly and edit the query as needed. Plus, a nice background!
I recently had to downgrade from SQL Server 2008 R2 Enterprise down to Standard with SharePoint 2010 Enterprise installed. It turned out to be surprisingly easy, thanks to this thread. One issue will likely come up. Search won’t work and you’ll get this error:
Database ‘[name]‘ cannot be started in this edition of SQL Server because part or all of object ‘MSSDocSdids’ is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition.
Unfortunately you’ll have to recreate search. This post references any issues with that. The same might be true for your Web Analytics Service Application with an error like this:
EVENT 5586: Database ‘WebAnalyticsDatabaseName’ cannot be started in this edition of SQL Server because it contains a partition function ‘DateIdPF’. Only Enterprise edition of SQL Server supports partitioning.
Nevertheless, here are the steps that worked for me. Be sure to follow them to the letter.
Take a good backup of all of your databases (system and user).
Run SELECT @@VERSION and note the specific build number of SQL Server that you are currently on.
Shut down your existing instance of SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf), don’t move them copy them, from the current location to a new folder that you mark as readonly.
Uninstall SQL Server from the system.
Reboot the server.
Install SQL Server Standard Edition.
Apply the necessary Service Pack and/or Cumulative Updates to bring the instance up to your previous build number.
Shutdown SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf) from the folder you saved them in to the correct location for the new install and remove the readonly flag from the files, and change the file ACL’s so that the SQL Service account has Full Control over the files.
Startup SQL Server and if you did it correctly it will startup and be exactly where you were before you made any changes, with all of your user databaes online and you should be ready to let applications connect and resume operations.
The whole process took less than two hours. Good stuff.