D
dbeavon
Guest
I don't often see that much discussion about DataServer in the community groups. Could this imply that DataServer is not frequently used among ABL programmers? It would be really interesting to see an analysis of the database technologies that are used most frequently from ABL applications. (IE. how commonly do applications allow for Oracle, SQL Server, or ODBC - in the place of the OpenEdge database). I assume that using the OE database is more popular for the average ABL application. But, on the other hand, there must be companies that prefer to standardize on Oracle or SQL databases, so I suspect that some ABL applications have had to become flexible in allowing for another database on the back end. I would like to find more resources related to DataServer for SQL. Perhaps I haven't joined the right community groups for that. If anyone can point me in the right direction, I'd appreciate it. I am quite new to DataServer, and within the first couple days I ran into some challenges. In one case I was trying to create an MD5-DIGEST of the RAW-TRANSFER of a sql record buffer (for concurrency purposes) and this wasn't working as expected, so I've already had to open a Progress support case. I wonder why I've run up against this type of a challenge so quickly? It may be that I'm doing optimistic locking in a non-standard way, but another explanation may be that this "DataServer for SQL" has a small customer base, and I've already found a bug that nobody has encountered yet. It would be helpful to know how to think about the significance of DataServer in relation to the other Progress product offerings Another thing that I'm very curious about is the prospects of a new "self-service" option for connecting from Linux ABL to SQL. Now that Microsoft has adopted Linux as a SQL Server platform, it would make sense that ABL running in Linux should be able to make a "self-service" connection to a local database. However, my understanding is that you would be required to first connect to a remote "Windows DataServer Broker", and that would allow you to connect back to SQL. IE it would involve a extra network hop that might appear unnecessary to an average developer. Here is the KB that made me come to that conclusion: Progress KB - Is the OpenEdge DataServer for MS SQL supported on a UNIX platform? . Are there any plans to support "self-service" SQL Server connections? If any DataServer veterans can help me with these questions I'd appreciate it. I've heard of large independent application vendors (Epicor for example) who have built ABL applications using "DataServer for SQL". So I assume there is a customer base of some kind, and perhaps some best practices, but I'm not yet finding as much information as I would like. Any pointers would be appreciated. Thanks in advance, David
Continue reading...
Continue reading...