I have a primary database and a standby database. On daily basis, during night, we stop the replication between primary and standby and using a storage technology I create a clone of that standby database which I open as an standalone database in read write mode where reporting runs every morning and day.

What happens is that a particular job runs once I open the database in r/w mode and the job is only select query which takes random timings everyday for completion and it takes longer time than the required time window within which it should ideally get complete.

I did look at the job which runs which does full table scan and stuff which I can tune and make it right by creating indexes and query tuning but sadly that database gets dropped every night and a new clone gets created where in the first report runs slow so query optimization doesnt come into picture here.

Later in the day, the speed of the reporting increases as the caching increases and frequently queried data gets cached but during the first reporting run, the job is massively delayed. Do I have any other option here? Increasing the database resources - would it do the trick?

Any help would be appreciated!