Greetings,

We have recently upgraded our SQL server we use for MOSS.

I have successfully moved all content databases from one SQL server to 
another.

Now I need to move all "admin" type databases as well:
1) AdminContent
2) Config
3) Search
4) SharedServices

Can I do this without a call to Microsoft? I looked for documentation, but 
some of the comments do not flatter the content.

Is there an official "This is how we do it?"

Thank you,
Gregory

Hi Greg,

The most important databases that needs to be migrated are the content
databases and my sites. Admin Content and Config database would be
created when you install the new sharepoint farm. Similarly search and
sharedservices databases would have to be brand new.

Though after attaching the content databases to the respective web
applications after droping the temporary databases that are created
when you create webapplications. You would also have to configure SSP,
search, content sources, excel services and pretty much everything. If
you have customizations like webparts, custom features, site
tempaltes, you would have to redeploy those in the new farm otherwise
the sites might not work as you expect.

You can refer the documentation below.

Migrate databases
http://technet.microsoft.com/en-us/library/cc263299.aspx

I hope this information is usefull.

Regards,
Vaibhav Desai

Hi Vaibhav, and thank you for your reply.

We actually are not moving or upgrading the farm.

We only want to move all admin and content databases to a faster SQL server.

Can this be done?

Thank you,
Gregory




"Vaibhav Desai" wrote:

> Hi Greg,
> 
> The most important databases that needs to be migrated are the content
> databases and my sites. Admin Content and Config database would be
> created when you install the new sharepoint farm. Similarly search and
> sharedservices databases would have to be brand new.
> 
> Though after attaching the content databases to the respective web
> applications after droping the temporary databases that are created
> when you create webapplications. You would also have to configure SSP,
> search, content sources, excel services and pretty much everything. If
> you have customizations like webparts, custom features, site
> tempaltes, you would have to redeploy those in the new farm otherwise
> the sites might not work as you expect.
> 
> You can refer the documentation below.
> 
> Migrate databases
> http://technet.microsoft.com/en-us/library/cc263299.aspx
> 
> I hope this information is usefull.
> 
> Regards,
> Vaibhav Desai
> .
> 

Check out this technet article:

http://technet.microsoft.com/en-us/library/cc512723.aspx


-- 
Daniel A. Galant

Imagine what we could be... if we could just imagine.

"GregoryH" <gregoryh@newsgroup.nospam> wrote in message 
news:08D780C4-F42F-4C83-844E-8349A8B574E0@microsoft.com...
> Hi Vaibhav, and thank you for your reply.
>
> We actually are not moving or upgrading the farm.
>
> We only want to move all admin and content databases to a faster SQL 
> server.
>
> Can this be done?
>
> Thank you,
> Gregory
>
>
>
>
> "Vaibhav Desai" wrote:
>
>> Hi Greg,
>>
>> The most important databases that needs to be migrated are the content
>> databases and my sites. Admin Content and Config database would be
>> created when you install the new sharepoint farm. Similarly search and
>> sharedservices databases would have to be brand new.
>>
>> Though after attaching the content databases to the respective web
>> applications after droping the temporary databases that are created
>> when you create webapplications. You would also have to configure SSP,
>> search, content sources, excel services and pretty much everything. If
>> you have customizations like webparts, custom features, site
>> tempaltes, you would have to redeploy those in the new farm otherwise
>> the sites might not work as you expect.
>>
>> You can refer the documentation below.
>>
>> Migrate databases
>> http://technet.microsoft.com/en-us/library/cc263299.aspx
>>
>> I hope this information is usefull.
>>
>> Regards,
>> Vaibhav Desai
>> .
>> 

------=_NextPart_0001_3F0149DB
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hello Greg,

I would suggest the following steps :
1. First disconnect the existing sharepoint server from the farm.
2.Take backup of the SQL database including the config and the Admin Content
3. Restore to the other SQL box, 
4. Give the same name and the IP address to the new SQL server.
5. Run the configuration wizard and connect to the Config database on the 
new SQL server.
6. Once connected, verify that everything works fine.

Hope this helps!
------=_NextPart_0001_3F0149DB
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hello Greg,
\par 
\par I would suggest the following steps :
\par 1. First disconnect the existing sharepoint server from the farm.
\par 2.Take backup of the SQL database including the config and the Admin Content
\par 3. Restore to the other SQL box, 
\par 4. Give the same name and the IP address to the new SQL server.
\par 5. Run the configuration wizard and connect to the Config database on the new SQL server.
\par 6. Once connected, verify that everything works fine.
\par 
\par Hope this helps!
\par }
------=_NextPart_0001_3F0149DB--