SQL vs Progress

Does anyone have a document on Replication Server
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Joe Rojas <jrojas@...>
Sender: vantage@yahoogroups.com
Date: Thu, 16 Jun 2011 16:13:17
To: <vantage@yahoogroups.com>
Reply-To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL vs Progress

We purchased the Replication Server module and we have, in my opinion,
the best of both worlds.

Epicor is running off of Progress and we have an almost real time copy
of the data in SQL Server.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Blake Clemens
Sent: Thursday, June 16, 2011 4:06 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL vs Progress





We went with Progress (not my decision). Now I wish we would have
chosen SQL because all our third party software use SQL.

Thanks,

Blake Clemens

IT Systems Engineer

Delmarva Millwork Corporation

(800) 360-2364 x132

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of Bethany Rye
Sent: Thursday, June 16, 2011 11:48 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] SQL vs Progress

The reason we chose SQL was that if you have 3rd party apps that
integrate
with Epicor and they require SQL (such as Advanced Quality from IQS),
then
you are going to need SQL anyway. We did it to have consistency with
what
we are using for our databases.

Beth Rye

IT Director

CIGNYS

***ITAR NOTICE***

This e-mail and/or the attached documents may contain technical data
within
the definition of the International Traffic in Arms regulations, and are
subject to the export control laws of the US Government. Transfer of
this
data by any means to a foreign person, whether in the US or abroad,
without
an export license or other approval from the US Department of State, is
prohibited. No portion of this e-mail or its attachment(s) may be
reproduced
without written consent of CIGNYS. If you are not the intended recipient
or
believe that you may have received this document in error, please notify
the
sender and delete this e-mail and any attachments immediately.

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Richard
Sent: Thursday, June 16, 2011 11:09 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] SQL vs Progress

Which is the best WITH Vantage?

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]
We just purchased the Vantage product and are debating which database
platform to use. We currently use Microsoft SQL 2000 but understand
that Progress is the native structure Epicor uses. We are thinking of
starting up on SQL 2000 for easy of implementing and running it for a
year or so, then migrating to Progress. Has anyone done this or are we
better off picking one platform and staying with it? Of course, which
one is better? Everyone we have talked with uses Progress and we would
be interested in hearing from someone who has uses Microsoft SQL or
has used both.
warning: biased view.
This is my experience and Im sure everyone else has a
better experience... but...

Im a sql server guy but the company Im at now uses progress
(Vantage is new here). After having issue in progress
explorer with it consuming 50% cpu for no good reason
(clicking to see properties of an item doesn't seem like a
good reason to consume 50% cpu indefinitely), admin service
stopping and not starting up, app servers not showing any
status when you ask to see status, having no nice graphical
scheduling/db tools, and having a problem starting an app
server back up (two reboots required) when the admin ports
just went down - Im still extremely partial to sql.

