Progress v6 vs. MS SQL 
Author Message
 Progress v6 vs. MS SQL

Any feeback on migrating an existing Progress v6 db to Progress v8 vs.
moving to MS SQL server. 1000 employee/12 location firm with WAN.

The clients are going from DOS to Windows NT 4.0 at the desktop and NT
will be the standard NOS on the backend.

What are the challenges in the migration and what is the justification
for dropping Progress?

Please advise.



Mon, 28 Aug 2000 03:00:00 GMT
 Progress v6 vs. MS SQL

Just when you think you're all alone in the world, along comes

Quote:
>Any feeback on migrating an existing Progress v6 db to Progress v8 vs.
>moving to MS SQL server. 1000 employee/12 location firm with WAN.

I seem to be facing the same problem.  We are a Motorola 8840 shop
with almost all of our apps in Prog V.6 but we also have 5 NT 4.0
servers running office automation apps.  When I came on board, the
decision to migrate the 8840 load to multiple SCO servers had already
been made.  I  delayed the project long enough to figure out what was
where and why.  Now I'd really like to find another job :-).  

We have 500 stations (WFW, WinNT 4.0) accessing  37 text based
Progress applications.  All applications are critical to either
revenue production or service delivery.  Last year at this time, my
predecessor converted our unlimited Progress 6 (M88k) to a 20 and a 40
user workgroup and 8 developer seats on SCO and upgraded to Version
8.1.  Total cost - approximately $9,500.00.  

Unfortunately, we average 60 concurrent users over a 12 hour day.
When our vendor confirmed the number and type of converted seats last
week, I asked for an estimate to convert our 60 workgroup licenses to
70 Enterprise usersI almost fell over -- $35,000.00.  I believe I can
buy an unlimited license for MS SQL for 25,000.00.  

The vendor who won our hardware replacement bid specializes in
Progress. They claimn to have had good results in converting text
based V 6 apps to NT then upgrading to V8.  I probably won't find out
as the current plan is to convert to SCO V6 and then.....

My reaction last September was to not change the db and to stay away
from SCO.  I felt that we would lose up to 18 months in retraining
programmers to write to another db and more if we had to do GUIs.  
 My opinion hasn't changed, even though I did fold on the SCO issue..
I don't have the staff to write client front ends, and if I did, I
don't  have the staff to run around and install them.  Progress
programmers aren't really plentiful around here (almost as scarce as
people who have heard of progress).  

Progress has a great 4GL, not hard to learn, darned powerful when its
mastered.  It is not a "popular" DB and finding people who have even
heard of it  isn't easy.  I don't have, and don't need ,a full time
DBA with V6, don;t know about V8.      

Why would I drop it?  Lack of experienced help (yeah, everything has
that problem now), I don't like their website, and, at $600.00+ per
seat in the Enterprise edition, I don't know that I want to afford
it.,

Quote:
>The clients are going from DOS to Windows NT 4.0 at the desktop and NT
>will be the standard NOS on the backend.

>What are the challenges in the migration and what is the justification
>for dropping Progress?

>Please advise.



Mon, 28 Aug 2000 03:00:00 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. VB3.0 call SQL stored procedure in v6.5 vs v6.0

2. Progress v6 (on Unix) ODBC drivers availabilty on MS-Windows

3. MS SQL vs Progress

4. Progress vs. MS SQL Server

5. Progress vs. MS SQL Server

6. MS SQL vs Progress

7. Sybase ASA vs MS Access vs MS SQL Server

8. Sybase ASA vs MS Access vs MS SQL Server

9. Sybase ASA vs MS Access vs MS SQL Server

10. Progress: Progress V6 on SunOS - dynamicly linked?? (crosspost)

11. MS SQL v6 and SQL Links

12. MS SQL 2000 vs MS SQL 7


 
Powered by phpBB® Forum Software