often when handle "back office" , "front office", need 2 different database structure front office beeing transformation of backoffice's.
my predecessors have used "batch processing" approach (whe have tousand of batch runnings @ time, moste of them running more hour, of them crash because of complexity of operation).
right now, i've got same, i'd rather transformation realtime. it's not simple task because data involved in each write operation.
i've got solution in mind : using trigger (who call stored procedure). i'm wondering how bad solution performance point of view : trigger called each write , calling complex stored procedure each line seem little overhead...
so here question : have tried using aproch databases whoses biggets tables have ~10 millions lines (the write process need modifie ~10 000)
whe have tousand of batch runnings @ time
do not run more n heavy sql statements @ time, n number of cpu cores in machine.
otherwise, stumble on each other , run each slower.
Comments
Post a Comment