I was told by the support person that sql is not
recommended and that if there was a sql issue they would
have to locate a resource for it and it wold take longer to
troubleshoot (essentially saying they didn't know it well).
However....sales guy told me about 40% of new installs are
sql based. Consultant said sql used to be slower, and is
now about equal. I don't trust progress to be stable for us
only because of the issues I had with it my first two weeks
here (never had same issues with sql server and admin tools
for sql can't be touched by progress). HOWEVER - I have
been told their progress customers have been happy and its
been stable for them... so take that how you want it.

Its my understanding as for "native structure" that they
use progress 4gl components for the app logic (c# front
end). So the progress components call out to progress or
via odbc to sql. Its too bad app logic isn't .net based as
well and they could then use the sql managed provider to
gain more speed out of it. I want to use sql and am in the
progress of evaluating licensing here... so that may be a
switch for us.




On Tue, 10 Oct 2006 20:11:43 -0000
"ddave97" <ddave97@...> wrote:
> We just purchased the Vantage product and are debating
> which database
> platform to use. We currently use Microsoft SQL 2000 but
> understand
> that Progress is the native structure Epicor uses. We are
> thinking of
> starting up on SQL 2000 for easy of implementing and
> running it for a
> year or so, then migrating to Progress. Has anyone done
> this or are we
> better off picking one platform and staying with it? Of
> course, which
> one is better? Everyone we have talked with uses Progress
> and we would
> be interested in hearing from someone who has uses
> Microsoft SQL or
> has used both.
>
>
>

---------------------------------------------------------------------
Web mail provided by NuNet, Inc. The Premier National provider.
http://www.nni.com/
Warning...another biased view.

We've been using Progress for 10 years. As far as using db tools
etc...we haven't needed to use any. Once you get the database tuned for
your implementation you shouldn't have to fool with it. We do review
database settings after every upgrade. But once the changes are made,
we're done. If you're a mid-sized manufacturer with a very lean I.T.
staff then Progress is the way to go. If you have resources for a
larger I.T. staff and wish to do some customization and/or interfacing
with the database then Progress or SQL are options. If you have sites
in Asia (as we have several) you may want to consider Progress as I
understand (though, this may be incorrect) that there are issues with
SQL and Asian languages.

For us, Progress just purrs quietly in the background doing it's job.
About as low maintenace as you can get. Which, is exactly the way I
like it! "Get it and forget it"!

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Adam Tuliper
Sent: Tuesday, October 10, 2006 2:28 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] SQL vs Progress

warning: biased view.
This is my experience and Im sure everyone else has a better
experience... but...

Im a sql server guy but the company Im at now uses progress (Vantage is
new here). After having issue in progress explorer with it consuming 50%
cpu for no good reason (clicking to see properties of an item doesn't
seem like a good reason to consume 50% cpu indefinitely), admin service
stopping and not starting up, app servers not showing any status when
you ask to see status, having no nice graphical scheduling/db tools, and
having a problem starting an app server back up (two reboots required)
when the admin ports just went down - Im still extremely partial to sql.


I was told by the support person that sql is not recommended and that if
there was a sql issue they would have to locate a resource for it and it
wold take longer to troubleshoot (essentially saying they didn't know it
well).
However....sales guy told me about 40% of new installs are sql based.
Consultant said sql used to be slower, and is now about equal. I don't
trust progress to be stable for us only because of the issues I had with
it my first two weeks here (never had same issues with sql server and
admin tools for sql can't be touched by progress). HOWEVER - I have been
told their progress customers have been happy and its been stable for
them... so take that how you want it.

Its my understanding as for "native structure" that they use progress
4gl components for the app logic (c# front end). So the progress
components call out to progress or via odbc to sql. Its too bad app
logic isn't .net based as well and they could then use the sql managed
provider to gain more speed out of it. I want to use sql and am in the
progress of evaluating licensing here... so that may be a switch for us.




On Tue, 10 Oct 2006 20:11:43 -0000
"ddave97" <ddave97@...> wrote:
> We just purchased the Vantage product and are debating which database
> platform to use. We currently use Microsoft SQL 2000 but understand
> that Progress is the native structure Epicor uses. We are thinking of
> starting up on SQL 2000 for easy of implementing and running it for a
> year or so, then migrating to Progress. Has anyone done this or are we

> better off picking one platform and staying with it? Of course, which
> one is better? Everyone we have talked with uses Progress and we would

> be interested in hearing from someone who has uses Microsoft SQL or
> has used both.
>
>
>

---------------------------------------------------------------------
Web mail provided by NuNet, Inc. The Premier National provider.
http://www.nni.com/



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/links
Yahoo! Groups Links
I agree with Mike 100%. We have been on Vantage and Progress since 1997. Progress in our shop has been bullet proof (knock on wood). No need to play with it. If you are having stability issues then you have an installation problem. Get with support and they can help you figure out what is wrong.

Todd


________________________________

From: vantage@yahoogroups.com on behalf of Mike Lowe
Sent: Tue 10/10/2006 6:02 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL vs Progress



Warning...another biased view.

We've been using Progress for 10 years. As far as using db tools
etc...we haven't needed to use any. Once you get the database tuned for
your implementation you shouldn't have to fool with it. We do review
database settings after every upgrade. But once the changes are made,
we're done. If you're a mid-sized manufacturer with a very lean I.T.
staff then Progress is the way to go. If you have resources for a
larger I.T. staff and wish to do some customization and/or interfacing
with the database then Progress or SQL are options. If you have sites
in Asia (as we have several) you may want to consider Progress as I
understand (though, this may be incorrect) that there are issues with
SQL and Asian languages.

For us, Progress just purrs quietly in the background doing it's job.
About as low maintenace as you can get. Which, is exactly the way I
like it! "Get it and forget it"!

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf
Of Adam Tuliper
Sent: Tuesday, October 10, 2006 2:28 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] SQL vs Progress

warning: biased view.
This is my experience and Im sure everyone else has a better
experience... but...

Im a sql server guy but the company Im at now uses progress (Vantage is
new here). After having issue in progress explorer with it consuming 50%
cpu for no good reason (clicking to see properties of an item doesn't
seem like a good reason to consume 50% cpu indefinitely), admin service
stopping and not starting up, app servers not showing any status when
you ask to see status, having no nice graphical scheduling/db tools, and
having a problem starting an app server back up (two reboots required)
when the admin ports just went down - Im still extremely partial to sql.

I was told by the support person that sql is not recommended and that if
there was a sql issue they would have to locate a resource for it and it
wold take longer to troubleshoot (essentially saying they didn't know it
well).
However....sales guy told me about 40% of new installs are sql based.
Consultant said sql used to be slower, and is now about equal. I don't
trust progress to be stable for us only because of the issues I had with
it my first two weeks here (never had same issues with sql server and
admin tools for sql can't be touched by progress). HOWEVER - I have been
told their progress customers have been happy and its been stable for
them... so take that how you want it.

Its my understanding as for "native structure" that they use progress
4gl components for the app logic (c# front end). So the progress
components call out to progress or via odbc to sql. Its too bad app
logic isn't .net based as well and they could then use the sql managed
provider to gain more speed out of it. I want to use sql and am in the
progress of evaluating licensing here... so that may be a switch for us.

On Tue, 10 Oct 2006 20:11:43 -0000
"ddave97" <ddave97@... <mailto:ddave97%40yahoo.com> > wrote:
> We just purchased the Vantage product and are debating which database
> platform to use. We currently use Microsoft SQL 2000 but understand
> that Progress is the native structure Epicor uses. We are thinking of
> starting up on SQL 2000 for easy of implementing and running it for a
> year or so, then migrating to Progress. Has anyone done this or are we

> better off picking one platform and staying with it? Of course, which
> one is better? Everyone we have talked with uses Progress and we would

> be interested in hearing from someone who has uses Microsoft SQL or
> has used both.
>
>
>

----------------------------------------------------------
Web mail provided by NuNet, Inc. The Premier National provider.
http://www.nni.com/ <http://www.nni.com/>

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/. <http://groups.yahoo.com/group/vantage/files/.>
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages <http://groups.yahoo.com/group/vantage/messages>
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links <http://groups.yahoo.com/group/vantage/links>
Yahoo! Groups Links






This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.

[Non-text portions of this message have been removed]
Hi
We migrated from ver. 6 progress to 8 in SQL. So I cannot make a real
comparison between both. At the beginning I was exited about using SQL with
many other tools in the market BUT, unfortunately Vantage was designed in
Progress and it uses SQL server as data repository only. There is no views,
store procedures, triggers, etc in SQL. As result of this, you do not take
any advance of the db server and because everything is via Progress/ODBC
makes the application performance not good.

The other major drawback is that the app server is connected to SQL via
ODBC. If, for some reason, you implement triggers or store procedures in the
SQL server and they create a message that is sent back to the app, for sure
the whole application will crash and you will need to restart the app
servers. If we need to run SQL code in the server, we use VB.net to connect
direct to SQL (In customizations).

If you want to create triggers or extra code, the safer in my opinion, is
doing Progress procedures to run them in the app server (what they called
�Super-procedures�)

In my opinion you need to evaluate carefully what are you going to get from
or use for. You can take advantage of the SQL in many other things but the
Vantage performance is not so good.

Regards,
Jose Ferrer



>From: "ddave97" <ddave97@...>
>Reply-To: vantage@yahoogroups.com
>To: vantage@yahoogroups.com
>Subject: [Vantage] SQL vs Progress
>Date: Tue, 10 Oct 2006 20:11:43 -0000
>
>We just purchased the Vantage product and are debating which database
>platform to use. We currently use Microsoft SQL 2000 but understand
>that Progress is the native structure Epicor uses. We are thinking of
>starting up on SQL 2000 for easy of implementing and running it for a
>year or so, then migrating to Progress. Has anyone done this or are we
>better off picking one platform and staying with it? Of course, which
>one is better? Everyone we have talked with uses Progress and we would
>be interested in hearing from someone who has uses Microsoft SQL or
>has used both.
>
>
>

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
You have to have a reason for SQL. Without one, choose OpenEdge/Progress.

----- Original Message -----
From: "Jose Ferrer" <ferrerj@...>
To: <vantage@yahoogroups.com>
Sent: Tuesday, October 10, 2006 5:50 PM
Subject: RE: [Vantage] SQL vs Progress


> Hi
> We migrated from ver. 6 progress to 8 in SQL. So I cannot make a real
> comparison between both. At the beginning I was exited about using SQL
> with
> many other tools in the market BUT, unfortunately Vantage was designed in
> Progress and it uses SQL server as data repository only. There is no
> views,
> store procedures, triggers, etc in SQL. As result of this, you do not take
> any advance of the db server and because everything is via Progress/ODBC
> makes the application performance not good.
>
> The other major drawback is that the app server is connected to SQL via
> ODBC. If, for some reason, you implement triggers or store procedures in
> the
> SQL server and they create a message that is sent back to the app, for
> sure
> the whole application will crash and you will need to restart the app
> servers. If we need to run SQL code in the server, we use VB.net to
> connect
> direct to SQL (In customizations).
>
> If you want to create triggers or extra code, the safer in my opinion, is
> doing Progress procedures to run them in the app server (what they called
> "Super-procedures")
>
> In my opinion you need to evaluate carefully what are you going to get
> from
> or use for. You can take advantage of the SQL in many other things but the
> Vantage performance is not so good.
>
> Regards,
> Jose Ferrer
>
>
>
>>From: "ddave97" <ddave97@...>
>>Reply-To: vantage@yahoogroups.com
>>To: vantage@yahoogroups.com
>>Subject: [Vantage] SQL vs Progress
>>Date: Tue, 10 Oct 2006 20:11:43 -0000
>>
>>We just purchased the Vantage product and are debating which database
>>platform to use. We currently use Microsoft SQL 2000 but understand
>>that Progress is the native structure Epicor uses. We are thinking of
>>starting up on SQL 2000 for easy of implementing and running it for a
>>year or so, then migrating to Progress. Has anyone done this or are we
>>better off picking one platform and staying with it? Of course, which
>>one is better? Everyone we have talked with uses Progress and we would
>>be interested in hearing from someone who has uses Microsoft SQL or
>>has used both.
>>
>>
>>
>
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
>
>
> 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/links
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
I have extensive experience with SQL and Oracle and I must say that I'm very happy with the performance of Progress. Like most enterprise DBs, if it is not installed and configured correctly, Progress is very unforgiving. I would recommend that you consider a reinstall. First make sure you have the optimum hardware configuration, then execute systernal's tcpviewer to compile a list of all ports that are committed to other processes to determine if there will be any conflicts. After reinstalling, you should enroll in Epicor's admin and DB tuning class (it's a one day class) use the provided workbook to determine the optimum tuning parameters for your enviroment and apply them to your installation.

The choice ultimately is yours, but IMO, something is wrong with the way your Progress is installed and or configured.

________________________________

From: vantage@yahoogroups.com on behalf of Adam Tuliper
Sent: Tue 10/10/2006 5:27 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] SQL vs Progress



warning: biased view.
This is my experience and Im sure everyone else has a
better experience... but...

Im a sql server guy but the company Im at now uses progress
(Vantage is new here). After having issue in progress
explorer with it consuming 50% cpu for no good reason
(clicking to see properties of an item doesn't seem like a
good reason to consume 50% cpu indefinitely), admin service
stopping and not starting up, app servers not showing any
status when you ask to see status, having no nice graphical
scheduling/db tools, and having a problem starting an app
server back up (two reboots required) when the admin ports
just went down - Im still extremely partial to sql.

I was told by the support person that sql is not
recommended and that if there was a sql issue they would
have to locate a resource for it and it wold take longer to
troubleshoot (essentially saying they didn't know it well).
However....sales guy told me about 40% of new installs are
sql based. Consultant said sql used to be slower, and is
now about equal. I don't trust progress to be stable for us
only because of the issues I had with it my first two weeks
here (never had same issues with sql server and admin tools
for sql can't be touched by progress). HOWEVER - I have
been told their progress customers have been happy and its
been stable for them... so take that how you want it.

Its my understanding as for "native structure" that they
use progress 4gl components for the app logic (c# front
end). So the progress components call out to progress or
via odbc to sql. Its too bad app logic isn't .net based as
well and they could then use the sql managed provider to
gain more speed out of it. I want to use sql and am in the
progress of evaluating licensing here... so that may be a
switch for us.




On Tue, 10 Oct 2006 20:11:43 -0000
"ddave97" <ddave97@...> wrote:
> We just purchased the Vantage product and are debating
> which database
> platform to use. We currently use Microsoft SQL 2000 but
> understand
> that Progress is the native structure Epicor uses. We are
> thinking of
> starting up on SQL 2000 for easy of implementing and
> running it for a
> year or so, then migrating to Progress. Has anyone done
> this or are we
> better off picking one platform and staying with it? Of
> course, which
> one is better? Everyone we have talked with uses Progress
> and we would
> be interested in hearing from someone who has uses
> Microsoft SQL or
> has used both.
>
>
>

---------------------------------------------------------------------
Web mail provided by NuNet, Inc. The Premier National provider.
http://www.nni.com/



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/links
Yahoo! Groups Links














[Non-text portions of this message have been removed]
How simple is it to get raw data out of your Progress Vantage database
in a format easily imported into Microsoft Office products?
It is really simple.

Set up ODBC to connect to the Database. Then in Excel or Access run a query
to the Table and Fields you wish to extract. Now it is the app.

Scott Litzau, MCP
Olympus Flag & Banner
Information Systems Manager
scott.litzau@...
P: 414-365-9732
F: 414-355-1931

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
acp2g99
Sent: Wednesday, January 17, 2007 1:23 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: SQL vs Progress


How simple is it to get raw data out of your Progress Vantage database
in a format easily imported into Microsoft Office products?





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/links
Yahoo! Groups Links
--- In vantage@yahoogroups.com, "acp2g99" <acp2g99@...> wrote:
>
> How simple is it to get raw data out of your Progress Vantage
database
> in a format easily imported into Microsoft Office products?
>

We are on version 8.00.810B - Progress
If you have list views (dashboards) all that is required is right
click and copy. Dashboards are easily created. There are companies
that will custom design for you if necessary.
Which is the best WITH Vantage?
Oh gosh, do you REALLY want to start another debate? :-)



Do a little search on this topic from previous threads. You'll see that
anyone over the age of 40 will prefer Progress. Anyone younger will
choose SQL.



Again, a little humor...... but SQL is the best bet IMO. Opens up a
world of opportunity and is much easier to manage and administrate.







________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Richard
Sent: Thursday, June 16, 2011 11:09 AM
To: vantage@yahoogroups.com
Subject: [Vantage] SQL vs Progress





Which is the best WITH Vantage?





[Non-text portions of this message have been removed]
Just search the list there are like 30 entries on the topic. And frankly it
always blows up out of proportion.

*Jose C Gomez*
*Software Engineer*
*
*
*checkout my new blog <http://www.usdoingstuff.com> *
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*



On Thu, Jun 16, 2011 at 11:16 AM, Vic Drecchio <vic.drecchio@...>wrote:

> **
>
>
> Oh gosh, do you REALLY want to start another debate? :-)
>
> Do a little search on this topic from previous threads. You'll see that
> anyone over the age of 40 will prefer Progress. Anyone younger will
> choose SQL.
>
> Again, a little humor...... but SQL is the best bet IMO. Opens up a
> world of opportunity and is much easier to manage and administrate.
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Richard
> Sent: Thursday, June 16, 2011 11:09 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] SQL vs Progress
>
>
> Which is the best WITH Vantage?
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]
The reason we chose SQL was that if you have 3rd party apps that integrate
with Epicor and they require SQL (such as Advanced Quality from IQS), then
you are going to need SQL anyway. We did it to have consistency with what
we are using for our databases.



