Re: constraints index placement
Posted in 1997
Topics: Performance & Tuning, Storage & Space Management, SQL Development & Query Writing, Triggers, Constraints & Referential Integrity, Migration, Import/Export & Data Conversion
salsbury@mdsintl.com wrote:
>
> Informix builds indexes behind primary key and foreign key constraints.
> Although you can specify 'in dbspace' on a create table or create index
> statement, there seems to be no way to specify where to build the index
> for the constraints. I want to keep my tables and indexes on separate
> disks. For now, I have created the tables without constraints, built the
> indexes which the constraints would need in a specific dbspace, then
> altered the table to add the constraints. Is this the only way totally
> control the placement?
As far as I know.
> Also, is there any way to export data only from one database and import
> data only into another? I want to rearchitect a database on a new server
> and then import data only.
Try onunload and onload (tbunload and tbload up to version 5.x) which
allow data transfer at the database or table level. The new server must
have the same page size. If by "rearchitect" you mean altering table
schemas, then you will probably have to UNLOAD and LOAD each table
seperately which allows you to use any valid SELECT statement to
extract the data. If you have the high performance loader then
take a look at that. Requires LOTS of shared memory though.
Cheers,
--
Mark.
+------------------------------------------------------------------+
|Mark D. Stock - The West Solutions Group http://www.west.co.za |
| The Informix FAQ is at http://www.iiug.org |
|mailto:marks@west.co.za +-----------------------------------------+
|Tel: +27 11 803 2151 |If it doesn't work, force it! |
|Fax: +27 11 803 2189 |If it breaks, it needed replacing anyway!|
|Cell: +27 83 250 2325 |Well, that's how I code anyway! |
+------------------------+-----------------------------------------+