Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

Yahoo Archive
1
I have taken a few customers from 8 to 9 where we brought in history.  Jobs, Orders, and PO's.
I even had one customer where we brought in ALL GL Transactions for a year, without a hitch.
Granted, it required some testing and use of scripts in Vantage and DMT, but it went smooth.
I remember for one company the conversion took two days and I did it solo.
DMT has only gotten better, so it should be easier now.


Agree on the UOM, they can be a real bear if not done correctly.


Bruce
Bruce@...
2

Hello, Everybody: 


Just looking for some general feedback on user's experiences and what works and what doesn't work.   We currently are running a Vista 8.03.408 Progress DB with about 10GB database.  We have purchases licenses for Epicor 10 and SQL Server.


If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help?  What is some of the data in 8 is data we wish not to migrate to 10?  Can we select the data that comes over?  What about using the DMT tool to extract the data from 8 directly into 10?


We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server.  I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.   The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines? 


Thanks for the feedback in advance.


--SF

3
This can be done by a regular person without outside help as long as you know what you are doing... assuming you understand Vantage and  Epicor 10 then yes it can be done.
Â
For people coming from 8x , unless historical data is super important I recommend doing a new implementation + DMT. The reason for this is that the data schema from 8x to E10 is drastically different (especially coming from progress) and a lot of data in 8x is probably "junk"
In version 8 Epicor didn't really handle UOM (Units of Measure) they way they do in 9 and 10 and the conversion is less than clean most times unless it is done with extreme care.
Also on a conversion from 8 to 10 you generally have to jump from 8 to 9.04(passthrough) to 9.05 to E10 which can take several days to process depending on your DB size, any of those steps can cause some corruption and marvelous data gremlins which are fun to deal with later.
Also if you have customizations , BPMS and Reports in place which most places do you will have to re-write those completely anyways.

So my recommendations are (and disclaimer I am a consultant)

a) If historical invoice / sales data is not that crucial for your business. (or if you can live with running 8x as a "lookup" for a while) I recommend that you do a fresh E10 implementation and DMT your data in.Â
I also recommend that if you go this route you get someone in to help you with your financial, and Inventory / UOM Setup. There are plenty of differences between 8 and 10 and enough time has passed between versions that it warrants a look to see if things can be done differently / better from a financial standpoint and the UOMs are a royal pain if they are done incorrectly.

b) If historical data is important to you then you can do a upgrade but I HIGHLY recommend that you get some expert help with your Inventory and UOMs so you don't end up with a royal mess and a massive inventory loss / gain / after the upgrade

In terms of Hyper V the setup is really more dependent on how many users you have and what kind of performance can hardware puts out.Â

But generally we recommend that the SQL Server Data Drives be separate from the OS / Epicor drive and that you have the fastest drives available for this purpose. Hyper V does introduce some overhead but if your hardware is pretty swanky that's not that big of a deal. If your setup is small (few users) you can have Epicor App and SQL on the same Box just make sure your Data and your App are on different physical drive arrays for performance reasons.

Hope this helps


Â






Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Wed, Feb 17, 2016 at 8:08 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p></p><p><span>Hello, Everybody: </span></p><p><span><br></span></p><p>Just looking for some general feedback on user&#39;s experiences and what works and what doesn&#39;t work.   We currently are running a Vista 8.03.408 Progress DB with about 10GB database.  We have purchases licenses for Epicor 10 and SQL Server.</p><p><br></p><p>If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help?  What is some of the data in 8 is data we wish not to migrate to 10?  Can we select the data that comes over?  What about using the DMT tool to extract the data from 8 directly into 10?</p><p><br></p><p>We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server.  I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.   The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines? </p><p><br></p><p>Thanks for the feedback in advance.</p><p><br></p><p>--SF</p><p></p>

</div>
 


<div style="color:#fff;min-height:0;"></div>

4
We are currently upgrading from Vantage 8.0.811b Progress to Epicor 10.700.4. SQL Server

We are having Epicor Technical do the actual db conversions.  We have had them do 2 passes so far so we currently have a test db in place which is a copy of our live Vantage 8 data.

We are using this db for testing functionality and for upgrading all of our CR XI R2 reports to CR 2011 reports which are still usable in E10.

We needed to keep all of our historical data in place.

This is a complicated procedure to update our database as multiple conversions need to take place (8.0.811b to 8.03 to 803.4 to 9.04 to 905 progress and then from 905 progress to 905 SQL and then 905 SQL to 10.0.700.4 SQL.

Even then with Epicor doing the conversion, it takes 3 days processing time to convert our db and we will then  need an another day at least to update/ port all of our customizations we have revised to E10 as well as verify the data before we can go live.  So we figure to start on a Friday evening, get the db back Monday evening, Tuesday for verification and updating customization and then sometime on Wednesday to actually open the db to the rest of the users.

Additionally our progress db of about 6 GB grew to about 74 GB SQL Db in the process.

Our Go Live date is the middle of May after our financials are closed for April.

Hope this info is helpful.
5

Having gone from Vantage 6.1 (and another cloud based ERP system) to E10 as a “new” implementation I totally agree with Jose.  In addition to the actual conversion process it allows you to re-define all the coding schemes for types, classes, resources, resource groups (aka work centers), etc…  Chances are the formats and codes set up for V8 (or prior) that have been “locked in” are now obsolete so it gives a chance to model the business as it is now, not what it was way back then.  DMT is a great tool for doing this but it takes time and a lot of thinking about how you want things.

-Todd C.

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 17, 2016 7:29 PM
To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

 

 

This can be done by a regular person without outside help as long as you know what you are doing... assuming you understand Vantage and  Epicor 10 then yes it can be done.

 

For people coming from 8x , unless historical data is super important I recommend doing a new implementation + DMT. The reason for this is that the data schema from 8x to E10 is drastically different (especially coming from progress) and a lot of data in 8x is probably "junk"

In version 8 Epicor didn't really handle UOM (Units of Measure) they way they do in 9 and 10 and the conversion is less than clean most times unless it is done with extreme care.

Also on a conversion from 8 to 10 you generally have to jump from 8 to 9.04(passthrough) to 9.05 to E10 which can take several days to process depending on your DB size, any of those steps can cause some corruption and marvelous data gremlins which are fun to deal with later.

Also if you have customizations , BPMS and Reports in place which most places do you will have to re-write those completely anyways.

 

So my recommendations are (and disclaimer I am a consultant)

 

a) If historical invoice / sales data is not that crucial for your business. (or if you can live with running 8x as a "lookup" for a while) I recommend that you do a fresh E10 implementation and DMT your data in. 

I also recommend that if you go this route you get someone in to help you with your financial, and Inventory / UOM Setup. There are plenty of differences between 8 and 10 and enough time has passed between versions that it warrants a look to see if things can be done differently / better from a financial standpoint and the UOMs are a royal pain if they are done incorrectly.

 

b) If historical data is important to you then you can do a upgrade but I HIGHLY recommend that you get some expert help with your Inventory and UOMs so you don't end up with a royal mess and a massive inventory loss / gain / after the upgrade

 

In terms of Hyper V the setup is really more dependent on how many users you have and what kind of performance can hardware puts out. 

 

But generally we recommend that the SQL Server Data Drives be separate from the OS / Epicor drive and that you have the fastest drives available for this purpose. Hyper V does introduce some overhead but if your hardware is pretty swanky that's not that big of a deal. If your setup is small (few users) you can have Epicor App and SQL on the same Box just make sure your Data and your App are on different physical drive arrays for performance reasons.

 

Hope this helps

 

 

 

 

 

 

 



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 

On Wed, Feb 17, 2016 at 8:08 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

 

Hello, Everybody: 

 

Just looking for some general feedback on user's experiences and what works and what doesn't work.   We currently are running a Vista 8.03.408 Progress DB with about 10GB database.  We have purchases licenses for Epicor 10 and SQL Server.

 

If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help?  What is some of the data in 8 is data we wish not to migrate to 10?  Can we select the data that comes over?  What about using the DMT tool to extract the data from 8 directly into 10?

 

We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server.  I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.   The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines? 

 

Thanks for the feedback in advance.

 

--SF

 

6

I concur with Mr. Jose.  We just upgraded from Vantage 8 to Epicor 10. 

 

