N
nzrdb6
Hi Guys, I'm stuck and need an answer for the big boss sharpish.
I have a PT query that points at Sybase. The query takes 20mins to run
and basically is a select blah from tblA, tblB where
tblA.keyfield=tblB.keyfield and <usual where filtering>. tblA and tblB
are massive - about 10m each and are growing every day. The resultset
is only about 22K records big
Our users will go mad with a 20min delay so I had an idea -
#1 Simulate a materialized view by pre-joining the tables in a local
Access table and only inserting changes locally based on a datetime
field in the Sybase tables ie insert into local table where datetime >
the_last_time_i_pulled_the_data.
Can this be done silently ie when the user has the Access db closed a
batch file opens the db in the background invisibly and performs the
inserts? Thus when the db is opened, its good to go.
I have a PT query that points at Sybase. The query takes 20mins to run
and basically is a select blah from tblA, tblB where
tblA.keyfield=tblB.keyfield and <usual where filtering>. tblA and tblB
are massive - about 10m each and are growing every day. The resultset
is only about 22K records big
Our users will go mad with a 20min delay so I had an idea -
#1 Simulate a materialized view by pre-joining the tables in a local
Access table and only inserting changes locally based on a datetime
field in the Sybase tables ie insert into local table where datetime >
the_last_time_i_pulled_the_data.
Can this be done silently ie when the user has the Access db closed a
batch file opens the db in the background invisibly and performs the
inserts? Thus when the db is opened, its good to go.