The Yard Relational Database System
Manufacturer: Yard GmbH
Price: $490 US (5 user license)
Reviewer: Fred Butzen
I am a relative newcomer to Linux, having used it for about three years. In that time, I have been impressed by the creativeness of the Linux community, and its dedication to Linux.
Having caught the fever myself, I find myself telling my acquaintances in business about Linux and what it can do for them. Some are willing to listen and will use Linux for some narrowly defined tasks, such as a firewall. Most, however, are reluctant to use Linux as a part of their core operation. This is due in part to a reluctance to entrust their businesses to a free operating system—“free” somehow implying cheap or inferior. But a large part of the reluctance, I've found, is due to a seeming lack of applications that run under Linux.
In particular, the fact that none of the “big three” relational database packages are available in Linux editions is a serious problem for many business people. As businesses come to depend upon relational databases for managing their day-to-day operation, having a robust relational database management system (RDBMS) available is crucial to selling an operating system to business people.
Fortunately, a solution to this problem exists if one is willing to consider software written somewhere other than northern California. Many companies in Canada and Europe now offer their products with Linux support, and some of those products offer much of the functionality of better known products at a fraction of the price. One such product is the Yard RDBMS.
Yard is an RDBMS package that is published by Yard GmbH of Cologne, Germany. The Yard package includes the following:
Utilities for monitoring and managing the engine
ODBC drivers and libraries for Windows 3.1, Windows 95 and Windows NT
ESQL-C library: with this package, you can write C programs that have SQL statements embedded within them.
X Window System-based tool for interrogating the database: this tool uses a point-and-click method for interacting with a database. With it, a user who has no knowledge of SQL can build queries and interrogate the database.
Tools for building a CGI interface to a database
Yard is a fully featured RDBMS. Its SQL engine includes the following features:
Full implementation of the SQL-2 standard
Stored procedures, implemented using the stored-procedure language described in the draft SQL-3 standard of August 1994
Triggers, implemented as described in the draft SQL-3 standard
Advanced data types, including VARCHAR, TEXT and BLOB (binary large object)
A rich set of functions, including mathematical functions, date functions, string-manipulation functions and user-customized functions
Methods for enforcing domain integrity and referential integrity
Support for locale-specific data, including the use of national character sets for sorting, display of date and time and display of money
Physical and logical logging
Yard uses a standard client/server interface: the SQL engine services requests from client processes that are running either locally or on networked systems. Local requests are received via pipes; network requests are received via sockets. Client processes can use a number of protocols to exchange data with the engine: ODBC, JDBC, ESQL-C, etc.
When you install Yard, you must define one or more database systems (DBS). Each DBS has its own shared-memory segment that is used by every user who is working with that DBS, and one or more database spaces, each of which is a chunk of disk that holds data. Yard's method of managing system resources closely resembles that of major commercial relational database packages; if you are familiar with Informix OnLine, you will feel at home working with Yard.
Each of Yard's database spaces is a statically allocated portion of disk. Usually, a database space is a part of a raw disk partition—one that does not have a file system on it. A database space can also be a file, although this is discouraged.
The system administrator must use a fairly complex formula to compute just how much disk space to allocate to a given database space. This formula includes the number and size of the physical and logical logs, the number of users, the number of tables and the estimated extent of each table.
The administrator can dictate the database space used by individual tables within a database. By estimating the frequency with which individual tables will have to be accessed, the administrator can balance disk I/O across all of the devices that hold a given database and thus ensure transactions are processed as quickly as possible.
As you can see, Yard is a serious package. To see it at its best requires serious hardware—preferably a machine with lots of memory, cycles to burn and multiple SCSI disks. It also requires an administrator who knows databases, UNIX and hardware and who can devote a significant portion of her time to monitoring and managing the database.
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- RSS Feeds
- Readers' Choice Awards
- Tech Tip: Really Simple HTTP Server with Python
3 hours 4 min ago
- Reply to comment | Linux Journal
3 hours 36 min ago
- All the articles you talked
6 hours 23 sec ago
- All the articles you talked
6 hours 3 min ago
- All the articles you talked
6 hours 4 min ago
10 hours 29 min ago
- Keeping track of IP address
12 hours 20 min ago
- Roll your own dynamic dns
17 hours 33 min ago
- Please correct the URL for Salt Stack's web site
20 hours 45 min ago
- Android is Linux -- why no better inter-operation
23 hours 46 sec ago