Beth Rye

IT Director

CIGNYS



***ITAR NOTICE***

This e-mail and/or the attached documents may contain technical data within
the definition of the International Traffic in Arms regulations, and are
subject to the export control laws of the US Government. Transfer of this
data by any means to a foreign person, whether in the US or abroad, without
an export license or other approval from the US Department of State, is
prohibited. No portion of this e-mail or its attachment(s) may be reproduced
without written consent of CIGNYS. If you are not the intended recipient or
believe that you may have received this document in error, please notify the
sender and delete this e-mail and any attachments immediately.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Richard
Sent: Thursday, June 16, 2011 11:09 AM
To: vantage@yahoogroups.com
Subject: [Vantage] SQL vs Progress





Which is the best WITH Vantage?





[Non-text portions of this message have been removed]
I'd say that if you're going to try and integrate 3rd party stuff and mess
with the DB, go with SQL.

If you just wanna run vanilla Epicor and use the built in customization
functionality, Progress is probably a bit easier to manage.

On Thu, Jun 16, 2011 at 11:47 AM, Bethany Rye <brye@...> wrote:

>
>
> The reason we chose SQL was that if you have 3rd party apps that integrate
> with Epicor and they require SQL (such as Advanced Quality from IQS), then
> you are going to need SQL anyway. We did it to have consistency with what
> we are using for our databases.
>
> Beth Rye
>
> IT Director
>
> CIGNYS
>
> ***ITAR NOTICE***
>
> This e-mail and/or the attached documents may contain technical data within
> the definition of the International Traffic in Arms regulations, and are
> subject to the export control laws of the US Government. Transfer of this
> data by any means to a foreign person, whether in the US or abroad, without
> an export license or other approval from the US Department of State, is
> prohibited. No portion of this e-mail or its attachment(s) may be
> reproduced
> without written consent of CIGNYS. If you are not the intended recipient or
> believe that you may have received this document in error, please notify
> the
> sender and delete this e-mail and any attachments immediately.
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of
> Richard
> Sent: Thursday, June 16, 2011 11:09 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] SQL vs Progress
>
> Which is the best WITH Vantage?
>
> [Non-text portions of this message have been removed]
>
>
>



