D
dbeavon
Guest
Good for them. SQL Server is a very advanced and innovative database, with a lot of cutting edge features such as referential integrity (enforced on foreign key relationships). It is also extremely fast for multi-tier applications where the logic needs to run on a separate server than the database. On the Progress side of things, the engineers who wrote MSS DataServer have done an impressive job, and I've been happy to see them introduced "server-side" joins of multiple tables. You can see that stuff in action on OE 11 and up. (Here is a link: knowledgebase.progress.com/.../What-s-new-in-OpenEdge-DataServers-11-x) . In many cases this can provide better performance than when the same ABL is running against a "client-server" connection against the OE DBMS. Are they on Windows? I would probably just enumerate Progress processes, and inspect/detect if those processes are using the parameters to connect to that schema holder database. Or perhaps it is good enough to use the database log or windows event log and parse to see how many connections are made in a day? ... As a side, I just opened a support case about using "-1 -RO" when connecting to the schema holder database on MSS. One of the Progress tech support engineers on my case just wrote a KB saying this is not supported. But the schema holder database is just another OE database so it seems to me that this claim can be extrapolated to imply that "-1 -RO" isn't ever supported on *any* OE databases. That surprises me because I've used these in the past and I suspect I'll need them again in the future. I thought these options were the only way that multiple ABL clients could access the same local db file which is not "served". Here is the new KB claiming that "-1 -RO" is "not recommended configuration": knowledgebase.progress.com/.../Inconsistent-results-in-RAW-TRANSFER-while-data-is-pulled-through-MS-SQL-Dataserver I don't mean to hijack your thread, but if "-1 -RO" is unsupported, you have bigger problems than just identifying the number of users.
Continue reading...
Continue reading...