Matt
Tue Dec 20 11:19:40 CST 2005
v3.0 actually checks for a named instance and aborts the install with a hard
stop. Not sure on the upgrade questions you pose as I haven't played with
that yet myself.
--
Matt Parks
MVP - Microsoft CRM
"Al Baird" <AlBaird@discussions.microsoft.com> wrote in message
news:BA6BF70E-ADD4-4896-99C5-5F891A7253BA@microsoft.com...
If we chose to 'restore' the databases to the central SQL server before
upgrading to SQL 2005, would the upgrade from SQL 2000 to SQL 2005 affect
our
databases? Or (since this is a new installation and we haven't really done
much data input) if we just reinstalled CRM and told it to use the central
server from the get-go, so to speak, how would CRM deal with the SQL
upgrade?
Our central server is a named instance as well. Would that affect the
installation or upgrade, or only whether or not it's supported? :)
"Matt Parks" wrote:
> Migrating the DB's is a lot easier with v3.0 since there is no longer any
> replication dependancies. Follow the guidelines in the implementation
Guide
> related to recovering the database to restore to the new server and point
> CRM to the restored DB/
>
> --
>
> Matt Parks
> MVP - Microsoft CRM
>
>
> "Al Baird" <Al Baird@discussions.microsoft.com> wrote in message
> news:0EB57A3B-24B1-490F-A5A5-486CD6A33C7E@microsoft.com...
> We're going to be deploying a new installation of CRM 3.0 using a SQL
Server
> 2000 installation on the CRM box itself. We want to migrate our databases
> to
> our central SQL server after our central SQL server is upgraded from 2000
to
> 2005 in the near future. What would be the best method to accomplish
this?
>
>
>