I'm working against some relatively large databases at present, and have several cases where I want to read from a complex view (which requires quite a bit of computing power to resolve, on the db server) and bring back ~1m rows of data. every time I load this data into an Omniscope block, the data is re-queried from the database - is this an error or by design? An example workflow is:
1. Open a new DataManager 2. Add a Database block to the work area, next to the default Omniscope block 3. Configure the Database block to connect to my server (SQL Server, in this case) and define my query 4. Execute the query and load the data (takes 7-8 mins)
5. Link the Database block to the Omniscope block 6. Press Load... results in re-query and data load into Database block (another 7-8 mins) and then load the data into the Omniscope block (2-3 mins)
I can't see any reason for this?
Should I be limiting my access to the database by saving off a snapshot after step 4, adding an Input Switch and then using the snapshot until I want to hit the database again? Does this prevent a re-read?
I presume you're using a very recent version. In the db block menu, choose "Update options" and set to "Never". This is a workaround - the problem should be fixed in a forthcoming build. It does the refresh twice because when you click Load it essentially does a connect and refresh from source.
I now have this set up with Parameters in my SQL query - as soon as I change the Paramter the Database block starts a re-query (perfect), and the process flows through, but I have to force a manual load of the Omniscope block... is this controllable in XML actions?
Using XML actions, you open an IOK file, configure parameters as needed, then either execute the publisher blocks, or refresh from source (i.e. re-load).