Upgrade from GP2010 to GP 2015

(0) Share

Report

Posted on by PBoor

We have a 135 GB Company Database that we are trying upgrade to GP2015. The log grew to 190 Gig which put the drive at full capacity. It was a long running transaction that did this, perhaps an index create. is there anything that can be done to lower the transaction log use via the upgrade? The mdf grew to 195 gig as well.

I have asked for additional 250 Gig of space. Are there other recommendations from anyone who has gone through this? Both for the space usage and having the company upgrade faster? Other companies are doing fine. Thanks!!

There was an open transaction on the database that used up the 190 Gig.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (9)

Answers (2)

Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Try setting a maximum size on the log file so it won't grow. What is the setting for recovery mode, simple or full? It is odd that your mdf file grew that much. What was the beginning GP version?

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (1)

Report

Hi Pbor,

Setting a maximum on your log file growth won't achieve your goal: upgrading GP. By limiting the size, you only risk running into SQL errors that will tell you that the log file is maxed out.

You should first start by setting your company DB in SIMPLE recovery mode and ensure that your DB is configured with multiple .ldf files (you can spread them across multiple drives, just for the time of the upgrade). Also make sure your TempDB files are setup correctly to allow for enough space to grow.

The TempDB should always been configured to have as many data files as there are CPU cores in your server. 8 cores should call for 8 data files in your TempDB config.

135 GB is nothing exceptional, I've upgrade company with larger companies than that.

Was this reply helpful? Yes No
PBoor 70 on at

Like (0)

Report

Hey you are right.....I do have a way to split the ldf across drives. Thanks so much!!!

Was this reply helpful? Yes No
PBoor 70 on at

Like (0)

Report

Do you see any reason why the client to do the setup cannot be on a Windows 2012 Server. I am going to give it a go. The terminal server I have now has a lot less memory and less Network speed. The 135 gig company DB was 10 hours in this morning. There was an open transaction that was 5 hours old. We have plenty of .mdb and .ldb and temp space.

We are going live in 4 weeks and I want to be able to get this done in a 12 hour windows for them to test on a Saturday at 9:00 oclock

Was this reply helpful? Yes No
Verified answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

it depends not so much about the Windows server version, but more about the SQL version.. Which version of GP are you trying to upgrade first ?

I would definitely not perform the upgrade from a remote client, but perform it right on the SQL server itself whenever this is possible.. This will save you from the network traffic lag.. It definitely shouldn't take that long, but it also depends on how many companies you're upgrading.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

[quote]
it depends not so much about the Windows server version, but more about the SQL version.. Which version of GP are you trying to upgrade first ?

I would definitely not perform the upgrade from a remote client, but perform it right on the SQL server itself whenever this is possible.. This will save you from the network traffic lag.. It definitely shouldn't take that long, but it also depends on how many companies you're upgrading.
[/quote]
You should first start by setting your company DB in SIMPLE recovery mode and ensure that your DB is configured with multiple .ldf files (you can spread them across multiple drives, just for the time of the upgrade). Also make sure your TempDB files are setup correctly to allow for enough space to grow.

Was this reply helpful? Yes No
PBoor 70 on at

Like (0)

Report

Thank you for your reply. It did run in 7 hours for one company. Having to install the client on the sql server is not going to fly here. I did get it work and the 7 hours will be acceptable. For anyone doing a GP upgrade, plan to have large transaction logs even in simple mode. One transaction takes 5 plus hours...nothing you can do but watch them grow. Our company DB for this was 135 gig. Thanks again to everyone who replied with my issue.

Was this reply helpful? Yes No
Verified answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Thanks for confirming that the upgrade worked..

Please mark the most appropriate answer in the thread as your response so the question will be identified as completed.

Good luck with the rest of the upgrade.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Did you go straight from GP 2010 to GP 2015? I have done numerous upgrades with databases of upwards of 300GB and I have never seen a log file grow that much. I will set the recovery mode to simple, do one hop, shrink the log file and perform the next hop and shrink the log file again. Switching back to full recovery and setting the log backup schedule allows the log file to grow back to its normal size.

Was this reply helpful? Yes No