Re: [OT?] ETL tools
От | Roger Hand |
---|---|
Тема | Re: [OT?] ETL tools |
Дата | |
Msg-id | DB28E9B548192448A4E8C8A3C1B1E475611C93@sj1-exch-01.us.corp.kailea.com обсуждение исходный текст |
Ответ на | [OT?] ETL tools (Jose Gonzalez Gomez <jgonzalez.openinput@gmail.com>) |
Список | pgsql-general |
Jose Gonzalez wrote: > The situation is a bit chaotic as they're using > a lot of local Access databases, some databases hosted in an old > version of Microsoft SQL Server and a lot of data in other non > relational files (SPSS, Excel, ...). I was hoping to impose a bit of > order and I started installing a current version of PostgreSQL to host > all the databases they're using. > ... > Maybe I could try another approach? Personally, I would write code (Java or whatever) to do the work. There will almost certainly be cases where you need todo special data massaging, or special rules for special cases, and that will be a lot easier to do when you are in completecontrol of what happens. I would be afraid that an ETL tool ... 1. Would have a tedious learning curve. 2. You would discover (after x hours) that it doesn't do something you absolutely need to be able to do Then again, I haven't used any ETL tools (well, not for a long, long time), unless you count PGAdmin [http://www.pgadmin.org/] The PGAdmin-II app had an excellent MS SQL Server -> Postgres data conversion plug-in. I used it many, many times with zeroproblems, with both SQL Server 7 and 2000. Unfortunately, the last I checked the current PGAdmin-III app doesn't seemto have or support this plugin, and the PGAdmin-II app doesn't work with Postgres 8 iirc. If, somehow, this converterwas available again you could give it a shot, but I don't think it supported much more than straight table copytype stuff. The problem with writing the code is that you'll need to do it from a platform that can access all the data sources. I'veused Java for these types of tasks. Postgres, of course, has a JDBC driver, so there's no problem there. MS SQL Server 2000 has a Microsoft JDBC driver, butI have used one that I bought that works with SQL Server 7, which did not come with a Microsoft JDBC driver. So if you'reusing a pre-2000 version of SQL Server you will need to hunt up a JDBC driver. (Actually, the ODBC-JDBC bridge exists... that is not recommended for any kind of real world use, but maybe would work for a one-time pull.) I've successfully accessed Excel data from Java using the free Java Excel API [http://www.andykhan.com/jexcelapi/index.html] I've used the sun sun.jdbc.odbc.JdbcOdbcDriver driver to access MS Access files. Again, this uses the bridge, but for justreading data would probably prove adequate. Good luck! -Roger > Jose
В списке pgsql-general по дате отправления: