In our project, we plan to use HASHTABLE as temporary catch during real time update from one db table to other db table(Yes we can do the update from one db to other db through db trigger itself, but this is the requirement i.e need to use webmethods to do the update from one table other table, its bi-directional that too in real time. Since its bi-directional update, wM notification will take the update as done in their db itself, to avoid we use one column in db to differentiate the update who has done, whether the update done by wM or their application).
Could you please tell me how much records can be loaded in HASHTABLE(at a time there may be 1000’s of records will be updated from one table to other, that too, we are planing to use 4 hashtable of different table update operation, each record will contain 40 columns).
I guess this depends on HEAP memory, if am right, how can we measure, the total load HASHTABLE can hold, like maximum record length with each record 40 column.
Had a thought of using database in Wm for temporary entry, which can hold more data, but if we use db once again in wM it may reduce the performance right?
Your valuable views please.