--
*Waffqle Driggers*
*High End Dev, System Design, Profit Drinking
*
*:: 904.962.2887*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]
Understood! Thank you very much.

--- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
>
> Just search the list there are like 30 entries on the topic. And frankly it
> always blows up out of proportion.
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *
> *checkout my new blog <http://www.usdoingstuff.com> *
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
> <http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
> <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
> <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
> <http://www.usdoingstuff.com>
>
> *Quis custodiet ipsos custodes?*
>
>
>
> On Thu, Jun 16, 2011 at 11:16 AM, Vic Drecchio <vic.drecchio@...>wrote:
>
> > **
> >
> >
> > Oh gosh, do you REALLY want to start another debate? :-)
> >
> > Do a little search on this topic from previous threads. You'll see that
> > anyone over the age of 40 will prefer Progress. Anyone younger will
> > choose SQL.
> >
> > Again, a little humor...... but SQL is the best bet IMO. Opens up a
> > world of opportunity and is much easier to manage and administrate.
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > Of Richard
> > Sent: Thursday, June 16, 2011 11:09 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] SQL vs Progress
> >
> >
> > Which is the best WITH Vantage?
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
I've used both and I vote for MS SQL.

[Non-text portions of this message have been removed]
We went with Progress (not my decision). Now I wish we would have
chosen SQL because all our third party software use SQL.



