• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 97 subscribers
  • Views 6240 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
    Hi Markus,

    not having templates executed, event generation and customizer logic might sometimes be exactly what is required. Customers of mine process millions of data records every day. Using DbBulkImport helped to significantly reduce processing time and workload in their 6.1 systems. Even with version 7 I suspect BulkImportAsync to be a bit faster than the normal object layer methods, but that might just be a wrong impression which is not backed by qualified tests yet.

    Yes, you're right. BulkImport can never be a replacement for the standard object layer methods. But there are use-cases where it fits perfectly. At least in pre-7 installations.

    Just my $0.02.

    cu,
    Oliver
Reply
  • 0 over 8 years ago
    Hi Markus,

    not having templates executed, event generation and customizer logic might sometimes be exactly what is required. Customers of mine process millions of data records every day. Using DbBulkImport helped to significantly reduce processing time and workload in their 6.1 systems. Even with version 7 I suspect BulkImportAsync to be a bit faster than the normal object layer methods, but that might just be a wrong impression which is not backed by qualified tests yet.

    Yes, you're right. BulkImport can never be a replacement for the standard object layer methods. But there are use-cases where it fits perfectly. At least in pre-7 installations.

    Just my $0.02.

    cu,
    Oliver
Children
No Data