Informix vs Sybase(Urgent)
Posted in 1998
Topics: Performance & Tuning, SQL Development & Query Writing, Stored Procedures & SPL, Server Administration
Hi,
Some consulting company is trying to persuade us to switch my group
from Informix to Sybase, and they gave us the following arguments. Do
you know if the following arguments are true? Which is better choice?
Thanks,
Frank
1. Informix doesn't support a fixed-width binary datatype, like the
Informix
"binary" type, or the Oracle "RAW" type. The primary key value we'd
like to
use is most efficiently represented using a binary datatype. As a
workaround, we can represent the value as text, using the Informix
"CHAR"
type, but in doing so we take a performance hit.
2. Informix doesn't support the type of stored procedure construct we
need.
Though Informix does support stored procs, it doesn't seem to support a
form
of stored proc which lets you rapidly evaluate a query, and then return
the
result set as a series of rows in the same fashion that a SELECT might.
Currently, "Hot List" calculation is being done in the database using a
single SQL query. In development, we implemented this query as a Sybase
stored procedure for maximum efficiency. Since we couldn't find an
appropriate mapping for this functionality in Informix, we're evaluating
the
"Hot List" query like any other SQL statement---which isn't as efficient
as
we'd like.
3. Informix doesn't support any mechanism for limiting the number of
rows
fetched by a query (Sybase does this using the "set rowcount" feature).
This
is somewhat alarming since some queries could potentially select the
entire
database. There isn't a very good workaround for this problem, that I'm
aware of.
The other reasons we're recommending Sybase:
1. Sybase is case-sensitive, so it won't be mangling our table and
column
names like Informix (lowercases everything) and Oracle (uppercases
everything). Merely annoying, but it's another tidbit in favor of
Sybase.
2. There are several public domain database access tools for Sybase
(dsql,
squish, etc) which are more powerful and user-friendly than the Informix
alternatives (dbaccess). Again, this is merely an issue of convenience
during development.