Great Plains 7.0 and 7.5 service packs and versions

To complete the list I have been asked to publish the Great Plains version 7.0 and 7.5 service pack versions. Check out my GP support lifecycle post to see support end dates for these versions. Here is the detailed list for GP 7.x:

Service Pack

Version

Great Plains 7.0

SP 1

7.00g5

Great Plains 7.0

SP 2

7.00g12

Great Plains 7.5

RTM

7.50g3

Great Plains 7.5

SP 1

7.50g10

Great Plains 7.5

SP 2

7.50g16

Great Plains 7.5

SP 3

7.50g26

Great Plains 7.5

SP 4

7.50g30

Great Plains 7.5

SP 5

7.50g43

Great Plains 7.5

SP 6

7.50g53

Great Plains 7.5

SP 7

7.50g66

Some notes:

Great Plains 7.0 had two editions: Dynamics and eEnterprise. The service pack versions above are valid for both of these editions.

Dexterity and SmartList were updated independently in version 7.0.

Great Plains 7.5 was the first version with only one edition (no more Dynamics and eEnterprise).

Starting with Great Plains 7.5 Dexterity and SmartList updates were all rolled into one service pack.

All the Great Plains service packs listed above are cumulative.

Links to similar information for other GP versions can be found on my Resources page.

7 Responses to “Great Plains 7.0 and 7.5 service packs and versions”

We are using currently using GP 7.5 here in our organization. We’ve been using it since 2006 and up to this date, the size of our company’s database has grown to 52GB and counting. We are also experiencing major slow down while processing transactions, must be caused to the huge DB size, wherein we need to restart the server every time the problem occurs (twice a day at to be exact) just to address the issue. We thought that archiving the old data might fix the issue but we have no knowledge on how to to that.

I would like to ask if you have a procedure on how to archive old GP data? Or if you have better suggestions on how we are going to resolve our issue. We are currently not into upgrading, just maximizing what we have right now. Our last resort would be setting up a new company in a new server, but if there’s any other method out there, we would like to try it out first.

There is no easy way to quickly archive GP data out-of-the-box. You would have to go through each module you want to do this for and determine the best approach based on the data that you have in there. Some modules have options for deleting history, however, note that this is not the same as ‘archiving’ as it just deletes data. Some modules you are using may not have this option and not all modules will make it easy to determine what exactly to delete. You will also want to do a lot of testing to make sure this does not break anything else.

Starting a new company will most likely be a lot easier and less expensive/time intensive all things considered. Another option may be to create a copy of your current company and delete some of the history from there. If you’re not familiar with GP data flow and table structures, you might want to consider working with a GP consultant to help you with this to make sure that this is done correctly.

Something else to consider. 52GB is a HUGE amount of data to accumulate in GP in 6 years. I have seen companies using GP heavily for 20 years not have half that much data. What is taking up all that room? Do you have a lot of 3rd party add-ons or customizations? Are you storing a lot of custom data in GP? Do you have that much transaction volume ? It’s certainly is possible, but I would make sure that all that data is actually valid and needed. This is also important even if you start a new company – if you keep generating the same volume of data you could run into the same issue quickly.

Finally, just because you have a large database does not mean that the issues you are experiencing are caused by that. It’s entirely possible that something else is causing the issue and simply archiving data or creating a new company in the same environment would have the same problem. Again, this is something that you may need to talk to a GP (or possibly a SQL Server – assuming you’re on SQL Server) expert about to see if they can help narrow down the problem. Of course being on a version that has not been supported in 5 years may make something like this difficult if not impossible to get help with as many possible solutions would not be available to you. 😦

Now that you mentioned it, we have some customizations for our manufacturing module (Horizons Manufacturing Suite). Plus some other customizations for taxation and personalized modules which our vendor provided upon our acquisition of GP. These customizations, especially HMS, is heavily used by our end-users. But we have not maximized the use of HMS since it’s MRP module doesn’t fit our actual processing. We are only using the Production Entry and Traveler Processing for recording production output. Having said that, other tables from HMS might be left populated even though their not being used at all which may have caused our over-grown company database. The only problem in here is that we haven’t got a full grasp of which table is which so finding those floating data might become troublesome. 😦

Sorry, I don’t have any IAXL references. If I am remembering correctly, the idea is similar to IM, which is basically like running a macro. I don’t see any way you would be able to get around it once the message actually comes out, the goal should be to avoid all pop-up messages.

The only thing I can suggest as a resource is to see if Microsoft’s Professional Services Team can do something as a consulting service for you. However, I suspect that the answer will be no, since this is a discontinued product for an unsupported version. 😦

I’m a new support tech at Daniels Equipment. They have an old version of Greatplains 7.5. It was originally running on a Windows 2000 server. I migrated it to Windows 2003. Everything works, but I am unable to install the Integration Manager client on the server I keep getting the error message indicating the it’s looking for mdac 2.7.

I read a tech note indicating that Integration manager 7.5 sp3 resolved this problem. Unfortunately, I don’t have this software and Microsoft doesn’t provide it anymore. Do you know where I can get this service pack?

Have you talked to your GP Partner about this? Perhaps they can provide the service pack for you? Alternately, have you tried installing MDAC 2.7? Or installing Integration Manager elsewhere? There is no requirement that it has to be installed on the server, you can run it on any workstation where GP is installed.