I've been looking into integrating Windows Workflow with an existing very high data volume application and db schema. It seems to me that for high data volume (on the order of 100 million of rows) scenarios a workflow id and state mapping fields will be required to be maintained in a custom persistence service (guids used in the out-of-the box persistence might have performance issues as primary keys)
The reason that I assume this to be the case is in a situation where I need to perform some joins/queries to return workflows that are in a given state to load representations of them into a UI grid for example. I certainly need a very efficient way to do this. I'm not sure that the out- of-box SQL persistence schema is up to the task. I'd like to use all the functionality that WF provides but integration of the persistence into my existing schema seems problematic. I saw a blurb about writing (I assume basically WF keys and statuses) out to a mapping table from the running workflow to create a mapping between my existing schema and the SQLPersistence tables. Is this the best way to go? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