UOM rules are still causing us much pain. Make sure you test UOM issues thoroughly.  Don’t forget to test serialized parts thoroughly.  Serialized parts cannot have a UOM code that allows decimals.  We were using the same UOM for decimal parts and Serialized parts.  After upgrading to E10, this has proved to be very difficult to fix.  In some cases we had to use a new part number.

 

Another UOM issue showed up after running “Refresh PartBin  QOH from PartTran”.  Our system ended up with multiple QOH records in a Part/WH/Bin for different UOMs.   These locations were created because of Purchase order and job transactions using a different UOM from the Part UOM.

 

We wanted to re-implement, but were over-ruled.  Our company thought we used “great care” with UOM codes, but found out differently.   

 

Thanks,

 

Sharon Pulsifer

Fibrebond Corporation

318.371.6347

 

7
Sorry to hear Sharon, UOMs are a giant pain


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Feb 18, 2016 at 9:26 AM, 'Pulsifer, Sharon' sharon.pulsifer@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>

I concur with Mr. Jose. We just upgraded from Vantage 8 to Epicor 10.Â

Â

UOM rules are still causing us much pain. Make sure you test UOM issues thoroughly. Don’t forget to test serialized parts thoroughly. Serialized parts cannot have a UOM code that allows decimals. We were using the same UOM for decimal parts and Serialized parts. After upgrading to E10, this has proved to be very difficult to fix. In some cases we had to use a new part number.

Â

Another UOM issue showed up after running “Refresh PartBin  QOH from PartTran”. Our system ended up with multiple QOH records in a Part/WH/Bin for different UOMs.   These locations were created because of Purchase order and job transactions using a different UOM from the Part UOM.

Â

We wanted to re-implement, but were over-ruled. Our company thought we used “great care” with UOM codes, but found out differently.  Â

Â

Thanks,

Â

Sharon Pulsifer

Fibrebond Corporation

318.371.6347

 

</div>
 


<div style="color:#fff;min-height:0;"></div>

8

Is this your next Insights talking points?

 

We want to implement a new E10 but I think the historical data will be needed.

 

I believe I remember you mentioning that E10 can support multiple EPCIOR db, how does that work when you are on 702A Progress.  Do you need to convert your Progress DB to be able to connect to the newer E10 SQL?

 

Miguel A. Santillan

Compass Manufacturing Systems

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 17, 2016 5:29 PM
To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

 

 

This can be done by a regular person without outside help as long as you know what you are doing... assuming you understand Vantage and  Epicor 10 then yes it can be done.

 

For people coming from 8x , unless historical data is super important I recommend doing a new implementation + DMT. The reason for this is that the data schema from 8x to E10 is drastically different (especially coming from progress) and a lot of data in 8x is probably "junk"

In version 8 Epicor didn't really handle UOM (Units of Measure) they way they do in 9 and 10 and the conversion is less than clean most times unless it is done with extreme care.

Also on a conversion from 8 to 10 you generally have to jump from 8 to 9.04(passthrough) to 9.05 to E10 which can take several days to process depending on your DB size, any of those steps can cause some corruption and marvelous data gremlins which are fun to deal with later.

Also if you have customizations , BPMS and Reports in place which most places do you will have to re-write those completely anyways.

 

So my recommendations are (and disclaimer I am a consultant)

 

a) If historical invoice / sales data is not that crucial for your business. (or if you can live with running 8x as a "lookup" for a while) I recommend that you do a fresh E10 implementation and DMT your data in. 

I also recommend that if you go this route you get someone in to help you with your financial, and Inventory / UOM Setup. There are plenty of differences between 8 and 10 and enough time has passed between versions that it warrants a look to see if things can be done differently / better from a financial standpoint and the UOMs are a royal pain if they are done incorrectly.

 

b) If historical data is important to you then you can do a upgrade but I HIGHLY recommend that you get some expert help with your Inventory and UOMs so you don't end up with a royal mess and a massive inventory loss / gain / after the upgrade

 

In terms of Hyper V the setup is really more dependent on how many users you have and what kind of performance can hardware puts out. 

 

But generally we recommend that the SQL Server Data Drives be separate from the OS / Epicor drive and that you have the fastest drives available for this purpose. Hyper V does introduce some overhead but if your hardware is pretty swanky that's not that big of a deal. If your setup is small (few users) you can have Epicor App and SQL on the same Box just make sure your Data and your App are on different physical drive arrays for performance reasons.

 

