E9.05 conversion from Progress to SQL

Three options I'm aware of, if you're looking for SQL server/SSRS
reporting capabilities:



Convert your main database to SQL server. If you're already on Epicor
9.05, this requires a re-install of Epicor server software as well as
the database conversion.



Leave main database in Progress, and use replication server to copy to a
SQL server database for reporting etc. I believe the replicated data
runs about a minute behind live. Requires replication server license
etc.



Use SQL server DTS (or Integration Services or whatever its called this
year) + ODBC to transfer data as required from Progress to a SQL
reporting database. These can be entire tables on a schedule, or
triggered on demand from a stored procedure when somebody requests a
report. When using on-demand, you can pass user specified report
parameters into the DTS package, so it only pulls the few rows required
for the report. We did this in Vantage 6, and got slow-but-acceptable
report performance for live data.



Brian.



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of sbraudrick@...
Sent: Wednesday, August 03, 2011 4:00 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: E9.05 conversion from Progress to SQL





It would / does, sort of. What I am doing now is moving data from
Progress to an old SQL 2000 instance I have using Data Transformation
Services. It works, but is only updated a few times a day because I
don't want to negatively impact the Progress performance.

I'm guessing I should look in to Replication server if I want more up to
date data in the reporting DB.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"cubcrafters_it" <jason.navarrete@...> wrote:
>
> Sean,
>
> My understanding is that you can run a SQL reporting server (even SQL
Server Express if you DB is small enough) and replicate your Progress
database to SQL for the purposes of reporting.
>
> Would that work for you?
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"sbraudrick@" <sbraudrick@> wrote:
> >
> > We're in a 9.05.603 / 10.2A Progress 64-bit environment and are
discovering that, for reporting and integration reasons, it might be
easier if we were a SQL environment. Has anyone done a conversion from
Progress to SQL? What would be involved?
> >
> > Sean
> >
>





[Non-text portions of this message have been removed]
We're in a 9.05.603 / 10.2A Progress 64-bit environment and are discovering that, for reporting and integration reasons, it might be easier if we were a SQL environment. Has anyone done a conversion from Progress to SQL? What would be involved?

Sean
This is definately a thread for me to keep an eye on.

Until recently I worked for a company where we were using V8 on MS SQL, and where I am now we are on V8 on Progress, and God do I miss MS SQL and using stored procedure and SSRS for reports etc.

So now I'm in the process of upgrading our V8 Progress to 9.05.605 MS SQL x64.

For me the upgrade for the data will probably be V8 Progress -> 9.04 Progress -> 9.05 Progress -> 9.05 MS SQL. So my final step will be what you want to do.

--- In vantage@yahoogroups.com, "sbraudrick@..." <sbraudrick@...> wrote:
>
> We're in a 9.05.603 / 10.2A Progress 64-bit environment and are discovering that, for reporting and integration reasons, it might be easier if we were a SQL environment. Has anyone done a conversion from Progress to SQL? What would be involved?
>
> Sean
>
Just to add something to the mix, I recently did all these steps, and one of
the tricky parts was the fact that back in version 8.03 not all data rules
were enforced by OpenEdge when it came to storing data in a field.

For example, EcoGroup.Description is supposed to be limited to 30
characters, however in Vantage 8.03 it was allowing for entry of longer than
30 characters to be stored. This ends up causing a problem down the line and
I needed to run some DB direct commands in order to truncate the fields so
they would fit and would convert properly(at all) to SQL which actually
enforces the data field rules. There were another dozen or so fields that
had similar problems.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Clive
Sent: Wednesday, August 03, 2011 4:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: E9.05 conversion from Progress to SQL

This is definately a thread for me to keep an eye on.

Until recently I worked for a company where we were using V8 on MS SQL, and
where I am now we are on V8 on Progress, and God do I miss MS SQL and using
stored procedure and SSRS for reports etc.

So now I'm in the process of upgrading our V8 Progress to 9.05.605 MS SQL
x64.

For me the upgrade for the data will probably be V8 Progress -> 9.04
Progress -> 9.05 Progress -> 9.05 MS SQL. So my final step will be what you
want to do.