Thanks,

Blake Clemens

IT Systems Engineer

Delmarva Millwork Corporation

(800) 360-2364 x132

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Bethany Rye
Sent: Thursday, June 16, 2011 11:48 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL vs Progress





The reason we chose SQL was that if you have 3rd party apps that
integrate
with Epicor and they require SQL (such as Advanced Quality from IQS),
then
you are going to need SQL anyway. We did it to have consistency with
what
we are using for our databases.

Beth Rye

IT Director

CIGNYS

***ITAR NOTICE***

This e-mail and/or the attached documents may contain technical data
within
the definition of the International Traffic in Arms regulations, and are
subject to the export control laws of the US Government. Transfer of
this
data by any means to a foreign person, whether in the US or abroad,
without
an export license or other approval from the US Department of State, is
prohibited. No portion of this e-mail or its attachment(s) may be
reproduced
without written consent of CIGNYS. If you are not the intended recipient
or
believe that you may have received this document in error, please notify
the
sender and delete this e-mail and any attachments immediately.

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Richard
Sent: Thursday, June 16, 2011 11:09 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] SQL vs Progress

Which is the best WITH Vantage?

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
We purchased the Replication Server module and we have, in my opinion,
the best of both worlds.

Epicor is running off of Progress and we have an almost real time copy
of the data in SQL Server.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Blake Clemens
Sent: Thursday, June 16, 2011 4:06 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SQL vs Progress





We went with Progress (not my decision). Now I wish we would have
chosen SQL because all our third party software use SQL.

Thanks,

Blake Clemens

IT Systems Engineer

Delmarva Millwork Corporation

(800) 360-2364 x132

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of Bethany Rye
Sent: Thursday, June 16, 2011 11:48 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] SQL vs Progress

The reason we chose SQL was that if you have 3rd party apps that
integrate
with Epicor and they require SQL (such as Advanced Quality from IQS),
then
you are going to need SQL anyway. We did it to have consistency with
what
we are using for our databases.

Beth Rye

IT Director

CIGNYS

***ITAR NOTICE***

This e-mail and/or the attached documents may contain technical data
within
the definition of the International Traffic in Arms regulations, and are
subject to the export control laws of the US Government. Transfer of
this
data by any means to a foreign person, whether in the US or abroad,
without
an export license or other approval from the US Department of State, is
prohibited. No portion of this e-mail or its attachment(s) may be
reproduced
without written consent of CIGNYS. If you are not the intended recipient
or
believe that you may have received this document in error, please notify
the
sender and delete this e-mail and any attachments immediately.

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Richard
Sent: Thursday, June 16, 2011 11:09 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] SQL vs Progress

Which is the best WITH Vantage?

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]