Hope this helps

 

 

 

 

 

 

 



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 

On Wed, Feb 17, 2016 at 8:08 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

 

Hello, Everybody: 

 

Just looking for some general feedback on user's experiences and what works and what doesn't work.   We currently are running a Vista 8.03.408 Progress DB with about 10GB database.  We have purchases licenses for Epicor 10 and SQL Server.

 

If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help?  What is some of the data in 8 is data we wish not to migrate to 10?  Can we select the data that comes over?  What about using the DMT tool to extract the data from 8 directly into 10?

 

We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server.  I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.   The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines? 

 

Thanks for the feedback in advance.

 

--SF

 



Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

9
Hi Miguel
I'll be at insights this year but I won't be speaking
I am not sure what you are referring to regarding E10 supporting multiple Epicor DB's? In E10 you can have as many E10 instances as you want. (Not just Test, Training, Pilot, Production).. maybe that's what I was referring to. If you are in 9.05 Progress there is an upgrade path direct to E10. Not sure if I misunderstood your question

Thanks!


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Feb 18, 2016 at 12:26 PM, Miguel Santillan msantillan@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>

Is this your next Insights talking points?

Â

We want to implement a new E10 but I think the historical data will be needed.

Â

I believe I remember you mentioning that E10 can support multiple EPCIOR db, how does that work when you are on 702A Progress. Do you need to convert your Progress DB to be able to connect to the newer E10 SQL?

Â

Miguel A. Santillan

Compass Manufacturing Systems

Â

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 17, 2016 5:29 PM
To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

Â

Â

This can be done by a regular person without outside help as long as you know what you are doing... assuming you understand Vantage and  Epicor 10 then yes it can be done.

Â

For people coming from 8x , unless historical data is super important I recommend doing a new implementation + DMT. The reason for this is that the data schema from 8x to E10 is drastically different (especially coming from progress) and a lot of data in 8x is probably "junk"

In version 8 Epicor didn't really handle UOM (Units of Measure) they way they do in 9 and 10 and the conversion is less than clean most times unless it is done with extreme care.

Also on a conversion from 8 to 10 you generally have to jump from 8 to 9.04(passthrough) to 9.05 to E10 which can take several days to process depending on your DB size, any of those steps can cause some corruption and marvelous data gremlins which are fun to deal with later.

Also if you have customizations , BPMS and Reports in place which most places do you will have to re-write those completely anyways.

Â

So my recommendations are (and disclaimer I am a consultant)

Â

a) If historical invoice / sales data is not that crucial for your business. (or if you can live with running 8x as a "lookup" for a while) I recommend that you do a fresh E10 implementation and DMT your data in.Â

I also recommend that if you go this route you get someone in to help you with your financial, and Inventory / UOM Setup. There are plenty of differences between 8 and 10 and enough time has passed between versions that it warrants a look to see if things can be done differently / better from a financial standpoint and the UOMs are a royal pain if they are done incorrectly.

Â

b) If historical data is important to you then you can do a upgrade but I HIGHLY recommend that you get some expert help with your Inventory and UOMs so you don't end up with a royal mess and a massive inventory loss / gain / after the upgrade

Â

In terms of Hyper V the setup is really more dependent on how many users you have and what kind of performance can hardware puts out.Â

Â

But generally we recommend that the SQL Server Data Drives be separate from the OS / Epicor drive and that you have the fastest drives available for this purpose. Hyper V does introduce some overhead but if your hardware is pretty swanky that's not that big of a deal. If your setup is small (few users) you can have Epicor App and SQL on the same Box just make sure your Data and your App are on different physical drive arrays for performance reasons.

Â

Hope this helps

Â

Â

Â

Â

Â

Â

Â



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile

E: jose@...
http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?

Â

On Wed, Feb 17, 2016 at 8:08 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

Â

Hello, Everybody:Â

Â

Just looking for some general feedback on user's experiences and what works and what doesn't work.  We currently are running a Vista 8.03.408 Progress DB with about 10GB database. We have purchases licenses for Epicor 10 and SQL Server.

Â

If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help? What is some of the data in 8 is data we wish not to migrate to 10? Can we select the data that comes over? What about using the DMT tool to extract the data from 8 directly into 10?

Â

