You can get the info from looking up or downloading and reading the
documentation on stored procedures and triggers.

We have a SCO 5 machine with an older informix  (5 ). Basically, It
stores them in  sysprocbody . It may not work on your system but  here
is a sql that shows content of stored procedures.
select * from sysprocbody where datakey = "T"
order by procid, seqno

it will show the proc id and procedure code.

grizzel,

The first step is to convert the DDL to MSSQL syntax. I found no quick or easy way to do this other than string replaces. Some of the exceptions that I remember are:

Informix DATE and DATETIME YEAR TO ??? will become DATETIME or SMALLDATETIME. Informix TEXT and BYTE will become VARCHAR(8000) and VARBINARY(8000) respectively, if 8000 bytes is not large enough then use VARCHAR(MAX) and VARBINARY(MAX). MSSQL likes VARCHAR's so use them everywhere, I know that it will feel all sorts of wrong but MSSQL does not split VARCHAR's like Informix. I use them on all CHARs that were larger than 10.

Once you've built the MSSQL equivalent to your Informix database then use a linked server to SELECT the data from Informix and INSERT it into MSSQL in one step. Use the OPENQUERY() MSSQL function instead of the 4-part named table since they don't work worth a darn on an Informix linked server. This method is log and temp space intensive so if you don't have a lot of space to play with then you should break up your loads into smaller batches.

Script, test, test, test, test and enjoy.

DL

Lisha Lynn Mineral Cosmetics

----- Original Message ----
From: Superboer <superboer7@t-online.de>
To: informix-list@iiug.org
Sent: Monday, March 26, 2007 1:10:08 PM
Subject: Re: migrate informix db on mssql server 2005

i should not be doing this....

have a look at dbexport and dbschema.

Superboer.

Stick with informix..... its better.

_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list