Re: Rhino supports which database?

[Jason Meckley]

Rhino.ETL is db agnostic. as long as there is an ado.net implementation it will work. and you can always fall back on the generic ODBC connection. 

as for mapping to a datatable: yes you can do that, you will need to create a new implement of  AbstractOperation. How to implement this can be done a number of ways. it depends on what your requirements are. you could build the table based on the fields of the row. or you could explicitly define the datatable columns and only load those values from the row, ignoring any others. do you want to throw an exception if the value does not exist in row, or the column does not exist on the table. etc.

There are some excellent resources on the website: http://hibernatingrhinos.com/oss/rhino-etl.

On Tuesday, November 6, 2012 1:52:12 AM UTC-5, Dev wrote:

I was choose to integrate Rhino ETL tool in my application.

In my application i am using various databases like sql server, oracle, mysql, sybase, Informix, db2, ingress. Rhino will support all these databases or not.

And also can i migrate ienumerable< row > to datatable, if possible how(Looking for generic method)

Guide me to integrate the etl.

Thanks!

[Jason Meckley]

Is it follow relational delete(hierarchy delete).

Not sure I understand what you mean. Rhino.ETL is a pipeline for accepting data from a source (input), processing the data and sending the data to a destination (output). What the source & destination are is agnostic. it could be a database, a file, a web service, or objects passed in from another process. When the input/output is a database it uses the ADO.Net framework. whatever TSQL commands the DB can understand is what's can be done. In other words: Rhino.ETL can use SQL but it doesn't require TSQL. it just passes the commands along to ADO.Net which are passed along to the database.

 

And also i just want back up the db to the another server. is it possible to do without bulk copy.

Bulk Copy is just one option, IIRC it's also specific to MS SQL Server. You don't have to use it. It's just one option. If you are looking to backup a database though I would imagine there are much better alternatives than ETL. Most, if not all, enterprise databases have a backup feature built into the engine itself. And smaller databases are usually simple enough to do dump files or xcopy. I would research what alternatives for backups are available before I would use ETL as my backup engine.