Microsoft SQL Server 2008 Upgrade Advisor

With the release of Microsoft Dynamics GP 2010, I have been seing more and more questions regarding upgrading from earlier versions of Microsoft SQL Server -- for example Microsoft SQL Server 2000 -- to Microsoft SQL Server 2008. The questions usually comes in the form of "we are currently running [some prior version of SQL Server here] and they are ready to move to Microsoft SQL Server 2008. Is there a checklist in place for this upgrade? How does this affect GP?"

To start, the reason you will not find much of a checklist on upgrading Microsoft SQL Server on CustomerSource or PartnerSource is because this topic does not have much to do with the Microsoft Dynamics GP application itself, but rather falls in the domain of the Microsoft SQL Server Team. As such, one of the cool tools available from the SQL Server Team is the SQL Server Upgrade Advisor.

SQL Server Upgrade Advisor is a wizard-based application that helps you prepare for upgrades to SQL Server 2008 or SQL Server 2008 R2. The Upgrade Advisor analyzes installed components from earlier versions of SQL Server, and then generates a report that identifies issues to fix either before or after you upgrade your database server.



Upgrade Advisor analyzes the following SQL Server components:

  • Database Engine
  • Analysis Services
  • Reporting Services
  • Integration Services
  • Data Transformation Services
While Notification Services appears in the Analysis Wizard, it is not included in Upgrade Advisor scans because it has been removed beginning in SQL Server 2008 R2.


You can find more information about Microsoft SQL Server Upgrade Advisor at the following links:

Using Upgrade Advisor to Prepare for Upgrades @ MSDN
Microsoft SQL Server Upgrade Advisor download page @ MS Download Center
Microsoft SQL Server versions and editions upgrade @ MSDN

Until next post!

MG.-
Mariano Gomez, MIS, MCP, PMP, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Scott said…
You say "this topic does not have much to do with the Microsoft Dynamics GP application itself", however, given that GP 9 runs on SQL 2005 at what point do you do the upgrade to SQL 2008?

Also, some of the features of GP 2010 are only available on SQL 2008 like "Microsoft SQL Server Reporting Services Charts & KPIs" according to the docs.

So if plenty of people are asking the question then clearly more guidance is needed on how you would get your environment from Win2k3 & SQL2005 to Win2k8 and SQL2008? It may seem obvious to you but not to the rest of us.
February 17, 2011 at 10:42 PM
Mariano Gomez said…
Scott,
Thanks for your inquiry.

Since GP9 runs on SQL Server 2005, you will want to upgrade to SQL Server 2008 when you are considering moving to GP10 or GP2010.

Nothing is "obvious" to me. I write for the general public, so I can't say what each individual circumstances are.

However, I will venture to say this: upgrades from W2K3 & SQL2005 to W2K8 & SQL2008 (or 2008R2) should factor in the company's systems upgrade policies. This is, I am sure many organizations just don't look at GP as the sole reason for upgrading their entire systems infrastructure, or do they? I personally have not come across this. At many of my clients, GP is one in hundreds of other applications they support and sure does not drive systems policies.

MG.-
February 18, 2011 at 9:48 AM
Scott said…
Hi Mariano, I agree upgrades need to be planned but if GP has its own server(s), once you have decided to upgrade, what is the recommended order to do this?

Is it:
1) Upgrade Dynamics GP to 2010
2) Upgrade Win2K3 to Win2k8
3) Upgrade SQL2005 to SQL2008

If you do this will you get all the available functionality since some of the features of GP 2010 require SQL 2008?

Does that mean you then need to reinstall some of the additional features once you upgrade the OS and SQL?

If you do the upgrade in some other sequence then you would effectively have GP 9 on either win2k8 or SQL2008 which is technically unsupported.

So there is a bit of a catch 22. Do you see what I mean? What is the recommended order? The documentation is particularly vague in this area.

Thanks
Scott
February 20, 2011 at 9:16 PM
Mariano Gomez said…
Scott,
My preferred upgrade plan is as follows:

1. Condition another server with Windows 2008 and SQL Server 2008 R2.

2. Transfer the databases from their current SQL2005 server to SQL 2008 (see KB article 878449).

3. Use the GP2010wSP1 DVD image on CustomerSource to upgrade the databases on your new server.

If you only have one server to work with, then your steps are what I would do. In any case, you will end up with all the functionality.

The documentation is vague, because is virtually impossible to predict all the possible configurations companies will end up with.

MG.-
February 21, 2011 at 9:11 AM
Scott said…
Thanks Mariano.
February 22, 2011 at 3:10 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more