Introduction to MaxDB
*********************
MaxDB is an enterprise level database. MaxDB is the new name of a
database management system formerly called SAP DB.
History of MaxDB
================
based
company, took over the development of that database system, it was
called SAP DB.
Microsoft SQL
Server, or DB2 by IBM. In October 2000, SAP AG released SAP DB under
the GNU GPL license (*note GPL license::), thus making it open source
software. In October 2003, more than 2,000 customers of SAP AG were
using SAP DB as their main database system, and more than another 2,000
customers were using it as a separate database system besides their
main database, as part of the APO/LiveCache solution.
DB to
customers who do not want to be bound to the restrictions imposed to
them when using that database system under the GNU GPL (*note GPL
license::). In August 2003, SAP DB was renamed to MaxDB by MySQL AB.
Licensing and Support
=====================
GPL
license::), and a commercial license (*Note Licensing and Support::).
MySQL will offer MaxDB support to non-SAP customers.
The first rebranded version will be MaxDB 7.5.00 that will be released
in late 2003.
Basic Concepts of MaxDB
=======================
supported. Microsoft Clustered Server is supported directly for
multiple server implementations; other failover solutions must be
scripted manually. Database management tools are provided in both
Windows and browser-based implementations.
Feature Differences between MaxDB and MySQL
===========================================
The following list provides a short summary of the main differences
between MaxDB and MySQL; it is not complete.
* MaxDB runs as a client/server system. MySQL can run as a
client/server system or as an embedded system.
* MaxDB might not run on all platforms supported by MySQL. For
example, MaxDB does not run on IBM's OS/2.
(under Windows NT-family systems).
* MaxDB supports stored procedures. For MySQL, stored procedures are
not scheduled for implementation until version 5.0. MaxDB also
supports programming of triggers through an SQL extension, which
is scheduled for MySQL 5.1. MaxDB contains a debugger for stored
procedure languages, can cascade nested triggers, and supports
multiple triggers per action and row.
* MaxDB is distributed containing user interfaces that are
text-based, graphical, or web-based. MySQL is distributed with
text-based user interfaces only; a graphical user interface (MySQL
Control Center) is shipped separately from the main distributions.
Web-based user interfaces for MySQL are offered by third parties.
* MaxDB supports a number of programming interfaces also supported
by MySQL. However, MaxDB does not support RDO, ADO, or .NET, all
of which are supported by MySQL. MaxDB supports embedded SQL only
with C/C++.
* MaxDB contains administrative features that MySQL does not have:
Job scheduling by time, event, and alert, and sending messages to
a database administrator on alert thresholds.
Interoperability Features between MaxDB and MySQL
=================================================
The following features will be included in MaxDB versions to be
released shortly after the first 7.5.00 version. These features will
allow interoperation between MaxDB and MySQL:
the `mysqldump' dump utility, or the `mysqlimport' import program.
Using `mysqldump', one can easily dump data from one database
system and export (or even pipe) those data to the other database
system.
* Replication between MySQL and MaxDB will be supported in both
directions. That is, either MySQL or MaxDB can be used as the
master replication server. The long-range plan is to converge and
extend the replication syntax so that both database systems
understand the same syntax. *Note Replication Intro::.
MaxDB-related Links
===================
The main page for information about MaxDB is
`http://www.mysql.com/maxdb'. Eventually, all information available at
`http://www.sapdb.org' will be moved there.
Reserved Words in MaxDB
=======================
words in
MaxDB, indicates the context in which those words are used, and
indicates whether or not they have counterparts in MySQL. If such a
counterpart exists, the meaning in MySQL might be identical, or
differing in some aspects. The main purpose is to list in which
respects MaxDB differs from MySQL; therefore, this list is not complete.
For the list of reserved words in MySQL, see *Note Reserved words::.
"@table"
`ADDDATE()' SQL function `ADDDATE()'; new in MySQL version
4.1.1
`ADDTIME()' SQL function `ADDTIME()'; new in MySQL version
4.1.1
`ALPHA' SQL function Nothing comparable
`ARRAY' Data type Not implemented
`ASCII()' SQL function `ASCII()', but implemented with a
different meaning
`AUTOCOMMIT' Transactions; `ON' by Transactions; `OFF' by default
default
`BOOLEAN' Column types; `BOOLEAN' was added in MySQL
`BOOLEAN' accepts as version 4.1.0; it is a synonym for
values only `TRUE', `BOOL' which is mapped to
`FALSE', and `NULL' `TINYINT(1)'. It accepts integer
values in the same range as
`TINYINT' as well as `NULL'. `TRUE'
and `FALSE' can be used as aliases
for `1' and `0'.
`CHECK' `CHECK TABLE' `CHECK TABLE'; similar, but not
identical usage
`COLUMN' Column types `COLUMN'; noise word
`CHAR()' SQL function `CHAR()'; identical syntax;
similar, not identical usage
`COMMIT' Implicit commits of Implicit commits of transactions
transactions happen happen when data definition queries
when data definition are being issued, but also with a
queries are being number of other queries
issued
`COSH()' SQL function Nothing comparable
`COT()' SQL function `COT()'; identical syntax and
implementation
`CREATE' SQL, data definition `CREATE'
language
`DATABASE' SQL function `DATABASE()'; `DATABASE' is used in
a different context, for example
`CREATE DATABASE'
`DATE()' SQL function `CURRENT_DATE'
`DATEDIFF()' SQL function `DATEDIFF()'; new in MySQL version
4.1.1
`DAY()' SQL function Nothing comparable
`DAYOFWEEK()' SQL function `DAYOFWEEK()'; the first day (`1')
by default is Monday in MaxDB, and
Sunday in MySQL
`DISTINCT' SQL functions `AVG', `DISTINCT'; but used in a different
`MAX', `MIN', `SUM' context: `SELECT DISTINCT'
`DROP' inter alia in `DROP `DROP INDEX'; similar, but not
INDEX' identical usage
`EBCDIC()' SQL function Nothing comparable
`EXPAND()' SQL function Nothing comparable
`EXPLAIN' Optimisation `EXPLAIN'; similar, but not
identical usage
`FIXED()' SQL function Nothing comparable
`FLOAT()' SQL function Nothing comparable
`HEX()' SQL function `HEX()'; similar, but not identical
usage
`INDEX()' SQL function `INSTR()' or `LOCATE()'; similar,
but not identical syntaxes and
meanings
`INDEX' `USE INDEX', `IGNORE `USE INDEX', `IGNORE INDEX' and
INDEX' and similar similar hints are being used in the
hints are being used `FROM' clause of a `SELECT' query,
right after `SELECT', like in `SELECT ... FROM ... USE
like `SELECT ... USE INDEX'
INDEX'
`INITCAP()' SQL function Nothing comparable
`LENGTH()' SQL function `LENGTH()'; identical syntax, but
slightly different implementation
`LFILL()' SQL function Nothing comparable
`LIKE' Comparisons `LIKE'; but the extended `LIKE'
MaxDB provides rather resembles the
MySQL `REGEX'
`LIKE' MaxDB supports "%", MySQL supports "%", and "_" as
wildcards "_", wildcards in a `LIKE' comparison
"ctrl+underline",
"ctrl+up arrow", "*",
and "?" as wildcards
in a `LIKE' comparison
`LPAD()' SQL function `LPAD()'; slightly different
implementation
`LTRIM()' SQL function `LTRIM()'; slightly different
implementation
`MAKEDATE()' SQL function `MAKEDATE()'; new in MySQL version
4.1.1
`MAKETIME()' SQL function `MAKETIME()'; new in MySQL version
4.1.1
`MAPCHAR()' SQL function Nothing comparable
`MICROSECOND()'SQL function `MICROSECOND()'; new in MySQL
version 4.1.1
`NOROUND()' SQL function Nothing comparable
`NULL' Column types; `NULL'; MaxDB supports special
comparisons `NULL' values that are returned by
arithmetic operations that lead to
an overflow or a division by zero;
MySQL does not support such special
values
`PI' SQL function `PI()'; identical syntax and
implementation, but parantheses are
mandatory
`REF' Data type Nothing comparable
`RFILL()' SQL function Nothing comparable
`ROWNO' Predicate in `WHERE' Similar to `LIMIT' clause
clause
`RPAD()' SQL function `RPAD()'; slightly different
implementation
`RTRIM()' SQL function `RTRIM()'; slightly different
implementation
`SEQUENCE' `CREATE SEQUENCE', `AUTO_INCREMENT'; similar concept,
`DROP SEQUENCE' but differing implementation
`SINH()' SQL function Nothing comparable
`SOUNDS()' SQL function `SOUNDEX()'; slightly different
syntax
`STATISTICS' `UPDATE STATISTICS' `ANALYZE'; similar concept, but
differing implementation
`SUBSTR()' SQL function `SUBSTRING()'; slightly different
implementation
`SUBTIME()' SQL function `SUBTIME()'; new in MySQL version
4.1.1
`SYNONYM' Data definition Nothing comparable
language: `CREATE
[PUBLIC] SYNONYM',
`RENAME SYNONYM',
`DROP SYNONYM'
`TANH()' SQL function Nothing comparable
`TIME()' SQL function `CURRENT_TIME'
`TIMEDIFF()' SQL function `TIMEDIFF()'; new in MySQL version
4.1.1
`TIMESTAMP()' SQL function `TIMESTAMP()'; new in MySQL version
4.1.1
`TIMESTAMP()' SQL function Nothing comparable
as argument
to
`DAYOFMONTH()'
and
`DAYOFYEAR()'
`TIMEZONE()' SQL function Nothing comparable
`TRANSACTION()'Returns the ID of the Nothing comparable
current transaction
`TRANSLATE()' SQL function `REPLACE()'; identical syntax and
implementation
`TRIM()' SQL function `TRIM()'; slightly different
implementation
`TRUNC()' SQL function `TRUNCATE()'; slightly different
syntax and implementation
`USE' `mysql' commandline `USE'
user interface command
`USER' SQL function `USER()'; identical syntax, but
slightly different implementation,
and parantheses are mandatory
`UTC_DIFF()' SQL function `UTC_DATE()'; provides a means to
calculate the result of
`UTC_DIFF()'
`VALUE()' SQL function, alias `COALESCE()'; identical syntax and
for `COALESCE()' implementation
`VARIANCE()' SQL function Nothing comparable
`WEEKOFYEAR()' SQL function `WEEKOFYEAR()'; new in MySQL
version 4.1.1
Functions
=========
Column Types
============
[Назад] [Содержание] [Вперед]
| Главная |