Admin Content DB move
I am trying to move the admin content DB from one SQL server to another SQL server with different name.
I run this command and it errors out with command line error.
STSADM –o preparetomove –contentdb WEB05\OFFICESERVERS:"SharePoint_AdminContent_bf974a1e-ffb4-4efb-9606-dde656c19072" –site http://web05:33145
I know the DB name is correct
C:\>stsadm.exe -o enumcontentdbs -url http://web05:33145
<Databases Count="1">
<ContentDatabase Server="WEB05\OfficeServers" Name="SharePoint_Admin
Content_bf974a1e-ffb4-4efb-9606-dde656c19072" />
</Databases>C:\>stsadm.exe -o enumcontentdbs -url http://web05:33145
I know the site name is correct as well
C:\>stsadm.exe -o enumsites -url http://web05:33145
<Sites Count="1">
<Site Url="http://web05:33145" Owner="xxx" SecondaryOwner="
yyy" ContentDatabase="SharePoint_AdminContent_bf974a1e-ffb4-4efb-9606-d
de656c19072" StorageUsedMB="17.4" StorageWarningMB="0" StorageMaxMB="0" />
</Sites>
Any ideas what I am missing here?
May 6th, 2010 7:38pm
What's the error message you're receiving?David Lozzi
Delphi Technology Solutions
SharePoint Blog |
LinkedIn | Twitter
** SharePoint users be aware! The command "stsadm -o uninstall" works, and it doesn't warn you, it simply uninstalls SharePoint!
It happened to me!
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2010 3:27pm
Hi,
Please try:
STSADM –o preparetomove –contentdb WEB05\OFFICESERVERS:SharePoint_AdminContent_bf974a1e-ffb4-4efb-9606-dde656c19072 –site
http://web05:33145
By the way,
stsadm –o preparetomove command is not required after Infrastructure Update patch on MOSS Server. Refer this blog for details:
http://blogs.msdn.com/toddca/archive/2009/01/30/preparetomove-away-from-running-this-command.aspx
Please also note that you should follow the instructions in this reference to avoid any errors.
http://technet.microsoft.com/en-us/library/cc512725.aspx
Hope it helps.Lily Wu
May 10th, 2010 12:19pm
Hi bscoggins4,
For your scenario, I think you should follow the second part procedures, also need to
direct the farm to the new database server by using a SQL Server connection alias as described in first part step 10.
Another option is first upgrade your old database server to Windows Server 2008 & SQL Server 2008 then follow the procedures for moving all databases to a new
database server with a different name.
Please note that backup all the database in case anything happens.
Hope it helps.
Thanks & Regards.
Lily Wu
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2010 11:26am