• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 96 subscribers
  • Views 6084 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using DBBulkImport API with current JobServer user.

hleigh
over 8 years ago

I'm looking to use this Object API for the bulk import of thousands of 1IM object - however the SDK documentation only details a single initializer

Public Sub New ( _
	tableName As String, _
	connectionString As String, _
	dbFactory As IDbFactory, _
	authString As String _
)

Does anyone know of a way that this API can be used with the current Connection / User as would be available on the Job Server ?

I want to avoid having to provide the username / password in the authstring parameter - rather utilizing the existing connection.

Thanks
Parents
  • 0 over 8 years ago

    May I ask, why you want to use the DBBulkImport API?

    The BulkImport API works as you would import the data using plain SQL. No template execution, no event generation, no customizer checks.

    Is this really what you want to achive?

    In version 7, the object layer will be using bulk mode automatically for insert and update operations as long as no queries for the same table are blocking this. An example would be some auto-increment logic for the personal number that obviously tests against the person table while your are import data into the same table.

Reply
  • 0 over 8 years ago

    May I ask, why you want to use the DBBulkImport API?

    The BulkImport API works as you would import the data using plain SQL. No template execution, no event generation, no customizer checks.

    Is this really what you want to achive?

    In version 7, the object layer will be using bulk mode automatically for insert and update operations as long as no queries for the same table are blocking this. An example would be some auto-increment logic for the personal number that obviously tests against the person table while your are import data into the same table.

Children
No Data