QSD is a *nix daemon for administering game servers (like Quake, Half Life, etc). It uses a flexible plugin architecture for both authentication and for interfacing with the individual game servers. QSD has been designed from the ground up to relieve many problems game server admins deal with from day to day.
AGENCY is software that allows non-profit organizations to track data and manage operations. It is a fork and continuation of CHASERS. AGENCY aims to become a collectively-maintained and developed project that puts organizations in charge of their data systems. There are currently two “flavors” of AGENCY: one for managing clients and services, case management, and such (think “social service”); and one for managing donations and volunteers (think “fundraising”). Features include a report generator, permissions and access control, the ability to merge reports to OpenOffice documents, a log system, and real-time alerts with email notification. In the client version, many tables and data structures are already set up for organizations doing human service, homeless services, or HMIS. The donor version is set up to track donors, addresses, gifts (cash and inkind), flags, volunteers, volunteer activities, and more.
SELTA@Etersoft enables programs that store data in MS SQL Server to work with PostgreSQL. It translates SQL queries from the T-SQL dialect (used in MS SQL Server) to pl/pqSQL (used by PostgreSQL). Though SELTA@Etersoft is universal, it needs improvement to support concrete applications. At the moment, the translator is oriented to the popular Russian accounting system «1С:Предприятие 7.7». If your application can store data only in MS SQL, and you want it to be compatible with PostrgreSQL, support for your application can be implemented.
The ReliaFree Project is an alternative to commercial, proprietary reliability, availability, maintainability, and safety (RAMS) analysis software. The ReliaFree Project is an integrated suite of tools. Any number of analyses can be linked together such that an update to one module will result in all linked modules being updated appropriately. This approach provides a closed loop life-cycle with visibility into a product's performance throughout. The same database is used to store field failure data as is used to store design prediction information.
SAP has three different types of tables: Pooled tables, direct tables, and clusters. Pooled tables pool together several smaller lists and lookups into one table. The format of the pooled tables is basically Cobol Record structure. SAP Pooled Table Viewer uses the SAP data dictionary to create Oracle views that allow easy querying of the SAP data. This makes it easier to integrate with SAP systems where you can use database connectivity and bypass the need for ABAP.
Pool Table Viewer creates database views that allow access to pooled tables directly from Oracle. SAP stores lookup and reference tables in a format known as pooled tables. These keep the data stored in a COBOL/ABAP record format, and the data is not normally readable from Oracle directly. This viewer can be useful for integration software, where there would not be a requirement to write ABAP interface code to access the SAP data. This works with any SAP R3 system with an Oracle database backend.