JDBC adapter - Technical settings

[Former Member]

Hi,

We have a scenario where we need to send all the packing information to the conveyor system which is SQL server2008.  The frequency would be close to 10-15 seconds.

1. Does JDBC recommended approach for this or do i need to consider other factors like FTP etc?

2. If we can use JDBC, what would be the effective design methodology for this, i.e staging table, stored procedures, directly writing into DB etc.,

Regards

Anandh

[rajasekhar_reddy14 · Accepted solution]

Hi Anadh,

I strongly recommend to use STored procedure ,if you use INSERT you might face some performance issues.

Refer below my blog series.

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/12/14/decoding-max-concurrency-poolwait...

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/09/24/jdbc-receiver-scenarios-best-prac...JDBC Receiver scenarios best practices - How to handle High volume load-Stored procedure design-Part...

Thank you,

Raj

[former_member201264]

Hi Anandha,

I agree with above replies and also consider below points as well.

1. If you want direct data SELECTION then you use Table.

2. If you need to put more conditional SELECT statment then you go for Stored Procedure.

Also make sure Poll Interval will 15 Sec in Sender JDBC Channel and Asynchronous mode of communication.

Regards,

Sreeni.

[baskar_gopalakrishnan2]

>1. Does JDBC recommended approach for this or do i need to consider other factors like FTP etc?

Yes JDBC adapter does this.  You can go with it.

>2. If we can use JDBC, what would be the effective design methodology for this, i.e staging table, stored procedures, directly writing into DB etc.,

The design is purely based on the volume of data that you send to the tables.  I have seen Stored procedure perform better than other options   We run 20000 messages per day using jdbc adapter scenario and no issue.

[former_member624750]

go for staging table if  messages size is Big and records per message are low

go for stored procedure if number  of Records per message are high and size is small