We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server. I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.  The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines?Â

Â

Thanks for the feedback in advance.

Â

--SF

Â



Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

</div>
 


<div style="color:#fff;min-height:0;"></div>

10
Jose, 

Thanks for the detailed response.  We could potentially grow to between 50-75 Users and 25-50 MES users.   We currently have a domain controller that is running Hyper-V, which I don't believe is the best setup, but it's what is in place.

I was thinking purchasing another Windows 2012 R2 Server Quad Xeon with an SSD OS drive and a RAID-10.  I could then either install Epicor on the SSD drive and use the RAID-10 as the SQL Server data drive, but then the APP and DB would be on the same machine.  Another option would be to load Hyper-V and load another Windows 2012 R2 and install SQL on this machine and run Epicor 10 outside the Hyper-V machine?  

What do you think? 

--SF
11
The Epicor App being on an SSD is pretty irrelevant, what you want on the fastest drives you can buy is your SQL Data. If you are going to have  up to 75 hours I recommend you run Epicor and SQL on different boxes and if you are using Hyper V then at least make sure that each machine is physically on different drive arrays and if possible different controllers.


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Feb 18, 2016 at 12:43 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>Jose, </p><div><br></div><div>Thanks for the detailed response.  We could potentially grow to between 50-75 Users and 25-50 MES users.   We currently have a domain controller that is running Hyper-V, which I don&#39;t believe is the best setup, but it&#39;s what is in place.</div><div><br></div><div>I was thinking purchasing another Windows 2012 R2 Server Quad Xeon with an SSD OS drive and a RAID-10.  I could then either install Epicor on the SSD drive and use the RAID-10 as the SQL Server data drive, but then the APP and DB would be on the same machine.  Another option would be to load Hyper-V and load another Windows 2012 R2 and install SQL on this machine and run Epicor 10 outside the Hyper-V machine?  </div><div><br></div><div>What do you think? </div><div><br></div><div>--SF</div><p></p>

</div>
 


<div style="color:#fff;min-height:0;"></div>

12

For me to use my historical data (Progress), I will need to convert from E9 Prog to E10 SQL.  Then I can use E10 Historical Instance along with a New E10 Instance.  I cannot run an E9 Prog DB and an E10 instance at the same time, unless I run both on separate servers.

 

Miguel A. Santillan

Compass Manufacturing Systems

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, February 18, 2016 9:38 AM
To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

 

 

Hi Miguel

I'll be at insights this year but I won't be speaking

I am not sure what you are referring to regarding E10 supporting multiple Epicor DB's? In E10 you can have as many E10 instances as you want. (Not just Test, Training, Pilot, Production).. maybe that's what I was referring to. If you are in 9.05 Progress there is an upgrade path direct to E10. Not sure if I misunderstood your question

 

Thanks!



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 

On Thu, Feb 18, 2016 at 12:26 PM, Miguel Santillan msantillan@... [vantage] <vantage@yahoogroups.com> wrote:

 

Is this your next Insights talking points?

 

We want to implement a new E10 but I think the historical data will be needed.

 

I believe I remember you mentioning that E10 can support multiple EPCIOR db, how does that work when you are on 702A Progress.  Do you need to convert your Progress DB to be able to connect to the newer E10 SQL?

 

Miguel A. Santillan

Compass Manufacturing Systems

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 17, 2016 5:29 PM
To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

 

 

This can be done by a regular person without outside help as long as you know what you are doing... assuming you understand Vantage and  Epicor 10 then yes it can be done.

 

For people coming from 8x , unless historical data is super important I recommend doing a new implementation + DMT. The reason for this is that the data schema from 8x to E10 is drastically different (especially coming from progress) and a lot of data in 8x is probably "junk"

In version 8 Epicor didn't really handle UOM (Units of Measure) they way they do in 9 and 10 and the conversion is less than clean most times unless it is done with extreme care.

Also on a conversion from 8 to 10 you generally have to jump from 8 to 9.04(passthrough) to 9.05 to E10 which can take several days to process depending on your DB size, any of those steps can cause some corruption and marvelous data gremlins which are fun to deal with later.

Also if you have customizations , BPMS and Reports in place which most places do you will have to re-write those completely anyways.

 

So my recommendations are (and disclaimer I am a consultant)

 

