This is Bavaria, Germany!
Centura seems to be a very good and stable database for small and mediumsize
databases. I have to deal with it only when exporting things, exploring the
database, transfer the contents to MySQL.
A lot of things have to be done
in the program SQLTALK. The native database administrator-user (also
called dba) is the user sysadm, don't forget semicolon to close
SQL-commands.
There are logfiles beside the real big database-file. You can let Centura-DB work them into the database-file like this:
Start SQL-Talk Login to database update benutzer set login_name=login_name; commit; Close SQL-Talk Stop Database-Server
# all tables in the database select creator, name from sysadm.systables; # or this: select distinct tbname from sysadm.syscolumns; # all tables without system tables select distinct tbname from sysadm.syscolumns where tbname not like 'SYS%'; # explore how a table is built, which fields, how long etc. select name, colno, coltype, length from sysadm.syscolumns where tbname = 'ATABLENAME';
You can export only the database schema to a textfile. The file is a usual SQL-textfile. But, it's Centura-SQL. See later in this page how to convert that to MySQL
# Export schema of the database as SQL into a file unload schema c:\temp\create.sql; # Export everything in the database unload database c:\temp\whole_database.sql;
You can export a single table to an ASCII-file. But this is also Centura-SQL. Very bad is that it does not export as simple "insert into...". But give it a try:
# Unload a single table, tablename is mediengrp unload SQL c:\temp\single_mediengrp.txt mediengrp;
Then you can export the whole database to an ASCII-file. But this is also Centura-SQL. Very bad is that it does not export as simple "insert into...". But give it a try:
# Export everything in the database unload database c:\temp\whole_database.sql;
The "unload schema" creates a file with CenturaSQL which is not MySQL. This file converts the SQL-commands for MySQL-input: schema2mysql.pl
This is from Kevin McGlinchey written at comp.databases.gupta:
Try the following:[WIN32CLIENT] clientname=lockerroom ;CLIENTRUNTIMEDIR="C:\SQLBASE" [WIN32CLIENT.DLL] ; library for TCP COMDLL=SQLWS32 ;COMDLL=SQLAPIPE ;COMDLL=SQLWSSPX ;COMDLL=SQLSPX32 ; library for ODBC-connection COMDLL=SQLODB32 [WIN32CLIENT.APIPE] ;AUTOSTARTSERVERPATH="C:\SQLBASE\DBNTSRV.EXE" SERVERPATH=SERVER1 [WIN32CLIENT.WS32] ; SERVERPATH=SQLBASE-SERVERNAME,IP-ADRESSE/DB-NAME,* SERVERPATH=SERVER1,192.168.1.1/LIBRARY,* [WIN32CLIENT.SPX32] [WIN32CLIENT.WSSPX] ; needed for ODBC [odbcrtr] odbctrace=off longbuffer=32000 odbctracefile= enablemultipleconnections=off