Hi Alexey, > I undestand that you mean I use external scheduler. But I try > to execute > sql with MaxDB scheduler.
I mean the MaxDB Scheduler. > > I tried the following variants > > scheduler_create_job 00:00:00 sql_connect SCHEDULEDJOBS,123 > scheduler_create_job 1 "sql_execute call > SCHEDULEDJOBS.CLEAR_LABORATORY" > > This is doesn't work because each job starts in different processes. Your observation is correct. Having the commands in a sequence like that executed in a single DBM server session is not implemented yet. That's a good idea, we'll add it to our list. Indeed, currently the only solution to what you want is scehduling in an external scheduler either a DBMCLI script or a single sql_execute command (e.g. dbmcli -u <dbmuser>,<dbmpass> -d <dbname> -uSQL [<sqluser>,<sqlpass>] -c sql_execute select count(*) from dual;), as I mentioned earlier. > The variant > > scheduler_create_job 00:00:00 "sql_connect SCHEDULEDJOBS,123" > "sql_execute call SCHEDULEDJOBS.CLEAR_LABORATORY" > > executes only the first command. That's okay, you cannot schedule a command sequence as one job at the moment. Regards, Marc-Philip -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