a) If historical invoice / sales data is not that crucial for your business. (or if you can live with running 8x as a "lookup" for a while) I recommend that you do a fresh E10 implementation and DMT your data in. 

I also recommend that if you go this route you get someone in to help you with your financial, and Inventory / UOM Setup. There are plenty of differences between 8 and 10 and enough time has passed between versions that it warrants a look to see if things can be done differently / better from a financial standpoint and the UOMs are a royal pain if they are done incorrectly.

 

b) If historical data is important to you then you can do a upgrade but I HIGHLY recommend that you get some expert help with your Inventory and UOMs so you don't end up with a royal mess and a massive inventory loss / gain / after the upgrade

 

In terms of Hyper V the setup is really more dependent on how many users you have and what kind of performance can hardware puts out. 

 

But generally we recommend that the SQL Server Data Drives be separate from the OS / Epicor drive and that you have the fastest drives available for this purpose. Hyper V does introduce some overhead but if your hardware is pretty swanky that's not that big of a deal. If your setup is small (few users) you can have Epicor App and SQL on the same Box just make sure your Data and your App are on different physical drive arrays for performance reasons.

 

Hope this helps

 

 

 

 

 

 

 



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 

On Wed, Feb 17, 2016 at 8:08 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

 

Hello, Everybody: 

 

Just looking for some general feedback on user's experiences and what works and what doesn't work.   We currently are running a Vista 8.03.408 Progress DB with about 10GB database.  We have purchases licenses for Epicor 10 and SQL Server.

 

If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help?  What is some of the data in 8 is data we wish not to migrate to 10?  Can we select the data that comes over?  What about using the DMT tool to extract the data from 8 directly into 10?

 

We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server.  I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.   The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines? 

 

Thanks for the feedback in advance.

 

--SF

 

 

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

 



Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

13
Is there a limitation for that Miguel? I honestly haven't tried, but I don't see why you couldn't have 905 and 10 running at the same time... though again I haven't tried.


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Feb 18, 2016 at 1:35 PM, Miguel Santillan msantillan@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>

For me to use my historical data (Progress), I will need to convert from E9 Prog to E10 SQL. Then I can use E10 Historical Instance along with a New E10 Instance. I cannot run an E9 Prog DB and an E10 instance at the same time, unless I run both on separate servers.

Â

Miguel A. Santillan

Compass Manufacturing Systems

Â

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, February 18, 2016 9:38 AM


To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

Â

Â

Hi Miguel

I'll be at insights this year but I won't be speaking

I am not sure what you are referring to regarding E10 supporting multiple Epicor DB's? In E10 you can have as many E10 instances as you want. (Not just Test, Training, Pilot, Production).. maybe that's what I was referring to. If you are in 9.05 Progress there is an upgrade path direct to E10. Not sure if I misunderstood your question

Â

Thanks!



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile

E: jose@...
http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?

Â

On Thu, Feb 18, 2016 at 12:26 PM, Miguel Santillan msantillan@... [vantage] <vantage@yahoogroups.com> wrote:

Â

Is this your next Insights talking points?

Â

We want to implement a new E10 but I think the historical data will be needed.

Â

I believe I remember you mentioning that E10 can support multiple EPCIOR db, how does that work when you are on 702A Progress. Do you need to convert your Progress DB to be able to connect to the newer E10 SQL?

Â

Miguel A. Santillan

Compass Manufacturing Systems

Â

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 17, 2016 5:29 PM
To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

Â

Â

This can be done by a regular person without outside help as long as you know what you are doing... assuming you understand Vantage and  Epicor 10 then yes it can be done.

Â

For people coming from 8x , unless historical data is super important I recommend doing a new implementation + DMT. The reason for this is that the data schema from 8x to E10 is drastically different (especially coming from progress) and a lot of data in 8x is probably "junk"

In version 8 Epicor didn't really handle UOM (Units of Measure) they way they do in 9 and 10 and the conversion is less than clean most times unless it is done with extreme care.

Also on a conversion from 8 to 10 you generally have to jump from 8 to 9.04(passthrough) to 9.05 to E10 which can take several days to process depending on your DB size, any of those steps can cause some corruption and marvelous data gremlins which are fun to deal with later.

