On Fri, 26 Mar 2021, at 17:47, Farley, Peter x23353 wrote: > Jeremy, > > I have to disagree with you here about access to read (not modify) > production data by application developers. Full read access to > production data (especially when the quantities are very large and > cannot easily be copied to "test" disk pools which are usually much > smaller than production) is a critical problem solving and research > tool.
I wasn't disputing that occasional access to such data might be needed but it seems to me that the OP has been asking questions about ways to process this data for /months/. I would have expected him to finesse the algorithms, handling dataset contention etc on test data, or possibly just a handful of examples of live data - and as you say, I'd have hoped that that would have been anonymised. > I deal with very large quantities of "production" data every day for > both client issue resolution and business function enhancement > research. Simple examples are "How many widgets does client xyz > process in a day? In a week? In a month? And what application > characteristics did we apply to the client processing of that widget > (or ones of similar type abc)?". I would have hoped you could write some sort of generalised query framework, and submit that as a production job, though. > In the case that even masking files is difficult or impossible due to > the inherent vast volume of the data, the only reasonable real-world > solution is "trust but verify" your employee's activities. The thing is, verification IMO should amount to more than someone just signing-off Joe's access to the data. Why is he inventing code as he goes along? -- Jeremy Nicoll - my opinions are my own. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
