"pk***@charter.net" wrote:

> Progress is a piece of crap!  Sure it runs on Unix.  But the time
> invested in learning and working with it obscene!  With SQL Server I
> could easily plan a maintenance backup plan and transaction backup plan
> - Progress - well you have to learn about AI files, sizing the BI and
> AI files as well as the data files.  It's a freakin nightmare.  If I
> want to see data in a table, can I simply click on a table and open it
> - NO!  Instead, I have to learn the 4GL language to write a script to
> return records (what if I want to resort those records - write another
> 4GL script and run it again).  But hey, why do you want to see the data
> in the tables (at least that's what I was told by my company)  Progress
> GUI - what a joke.  This database server might have been popular with
> unix but the world today is GUI and Microsoft are the GUI experts.
> Even with the GUI tools in Progress, I still can't click on a table,
> open it and see the records.  Maybe that's not important to others but
> as a dba, it sure is a necessity.  We're working with different
> versions of Progress and none of them integrate with the other.  I've
> spent 2 months now trying to run some simple database maintenance on
> Progress and all I can say is that I hate BI, AI, and D1, D2, D3 files.
>  Give me SQL Server any day where at least I can manage databases in a
> normal logical way without having to deal with a stinkin .ST files and
> prostrct this...prostrct that!!!  Any Progress responses are welcome
> but I'll take you on any day against SQL Server.  If you're a
> Pro-Progress and anti-SQL Server, you're behind the times - get with
> the newest technology and GUI (not a GUI in development.)  I have yet
> to see a true relational database designed in Progress.  Upsizing a
> Progress database into a GUI environment - HA!
>
>

> Progress is a piece of crap!  Sure it runs on Unix.  But the time
> invested in learning and working with it obscene!  With SQL Server I
> could easily plan a maintenance backup plan and transaction backup plan
> - Progress - well you have to learn about AI files, sizing the BI and
> AI files as well as the data files.  It's a freakin nightmare.  If I
> want to see data in a table, can I simply click on a table and open it
> - NO!  Instead, I have to learn the 4GL language to write a script to
> return records (what if I want to resort those records - write another
> 4GL script and run it again).  But hey, why do you want to see the data
> in the tables (at least that's what I was told by my company)  Progress
> GUI - what a joke.  This database server might have been popular with
> unix but the world today is GUI and Microsoft are the GUI experts.
> Even with the GUI tools in Progress, I still can't click on a table,
> open it and see the records.  Maybe that's not important to others but
> as a dba, it sure is a necessity.  We're working with different
> versions of Progress and none of them integrate with the other.  I've
> spent 2 months now trying to run some simple database maintenance on
> Progress and all I can say is that I hate BI, AI, and D1, D2, D3 files.
>  Give me SQL Server any day where at least I can manage databases in a
> normal logical way without having to deal with a stinkin .ST files and
> prostrct this...prostrct that!!!  Any Progress responses are welcome
> but I'll take you on any day against SQL Server.  If you're a
> Pro-Progress and anti-SQL Server, you're behind the times - get with
> the newest technology and GUI (not a GUI in development.)  I have yet
> to see a true relational database designed in Progress.  Upsizing a
> Progress database into a GUI environment - HA!
>