Need Pros and Cons of SQL vs Progress

[tonydt1g3r]

I am currently running Progress 10.0B but we might be switching to SQL Server soon and I am not sure if its a good idea or not. I was hoping with you help I can get a better understanding of which one is better.

SQL Server vs Progress DB

SQL Query Language vs 4gl

 

[KnutHandsome]

Career-wise, moving to SQL Server would be much better - more (standard) skills on your CV, and better salary.

There are several (rather religious) threads on this site that discuss Oracle vs. Progress, and no doubt some of the Oracle arguments will hold for SQL Server, as it is a very comprehensive, powerful system these days.

eg:
http://www.progresstalk.com/showthread.php?t=91281

http://www.progresstalk.com/showthread.php?t=89619

http://www.progresstalk.com/showthread.php?t=97254


Technically (bear in mind my SQL Server knowledge is limited):

Progress is a simpler database to the major platforms, which can be a good thing or bad thing depending on how much you want to DBA vs. develop.

SQL Server is the business end of Microsoft's development platform, with all the advantages that confers (eg. targeted interface from .Net).

The downside of moving to SQL Server (or any other database) is that it doesn't have the 4GL - T-SQL is very limited in comparison. You could if you wanted to retain the advantages of the 4GL run a DataServer against SQL Server, but that would be additional deployment cost, although perhaps you could justify it in reduced development time. Apparently, performance is good.

As for a breakdown of SQL vs 4GL, all I know from my limited experience with SQL is you have to think in set-oriented terms, and it may perform better for large set operations, but I doubt you will be able to write reliable business apps in a similar timeframe - but I'm a 4GL/ADM2 programmer so that opinion should be taken with a pinch of salt.

I just hate the hoops you have to jump through to call anything server/db side from .Net languages.

eg:
http://www.progresstalk.com/showpost.php?p=300850&postcount=13

Perhaps that has improved with web services.


One final point: Microsoft have introduced a db language/interface called LINQ/DLINQ. This seems to be very 4GL-like in its implementation, so may override the final argument against moving to SQL Server.

http://en.wikipedia.org/wiki/Language_Integrated_Query

http://msdn.microsoft.com/data/ref/linq/

more...


One final, final point:

If you intend to provide external (ie. web) access to your data for new/potential customers, then rule Progress DB out straightaway, as the licensing will make this unrealistic.

 

[lord_icon]

RE: SQL Query Language vs 4gl

SQL Query Language vs 4gl

4GL ??????
What is this 4gl to which you refer??
OpenEdge is an ABL (Advanced Business Language) 4GL is soo 90s and outDated

 

[KnutHandsome]

Incidentally, Tony, I've seen your question - conversion/comparison between SQL and (ahem) ABL come up a number of times, mostly on the Peg, but have never seen it answered in depth.

This may be because most Progress programmers don't have great experience of SQL to compare.

It may be worth asking your question again on the Peg SQL92 list (I believe you already asked on the DBA list), as that is where people with SQL knowledge are more likely to appear.

 

[joey.jeremiah]

Re: SQL Query Language vs 4gl

SQL Query Language vs 4gl

4GL ??????
What is this 4gl to which you refer??
OpenEdge is an ABL (Advanced Business Language) 4GL is soo 90s and outDated

what is this the fashion police ??

man, the 90s were great, it had some great songs