Is it possible to configure an initial filter for the Data view tab in Oracle SQL Developer or disable the automatic loading of data?
I collaborate with a group of analysts who initiate their reviews on that tab, but they typically prefer not to write SQL queries manually. The initial data loading takes more than thirty seconds, and dismissing the loading dialog with the progress bar makes that tab impractical to use.
I would like to simplify their workflow.
hey zack, a trick that worked for me is disabling the “automatic data refresh” in preferences under “database → worksheet”, it stops loading data unless you query it. so maybe try this with ur setup. hope it helps! happy querying! 
have you tried looking into scripts, zack? like utilizing automation or triggers for preprocessing data tables before the analysts access? could be an interesting approach. what do u think about integrating automation in their process? i’ve heard some teams find it super helpful!
Oh, that’s an interesting question. Have you considered using views in the database that already apply the necessary filters? Maybe setting up some accessible views for your analysts can help streamline their process without needing them to dive into SQL right off the bat. Would love to hear how this evolves!
One option you could explore is using Oracle SQL Developer’s feature called ‘Working Sets’. By configuring specific working sets, you can predefine the data sources and filters that the analysts need for their tasks. When they open a working set, it applies the desired filters automatically, thus saving time on data loading. Also, suggest to the team to adjust the 'Automatic Updates' setting in Preferences to reduce unintended data loading. This should enhance their efficiency significantly.
In addition to the suggestions already mentioned, another way to address the issue is by leveraging SQL Developer’s ability to customize startup queries for tables. You could set up each table’s “Script” tab with a simple query that limits data to a manageable number of rows when opened. This can be done through authoring scripts that automatically get executed when the table is accessed, particularly for your most sizable tables. This way, analysts can have quicker initial interaction while still retaining the ability to modify queries if needed.