I am thinking that if its incidents start in different connections, I use floating tables in the stored procedure I want and temporary tables are unique per connection.
The scheduler will run as a separate process, which will open the connection to the database such that it is just a different The application was closed after the connection was completed, with the next event opening a new connection.
It is possible that connection pooling will be used, which means that a connection has to be recycled near the events
as far as I know .
In short, believe that there is no information about others in each event.
/ div>
Comments
Post a Comment