Gary,

Thanks for sharing this info. It's good to hear it was so straight forward.

Have you verified that the replication is working OK with the Outlook
client?

Matt

"Gary" <gary.rey@NOOOOSPAM.virtium.com> wrote in message
news:%23ZPQZmwcDHA.2580@TK2MSFTNGP12.phx.gbl...
No questions here, simply commenting on an experience.....

In an earlier post I had an issue with our SQL server, mainly it was running
out of space and I needed to relocate the CRM databases.

One person suggest I read the IG, which I reviewed (not much info on the
impact of such a move). Trying to detach and retach was futile because I was
unable to stop replication or simply take it offline.

After some SQL research I found that simply backing up the database and
restoring it to a new location did the trick. First I had to stop SQL Agent,
then proced with the backup. Then I restored all 4 main CRM databases to the
new location, restarted Agent, and CRM was still alive and well.

I didn't receive a single error.....

-Gary

Yes. I've checked CRM via outlook, did a synch, went offline, and all is
still running smooth.

-Gary

"Matt Parks" <Matt.Parks@removetoX_XRevereGroup.Com> wrote in message
news:OAO7M1wcDHA.1580@tk2msftngp13.phx.gbl...

Gary

thanks for having the nerve to try this :-)

not always possible to test but as you see it works well and we appreciate
you taking the time to post your results

I'll have to do the same thing soon so this information is useful. Have to
admit i thought it would be hard with replication as matt says etc


"Gary" <gary.rey@NOOOOSPAM.virtium.com> wrote in message
news:O9PQz8wcDHA.2460@TK2MSFTNGP10.phx.gbl...

Well I first tried it on my test server and it worked great, so then I
waited till afterhours and patiently made the attempt on our work server. I
really had no other choice as I was running out of time (free space was at a
critical low).

I believe stopping the SQL Agent stops replication while you work on it, no?

See, now you guys are just scaring me. Is there something more specific I
should check with respect to replication? Both IE and Outlook are working
and synching fine.........seemingly, I suppose.

-Gary


"John O'Donnell" <csharpconsulting@hotmail.com> wrote in message
news:ex%23y3QxcDHA.1540@tk2msftngp13.phx.gbl...

John,

I think Gary just restored the DB's to a different drive on the same server.
Hopefully the "better installation experience" that is promised with v1.2
will include the ability to let you tell it where to put the DB's instead of
relying on the defaults that are configured on the SQL Server.

"John O'Donnell" <csharpconsulting@hotmail.com> wrote in message
news:%23PAVmWxcDHA.3248@tk2msftngp13.phx.gbl...
if replication is working I would say you are fine. If there were any
problems you would see them in the SQL event logs

just keep watching those.

See this sort of issue will re-occur because many companies will trial CRM
on a test box and when they decide they like it want to move to a bigger box
then have to move the database.

did you reload crm as well and point it to the new database?




"Gary" <gary.rey@NOOOOSPAM.virtium.com> wrote in message
news:e7oeuUxcDHA.2632@TK2MSFTNGP12.phx.gbl...

phew!
solved that one.....

I went into the <OrgName>_MSCRM database, and rebuilt and then repopulated
the Full-Text Catalogs.

Ran that Agent process again and no errors.

I think the worse is over, that was the only error/warning I saw since the
move of the DBs.

-Gary

"Gary" <gary.rey@NOOOOSPAM.virtium.com> wrote in message
news:eTMhYmycDHA.1128@tk2msftngp13.phx.gbl...