--- In vantage@yahoogroups.com, "sbraudrick@..." <sbraudrick@...> wrote:
>
> We're in a 9.05.603 / 10.2A Progress 64-bit environment and are
discovering that, for reporting and integration reasons, it might be easier
if we were a SQL environment. Has anyone done a conversion from Progress to
SQL? What would be involved?
>
> Sean
>




------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
Sean,

My understanding is that you can run a SQL reporting server (even SQL Server Express if you DB is small enough) and replicate your Progress database to SQL for the purposes of reporting.

Would that work for you?

--- In vantage@yahoogroups.com, "sbraudrick@..." <sbraudrick@...> wrote:
>
> We're in a 9.05.603 / 10.2A Progress 64-bit environment and are discovering that, for reporting and integration reasons, it might be easier if we were a SQL environment. Has anyone done a conversion from Progress to SQL? What would be involved?
>
> Sean
>
>data rules
>Field width

I recently encountered a similar issue.
The DMT tool wrote some ShipVia descriptions that were too long.

This caught our attention after going live - as random BOL processing failures. I'm sure you can guess, these can be a pain to track down.
The only error message was in the server log "Unable to update BOLHED field". We shortened the ShipVia descriptions and everything was fine.

>to SQL which actually
> enforces the data field rules.
I suspect the real field width problem is in the BOLHed table.
Because... later I tested the Ship Via entry screen.
I was able to enter descriptions that were "too" long.
E9.04.506

--- In vantage@yahoogroups.com, "Ned" <TechnoBabbly@...> wrote:
>
> Just to add something to the mix, I recently did all these steps, and one of
> the tricky parts was the fact that back in version 8.03 not all data rules
> were enforced by OpenEdge when it came to storing data in a field.
>
> For example, EcoGroup.Description is supposed to be limited to 30
> characters, however in Vantage 8.03 it was allowing for entry of longer than
> 30 characters to be stored. This ends up causing a problem down the line and
> I needed to run some DB direct commands in order to truncate the fields so
> they would fit and would convert properly(at all) to SQL which actually
> enforces the data field rules. There were another dozen or so fields that
> had similar problems.
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> Clive
> Sent: Wednesday, August 03, 2011 4:18 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: E9.05 conversion from Progress to SQL
>
> This is definately a thread for me to keep an eye on.
>
> Until recently I worked for a company where we were using V8 on MS SQL, and
> where I am now we are on V8 on Progress, and God do I miss MS SQL and using
> stored procedure and SSRS for reports etc.
>
> So now I'm in the process of upgrading our V8 Progress to 9.05.605 MS SQL
> x64.
>
> For me the upgrade for the data will probably be V8 Progress -> 9.04
> Progress -> 9.05 Progress -> 9.05 MS SQL. So my final step will be what you
> want to do.
>
> --- In vantage@yahoogroups.com, "sbraudrick@" <sbraudrick@> wrote:
> >
> > We're in a 9.05.603 / 10.2A Progress 64-bit environment and are
> discovering that, for reporting and integration reasons, it might be easier
> if we were a SQL environment. Has anyone done a conversion from Progress to
> SQL? What would be involved?
> >
> > Sean
> >
>
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
> already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and
> Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
It would / does, sort of. What I am doing now is moving data from Progress to an old SQL 2000 instance I have using Data Transformation Services. It works, but is only updated a few times a day because I don't want to negatively impact the Progress performance.

I'm guessing I should look in to Replication server if I want more up to date data in the reporting DB.

--- In vantage@yahoogroups.com, "cubcrafters_it" <jason.navarrete@...> wrote:
>
> Sean,
>
> My understanding is that you can run a SQL reporting server (even SQL Server Express if you DB is small enough) and replicate your Progress database to SQL for the purposes of reporting.
>
> Would that work for you?
>
> --- In vantage@yahoogroups.com, "sbraudrick@" <sbraudrick@> wrote:
> >
> > We're in a 9.05.603 / 10.2A Progress 64-bit environment and are discovering that, for reporting and integration reasons, it might be easier if we were a SQL environment. Has anyone done a conversion from Progress to SQL? What would be involved?
> >
> > Sean
> >
>