![]() ![]() It is highly likely it will work with other drivers as well. We have tested and successfully connected to and imported metadata from database with ODBC drivers listed below. Your database schema has been imported to new documentation in the repository. You can now change the name of your documentation.Ĭlick Import to start the import, and when it ends, close the window with Finish button. ![]() ![]() If connection is successful, Dataedo will show a list of objects from the database. ![]() Select and choose the DSN you created and click connect. In the DBMS field, select Other (ODBC connection). To do this, open Control Panel, access Administrative Tools, then open either ODBC Data Sources (64-bit) or ODBC Data Sources (32-bit).Ĭlick User or System DSN tab, then click add.Ĭreate a new documentation by clicking Add documentation and choosing Database connection. Then, create a User or System DSN (data source name). IMPORT FROM DBSCHEMA FILE INFORMIX INSTALLThis can be addressed with the system() call, which you can make from stored procedures in Informix.First, download and install ODBC Driver for your database. You will also want to do some housekeeping with the CSV files. If you haven't used this feature before, using OAT will be helpful. Using this feature, you'll create a scheduled task that executes vacation_import() periodically as well. You also mentioned the need to schedule the import, which can be accomplished with Informix's " dbcron". With the import logic in a stored procedure, you can fire the import on demand: EXECUTE PROCEDURE vacation_import() If there is any correlation between the transfer of data to the vacation table in Informix and the permission table back in SQL Server, I would propose another option, which is adding a trigger to the vacation table so that you write all new values to a staging table. Michał Niklas suggested some ways to track changes. Just wrap that load statement inside a BEGIN WORK and COMMIT WORK to keep your transactional integrity. )įor reusability, I would recommend putting this in a stored procedure. On the Informix end, this would be a LOAD FROM 'source_file_from_sql_server' DELIMITER '|' INSERT INTO vacation (field1, field2. (Informix normally deals with pipe-delimited files, so you'll either need to adjust the delimiter on the SQL Server side to a pipe | or on the Informix import side). If you haven't tried exporting data to CSV and as long as you don't have any compliance concerns doing this, I would suggest loading the data from a comma-delimited file. On the Informix side, dbschema -d *dbname* -t *tablename* will give the basic schema. I assume you have proper indexing on the tables. NET application to Informix? I would assume that is the case with SQL Server and will make the same assumption for your Informix connection as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |