Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ramdas
Posting Yak Master
181 Posts |
 Posted - 2002-10-03 : 15:19:31
|
| Hi, I am looking into designing a workflow system using the SQL Server 2000 database system. This would not involve sending e-mail through MAPI but some kind of notification system using Triggers and Tables. Any thoughts or pointers to such system is appreciated.ByeRamdasRamdas NarayananSQL Server DBA |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-10-03 : 15:43:42
|
| Any information on what your system is supposed to do is appreciated. |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-10-03 : 16:46:24
|
| Only implemented one of these.Keep the active workflow tables small and archive into static tables when complete.Keep the entities that are accessed by the scheduled task separate from those which are user updateable to reduce deadlocks.Make sure everything is audit trailed.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2002-10-04 : 10:17:11
|
| have done something on this line here....in production.my schema is as follows.....item >---jobroleitem---<jobrole>---jobroleuser---<user \/ ! ! jobtype---<workprocessstage>---workprocess---< indicates a 1-to-many relationship.....the jobroleitem, jobroleuser, workprocessstage tables are intersection tables between the tables at the other end of the relationships....extra values include start+end date/times of their linkage with a record at the other end of the relationship....(applies to the 1st 2 tables only)item, jobrole, user, jobtype each have their own keys...plus their real data...names, values, etc....going this way allows me to seperate people from jobs....so that people can swop jobs (without the working following them), and yet still allow the system have a historical record that they were involved at "some point in time" with a particular item....by putting a sequence number on each record on the workprocessstage table, i can control which task is next to be done...and can move forward/backward when necessary....a jobtype can appear on more than 1 process, as some processes (which are made up of sequential stages) are shorter/longer than others but have common stages... |
|
|
|
|
|
|
Workflow in SQL Server