Announcements
We are moving to 2013 but we have problems with upgrade the server from 2005 to 2008 and then 2012, any advise. Also I found the log file is very big around 2883 and shrink cant be dont any suggestion
*This post is locked for comments
Hi Pat,
You've two choices...either upgrade your GP first from 9.0 to 2010 : community.dynamics.com/.../upgrade-paths-to-microsoft-dynamics-gp-2013
or move your SQL databases to a new server first with a new SQL version (2008R2 or 2012). Check the KB878449 on how to manage that : support.microsoft.com/.../878449
If you want to plan for the future, I'd do it this way :
1. Build a new server with Windows 2012, SQL server 2008R2 and move your DB's over to that new server. In the process, you should get rid of your big log file. This will upgrade your SQL databases and get them ready for 2010R2.
2. Upgrade your GP 9.0 to 2010R2 on the new server.
3. Upgrade your SQL server 2008R2 to 2012
4. Proceed with the GP upgrade from 2010R2 to 2013 (R2? )
Document each steps and take backups after each major step (i.e. after SQL version upgrade and GP upgrade).
Hi,
We are in GP 9 sitting in 2005 SQL Server, idea is move to SQL 2012 but the log is too big ,the DB was trying to shrink the log and she couldn't. and after moving the DB we will install GP2013. Thank you
Yes, is exactly what it is
Hi Pat,
What is your current GP version exactly... there are some upgrade path that you need to follow in order for the version change to go right... and this includes also SQL server...
Tip : I would not migrate everything together in one shot (SQL & GP)... UPgrade your SQL server first to the least minimal version required for GP2013 (if you're moving to the base GP 2013, SQL 2005 is still supported, for 2013R2 you need to move at least to SQL 2008).
Check the following link : mbs.microsoft.com/.../HOT_TOPIC_MDGP2013Upgrade
Check also this community thread about the various upgrade paths for GP :
About your log file size, I would recommend that you take a full backup and get rid of your DB Log file... it can be re-initialized very easily after a full backup has been done with a detach/attach operation (the log file gets recreated). But I've the feeling there is another underlying problem with your SQL server if you allow your log file to grow that much large...
Good luck.
Pat201, You may need to have a plan in this upgrade. Are you referring the sql server database log file as 2883 GB?
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