Also if you have customizations , BPMS and Reports in place which most places do you will have to re-write those completely anyways.

Â

So my recommendations are (and disclaimer I am a consultant)

Â

a) If historical invoice / sales data is not that crucial for your business. (or if you can live with running 8x as a "lookup" for a while) I recommend that you do a fresh E10 implementation and DMT your data in.Â

I also recommend that if you go this route you get someone in to help you with your financial, and Inventory / UOM Setup. There are plenty of differences between 8 and 10 and enough time has passed between versions that it warrants a look to see if things can be done differently / better from a financial standpoint and the UOMs are a royal pain if they are done incorrectly.

Â

b) If historical data is important to you then you can do a upgrade but I HIGHLY recommend that you get some expert help with your Inventory and UOMs so you don't end up with a royal mess and a massive inventory loss / gain / after the upgrade

Â

In terms of Hyper V the setup is really more dependent on how many users you have and what kind of performance can hardware puts out.Â

Â

But generally we recommend that the SQL Server Data Drives be separate from the OS / Epicor drive and that you have the fastest drives available for this purpose. Hyper V does introduce some overhead but if your hardware is pretty swanky that's not that big of a deal. If your setup is small (few users) you can have Epicor App and SQL on the same Box just make sure your Data and your App are on different physical drive arrays for performance reasons.

Â

Hope this helps

Â

Â

Â

Â

Â

Â

Â



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile

E: jose@...
http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?

Â

On Wed, Feb 17, 2016 at 8:08 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

Â

Hello, Everybody:Â

Â

Just looking for some general feedback on user's experiences and what works and what doesn't work.  We currently are running a Vista 8.03.408 Progress DB with about 10GB database. We have purchases licenses for Epicor 10 and SQL Server.

Â

If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help? What is some of the data in 8 is data we wish not to migrate to 10? Can we select the data that comes over? What about using the DMT tool to extract the data from 8 directly into 10?

Â

We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server. I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.  The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines?Â

Â

Thanks for the feedback in advance.

Â

--SF

Â

Â

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

Â



Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

</div><div><div class="ygrps-yiv-378220798h5">
 


<div style="color:#fff;min-height:0;"></div>

14
#ygrps-yiv-1778263768 P.ygrps-yiv-1778263768b1e7fd89-0279-4ffe-a16a-1f1bcba0d537 { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1778263768 LI.ygrps-yiv-1778263768b1e7fd89-0279-4ffe-a16a-1f1bcba0d537 { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1778263768 DIV.ygrps-yiv-1778263768b1e7fd89-0279-4ffe-a16a-1f1bcba0d537 { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1778263768 TABLE.ygrps-yiv-1778263768b1e7fd89-0279-4ffe-a16a-1f1bcba0d537Table { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1778263768 DIV.ygrps-yiv-1778263768Section1 { }

You can run both

If you wanted to really change designs / setup you could convert and retain and even lookup data from the other instance.


Sent from my iPhone

On 18 Feb 2016, at 18:49, Jose Gomez jose@... [vantage] <vantage@yahoogroups.com> wrote:

 

Is there a limitation for that Miguel? I honestly haven't tried, but I don't see why you couldn't have 905 and 10 running at the same time... though again I haven't tried.


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Feb 18, 2016 at 1:35 PM, Miguel Santillan msantillan@... [vantage] <vantage@yahoogroups.com> wrote:
 

For me to use my historical data (Progress), I will need to convert from E9 Prog to E10 SQL.  Then I can use E10 Historical Instance along with a New E10 Instance.  I cannot run an E9 Prog DB and an E10 instance at the same time, unless I run both on separate servers.

 

Miguel A. Santillan

Compass Manufacturing Systems

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, February 18, 2016 9:38 AM


To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

 

 

Hi Miguel

I'll be at insights this year but I won't be speaking

I am not sure what you are referring to regarding E10 supporting multiple Epicor DB's? In E10 you can have as many E10 instances as you want. (Not just Test, Training, Pilot, Production).. maybe that's what I was referring to. If you are in 9.05 Progress there is an upgrade path direct to E10. Not sure if I misunderstood your question

 

Thanks!



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 

On Thu, Feb 18, 2016 at 12:26 PM, Miguel Santillan msantillan@... [vantage] <vantage@yahoogroups.com> wrote:

 

