Friday, October 03, 2008

SQL 2008 and MSCRM 4.0

We successfully completed our internal upgrade to SQL 2008 and it is awesome. We did a complete revamp of our system and moved our CRM server and SQL server to a virtualized 64bit server then upgraded SQL to 2008 and it is great. The speed is fantastic and the move and upgrade were easy. The SQL 2008 upgrade was very easy and we're reaping the benefits. The enhancements to reports alone are worth it from a CRM perspective.

Check out some of the screenshots but if you are familiar with the slick looking reports that Excel 2007 has then you will be familiar with what SQL 2008 now has. There are gauges that Excel doesn't have (to my knowledge) that SQL 2008 has so that's one welcomed addtion.

Also, you can check out the Customer Effective Blog about this as Joel Lindstrom posted on this before SQL 2008 came out. My guess is that Joel has upgraded his system as well but you never know. We did and we're fans.

Here are some screenshots:





David Fronk
Dynamic Methods Inc.

6 comments:

Awright said...

What method did you use to get your data from sql 2005 to sql 2008 without breaking crm 4?

Dynamic Methods said...

Awright,

I just backed up my databases, ran the SQL 2008 installer, chose the upgrade option and let the upgrade run. Once it completed everything continued to work. Typically my SQL upgrades have been the smallest headache for me in terms of application upgrades. The spin time is rather long compared to some other applications, but SQL does have all the data to go through. But either way, I just ran the upgrade and I really didn't have any issues with it.

David Fronk
Dynamic Methods Inc.

Kevin Clements said...

We're planning a double migration; want to move from one SQL 2005 Server to a different SQL 2008 server.

I've been undecided between migrating from one server to another at SQL 2005, then upgrading the destination server to SQL 2008.

The other option I came up with was to do a new CRM deploy to the 2008 server, then migrate the organanization to that deployment.

Dynamic Methods said...

Kevin,

Do the migration and upgrade then just repoint the CRM server to look at the SQL server. The redeploy is almost the same thing anyway, because you have to move the databases in order to perform the redeploy.

David Fronk
Dynamic Methods Inc.

Anonymous said...

I have following Configurations for current MS CRM 3.0 system:
1. Windows 2003 Server
a. Crm 3.0 Server
b. Reporting Server 2005

2. SQL Server 2005(Windows Server 2003)
a. MSCRM, and
b. METABASE databases

I am planning to upgrade CRM 3.0 to 4.0 and SQL Server 2005 to 2008. For this upgrade I need help to successfully complete it.

I have planned following steps for upgrade-
1. Upgrade CRM 3.0 to 4.0 with current SQL Server 2005
2. Then using Deployment Manager to move the database from SQL Server 2005 to 2008.

I read this article (http://support.microsoft.com/kb/957053) issues related to installing CRM 4.0 with SQL 2008. But the hot fixes can be installed during CRM 4.0 installation. But I am doing an upgrade with SQL Server 2005 and changing to SQL Server 2008 afterwards.

Has anyone done this kind of upgrade? Please help.
or suggest which is the best/standard sys requirements for MS CRM 4.0(win 2003/2008) and SQL Server 2005/2008(Win 203/2008).

Dynamic Methods said...

I would recommend upgrading CRM to 4.0 first and then SQL 2008 afterwards. CRM 3.0 doesn't support SQL 2008 so you might be giving yourself more of a headache if you upgrade differently. I've done this kind of upgrade a couple of times and this is the smoothest method that I've been able to come up with.

David Fronk
Dynamic Methods Inc.

Post a Comment