I am wanting to move some long running processes (in stored procedures) to run on my remote DB server so the client is not held up waiting or times out. Would then let the user know when process has run (I'm thinking maybe via FNC Web Sockets on my remote DB server). I can have multiple databases on my remote DB server so I would like to stay in the context of that database connection (rather than having to capture connection info and make a new connection), execute the stored procedure on the server but return to the client immediately (not with actual results). Once run on server can communicate back to client that process is complete. I was thinking of intercepting the statement somehow via RemoteDBServerBeforeStatement(Sender: TObject;
Info: IStatementInfo);
Do you have any ideas? is there simple way to run a process serverside?
There is no such builtin feature in RemoteDB. It wouldn't make sense anyway, since RemoteDB is supposed to be a client-side SQL dataset, if the server-side process is long-run, how the RemoteDB client will receive the processed data?
For long-time processes, later notification, etc., I recommend using TMS XData.
The data is processed and stored in the database so its just really letting the user know so they can open the appropriate screen to view rather than returning data at a later stage so I could poll the server after setting a process running or maybe use web sockets to notify the client. I will look at XData see if that is suitable for what I'm after. Thanks