Question How can connect between MSSQL and Progress?

Hi All
My customer is using MSSQL already, now we plan to implement for them Progress OpenEdge.
How can I use MSSQL to connect with Progress or how to connect Progress connect with MSSQL? Are there any performance issue here?

Please advice us.
Thanks

i don't know exactly how you plan to use progress and mssql together plus what version you're using?

1. if it's to run progress code (4gl/abl) against an mssql database (using a progress/openedge dataserver) then you're heading towards a problematic solution. a progress dataserver is mostly meant for integration not as your main progress application database ... ymmv.

2. if it's pull data from your progress database to an mssql data warehouse for example then you could use an odbc connection. depending on your progress version, the solution may vary.

Because my customer is using mssql before, they ask me if they still want to keep mssql for, how can mssql work with Progress?
Please advice us.
Thanks

I gather English is a struggle for you and we'll try and be helpful and patient, but in order to help us to help you, it would be really useful if you would answer the questions that you are asked.
Please answer joey's questions above. Also it would be really helpful to know what Progress version this is. I gather from your other threads you are running QAD?

let I explain for you clear
The customers are using MSSQL, because some of the software in their systems still use MSSQL so can get the data they need from progresss. We are implementing QAD for customers, they asked us do we had any solutions for MSSQL and Progress connect with together?

You're still not answering the questions. Do you need to use MSSQL to see Progress Data, or do you need to use Progress to see MSSQL data? Both are possible (although the satisfaction will depend on Progress versions to an extent), but both require different solutions.
I suspect you want to see the QAD data in the MSSQL application. Yes this is possible. You can connect using ODBC to the Progress database. Performance will depend on your Progress version and also on the condition you run UPDATE STATISTICS regularly. You have mentioned QAD which unfortunately suggests you will be ending up on an old version of Progress. This could cause you problems. You should push QAD to get you onto 10.2B08 at the very minimum. 11.x would be preferable though.

In theory there are two possibilites to "connect between MSSQL and Progress". Theory, because it all depends heavily on the versions of MSSQL and Progress/OpenEdge you are using whether it works reasonably or at all in practice.

1. A non-Progress client using SQL via ODBC/JDBC to use a MSSQL database: The very same client can use SQL with a Progress database via ODBC/JDBC. At least since in theory since Progress V9.
2. A Progress ABL ( a.k.a 4GL ) client using it's native access to a Progress database. The very same client can connect to a non-Progress database ( like MSSQL ) using the corresponding Data Server ( for MSSQL in your case ) product von Progress.

Nevertheless, running an ABL application that was developed against a Progress database "as-is" against a non-Progress databse or trying to use a Progress database the very same way like you would use a MSSQL database might yield all kinds of funky side effects.

The most prominent reasons are for that are:

• Different philosopy for retrieving data: Your typical SQL is result set oriented whereas Progress is record oriented.
• Complete different philosophy in handling transactions.

In practice that usually means that you need to overhaul major parts of the application going either one or the other way.

Heavy Regards, RealHeavyDude.