Is this your next Insights talking points?

 

We want to implement a new E10 but I think the historical data will be needed.

 

I believe I remember you mentioning that E10 can support multiple EPCIOR db, how does that work when you are on 702A Progress.  Do you need to convert your Progress DB to be able to connect to the newer E10 SQL?

 

Miguel A. Santillan

Compass Manufacturing Systems

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, February 17, 2016 5:29 PM
To: Vantage <vantage@yahoogroups.com>
Subject: Re: [Vantage] Upgrading from Vista 8.03.410 (Progress) to Epicor 10 (MYSQL)

 

 

This can be done by a regular person without outside help as long as you know what you are doing... assuming you understand Vantage and  Epicor 10 then yes it can be done.

 

For people coming from 8x , unless historical data is super important I recommend doing a new implementation + DMT. The reason for this is that the data schema from 8x to E10 is drastically different (especially coming from progress) and a lot of data in 8x is probably "junk"

In version 8 Epicor didn't really handle UOM (Units of Measure) they way they do in 9 and 10 and the conversion is less than clean most times unless it is done with extreme care.

Also on a conversion from 8 to 10 you generally have to jump from 8 to 9.04(passthrough) to 9.05 to E10 which can take several days to process depending on your DB size, any of those steps can cause some corruption and marvelous data gremlins which are fun to deal with later.

Also if you have customizations , BPMS and Reports in place which most places do you will have to re-write those completely anyways.

 

So my recommendations are (and disclaimer I am a consultant)

 

a) If historical invoice / sales data is not that crucial for your business. (or if you can live with running 8x as a "lookup" for a while) I recommend that you do a fresh E10 implementation and DMT your data in. 

I also recommend that if you go this route you get someone in to help you with your financial, and Inventory / UOM Setup. There are plenty of differences between 8 and 10 and enough time has passed between versions that it warrants a look to see if things can be done differently / better from a financial standpoint and the UOMs are a royal pain if they are done incorrectly.

 

b) If historical data is important to you then you can do a upgrade but I HIGHLY recommend that you get some expert help with your Inventory and UOMs so you don't end up with a royal mess and a massive inventory loss / gain / after the upgrade

 

In terms of Hyper V the setup is really more dependent on how many users you have and what kind of performance can hardware puts out. 

 

But generally we recommend that the SQL Server Data Drives be separate from the OS / Epicor drive and that you have the fastest drives available for this purpose. Hyper V does introduce some overhead but if your hardware is pretty swanky that's not that big of a deal. If your setup is small (few users) you can have Epicor App and SQL on the same Box just make sure your Data and your App are on different physical drive arrays for performance reasons.

 

Hope this helps

 

 

 

 

 

 

 



Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?

 

On Wed, Feb 17, 2016 at 8:08 PM, sanfranc415@... [vantage] <vantage@yahoogroups.com> wrote:

 

Hello, Everybody: 

 

Just looking for some general feedback on user's experiences and what works and what doesn't work.   We currently are running a Vista 8.03.408 Progress DB with about 10GB database.  We have purchases licenses for Epicor 10 and SQL Server.

 

If we use the built-in tools to migrate from 8-9-10 is this something a person who has installed 8 and 10 can migrate the database without outside help?  What is some of the data in 8 is data we wish not to migrate to 10?  Can we select the data that comes over?  What about using the DMT tool to extract the data from 8 directly into 10?

 

We are also using a Hyper-V Windows 2008 machine that runs on a  DC 2012 Server.  I was thinking of installing another Hyper-V Windows 2012R2 machine with SQL Server 2012R2.   The Hyper-V settings, do most users host the Hyper-V VHDX file on a separate drive, i.e., SAS/NAS or on a separate share with SMB 3.0 that provides redundancy across machines? 

 

Thanks for the feedback in advance.

 

--SF

 

 

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

 



Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.






Stephen Edginton (Beng) | Solutions & Technical Director

Mobile:  +44 7734 858415
DDI:  +44 121 314 1179
Main:  +44 (0) 121 314 1170
Web:  www.dotnetit.co.uk

Dot Net IT Limited, One St Kenelm Court, Steel Park Road, Halesowen, B62 8HD, United Kingdom.

DotNetIT

Epicor Platinum Partner

Epicor Alliance Partner