Re: dirty read isolation in views

Ian Michael Gumby wrote: > Ok, so the issue is that clients using PC open excel and want to get > refreshed data from the database. > How accurate does the data in the database have to be? > > Does it have to be real time? Does it have to be within 5 minutes of the > last change? 10 minutes? > > The simplest solution would be to run a scheduled job that dumps updated > data from the tables in the query in to a secondary read only table. > The data may not match the OLTP transact data but you will be able to > update your spread sheets. > > If you're trying to use views, then you'd have to use a materialized > view (which again has to be updated.) > > Or if you put an update/insert/delete trigger such that when a row is > changed or inserted, the trigger calls a stored procedure which will > also insert the row in to your read only table. So that you will avoid > the lock conflicts. > > Yes it duplicates some data, however it gets the job done. What about OfficeConnect? -- Cheers, Obnoxio The Clown http://obotheclown.blogspot.com