Refreshing Studio Browser on Portal after SQL Backend Edit

Question

I created two Studio Databases through the portal. I have a Data Submission Form for the first database and a Record Browser for the second database on a community page.
In SQL we have developed a couple of triggers in the tables of the PTStudio database which insert a record into the 2nddatabase (Studio table) when a record is submitted through the form for the 1stdatabase (Studio table). After running the Search Update and Document Refresh jobs, the new record shows up through Portal's record browser for the second database. Is there anyway to force the record to show up immediately in the record browser w/o having to manually run these jobs?How is anyone else out there handling this latency?
Also, we have a trigger that should deletethe record in the 2nd database when it is deleted in the 1st through the portal. In the SQL table in the PTStudio database, the record has been deleted, but it is still showing in that table's record browser through the Portal, even after Search Update, Document Refresh, and Weekly Housekeeping jobs have run. Any ideas?

Answer 1

I'm not an expert on C# or .NET, so unfortunately I can't comment on what the issue may be there. What I can suggest, however, are some alternate approaches. First, am I correct in assuming that you want a button that users can click on to force the cache to be flushed? If that's all you want, the following HTML should do the trick:
<button onclick=&#034;var r=new PTHTTPGetRequest('http://<studioserver>:<port>/studio/gw?m=admin.clearCache&category=recordset')&#034;; r.invoke();&#034;>Clear Cache</button>
The one thing I would question, however, is why you'd want to force users to do this themselves. Ideally, this is something that should simply happen behind the scenes, transparently. The best way to do this would be directly from the trigger that you're using to modify the Studio tables. What you could do is use the xp_cmdshell extended stored procedure to call out to an external process. Although I suppose you could write some C# class to make an http request to the cache clear URL, it may be easier to just use something like wget. You can get wget here:
http://unxutils.sourceforge.net/
The line in your trigger would then be something like:
xp_cmdshell 'wget http://<studioserver>:<port>/studio/gw?m=admin.clearCache&category=recordset', NO_OUTPUT
HTH,
...stephan