Progress vs. SQL Server 
Author Message
 Progress vs. SQL Server

Hi All

We had been planning to write a new system based on
C#, .Net, SQL Server etc etc but the bosses have had their
interest grabbed by someone else's Progress app that "does
everything we need".  I'm currently trying to conduct a
sensible, unemotional critique of the system in order to
help them make a decision (How do you communicate
professionally that your heart and mind are
yelling "NO!"??)

What I'm after are:
-any stories from anyone else who has found themselves in
this position.
- any research references comparing Progress to SQLS or
Progress Dev tools to VS.
- any other ammo that I might be able to use.

Anything will be gratefully received.

Jon



Sat, 03 Sep 2005 19:26:08 GMT
 Progress vs. SQL Server

One thing, that is for SQL Server and against progress is, that with SQL
Server you can always upgrade to a newer version. With Progress between
version 6 and 7 was a complete rewrite. Also SQL Server can be the database
for a multitude of languages, whereas Progress has in theory also support
for an number of languages but in pratice only supports their own client
based language.



Quote:
> Hi All

> We had been planning to write a new system based on
> C#, .Net, SQL Server etc etc but the bosses have had their
> interest grabbed by someone else's Progress app that "does
> everything we need".  I'm currently trying to conduct a
> sensible, unemotional critique of the system in order to
> help them make a decision (How do you communicate
> professionally that your heart and mind are
> yelling "NO!"??)

> What I'm after are:
> -any stories from anyone else who has found themselves in
> this position.
> - any research references comparing Progress to SQLS or
> Progress Dev tools to VS.
> - any other ammo that I might be able to use.

> Anything will be gratefully received.

> Jon



Sat, 03 Sep 2005 19:51:16 GMT
 Progress vs. SQL Server
My co-workers & I have worked with Progress in the past because it is what a
few of our clients use. There is running rate of about 97% disgust, and we
have all had horrible experiences with integration. The ODBC driver is
available if you're willing to pay, but plan on spending several hours on
setup, and another week or so to figure out how to make your SQL statements
work properly (depending on how many calls you have written). Overall, it's
sketchy at best, and completely unintelligible at worst. Around our shop,
it's earned the name "Digress". I hate it, and wish you luck in persuading
your employer to steer clear.


Quote:
> Hi All

> We had been planning to write a new system based on
> C#, .Net, SQL Server etc etc but the bosses have had their
> interest grabbed by someone else's Progress app that "does
> everything we need".  I'm currently trying to conduct a
> sensible, unemotional critique of the system in order to
> help them make a decision (How do you communicate
> professionally that your heart and mind are
> yelling "NO!"??)

> What I'm after are:
> -any stories from anyone else who has found themselves in
> this position.
> - any research references comparing Progress to SQLS or
> Progress Dev tools to VS.
> - any other ammo that I might be able to use.

> Anything will be gratefully received.

> Jon



Sat, 03 Sep 2005 22:43:11 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. Progress vs Oracel or SQL Server

2. Progress vs. MS SQL Server

3. Progress vs. MS SQL Server

4. Microsoft SQL Server 6.5 Vs. Progress

5. sql server vs sybase sql server vs oracle

6. Progress V9 vs SQL Server 7

7. Sql Server vs Oracle vs Ibm vs....

8. Access vs SQL Server vs Sybase vs Oracle

9. Oracle vs SQL Server vs Informix vs Sybase

10. Discussion please: Progress DB vs. Adaptive Server Anywhere

11. Discussion please: Progress DB vs. Adaptive Server Anywhere

12. SQL Server 7.0 vs SQL Server 2000: invalid column width


 
Powered by phpBB® Forum Software