Archive for SharePoint 2010 Research and Development
Overcome Test-SPContentDatabase “Database too old error message”
Ok, I was thinking that I could quickly take a SharePoint 2007 content database, apply the minimum Service Pack 2 for WSS 3.0 and MOSS 2007, and then perform a database attachment within SharePoint 2010 in minutes while basking in the glory of the easy process. I should have known this is SharePoint and everything is earned in this world. :-)
I rebooted all the web front end servers and application servers just to make sure my little SharePoint 2007 world had the right build number of 12.0.0.6421 within Central Admin. So I did a backup of the database and then moved the BAK file to the SharePoint 2010 Database instance and performed a simple restore. For extra incentive and I was the DBO in the environment, I placed the SP Farm Account DBO to make sure the attachment goes ok.
I ran the PowerShell commandlet Test-SPContentDatabase to verify the database. Then I got the error.
[box type="info"]So after I read multiple blogs, forums, etc.; I wanted to think outside-of-the-box. I tried an idea. “Maybe the commandlet needed a build number newer than 12.0.0.6421?”
So I got the April/2009 Cumulative update for WSS 3.0 and MOSS 2007. So I applied these two CU’s to the SharePoint 2007 Environment.
I verified I was on build number 12.0.0.6504. [/box]
Just like washing your hair. Rinse and Repeat.
So I did a backup of the database and then moved the BAK file to the SharePoint 2010 Database instance and performed a simple restore. For extra incentive and I was the DBO in the environment, I placed the SP Farm Account DBO to make sure the attachment goes ok.
I ran the PowerShell commandlet Test-SPContentDatabase to verify the database.
Resources for review:
I welcome any feedback.
A must have PowerShell statement inside your PowerShell Script for SharePoint 2010
The past few weeks, I have been writting a lot of PowerShell scripts so I can automate as many SharePoint administrative tasks that I can so I can enjoy other aspects of SharePoint during the business day. 
I found a must have statement from the book, “PowerShell for Microsoft SharePoint 2010 Administrators“, book.
Here is the statement. This statement is important if you have a scheduled task or a program that kicks off programs.
I have a template now to make sure I have this statement right underneath my opening comments area.
[box type="info"]Example: If (-not(Get-PSSnapin | Where-Object { $_.Name -eq “Microsoft.SharePoint.PowerShell”})) {Add-PSSnapin Microsoft.SharePoint.PowerShell;}[/box]
