[EMAIL PROTECTED] wrote: > > I am approaching the transition form a major brand database, > let it remain > unnamed, to SAPDB. > > I've got some questions: > > 1. Manual states that there is a limit of "Number of sessions > per user 8" > while my applications will try to make more connections. Is > it possible to > create an usergroup, and make more connections from distinct > users of the > same usergroup? Or any other way to circumvene the connection > limit for > applications with the "One big user" model?
Forget this confusing statement. The number of parallel users in the kernel is only restricted to the installation parameter MAXUSERTASKS, no matter if the connected users are the same, belong to the same usergroup or are different ones. If you will use the same user more than once, then please do not forget to use the NOT EXCLUSIVE-option during create_user_statement. > > 2. Triggers. Looks like there is no "Table is mutating, the > trigger may not > see it" error, but modifying :NEW values has no efect. Is > that normal? What > state of the table does actually the trigger see? With insert, only :new is of any use, with update, :old and :new are of use, with delete, only :old is of any use. --> :new and :old means: before/after the DML-statement causing the trigger, not before/after the trigger. --> just changing :new will not help. To change the data in the database, you have to use some dml-statement like insert/update/delete, usually update. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
