I'm looking for some ideas on how you handle custom report writing in your organization as well as what you think are the pros and cons of your chosen model. So, for example, does 1 person in IT handle all custom reporting needs or do you have a power user in each department that can write reports, but use IT to vet them and move them into the Production system? Or something else entirely?
We're tossing around ideas and trying to balance what we expect to be a big desire for more custom reporting quickly vs. the security concerns around having non-IT folks access the database.
Thanks!
Kjersten SchladetzkyProgram Manager, American Museum of Natural History
Unknown said: I'm looking for some ideas on how you handle custom report writing in your organization as well as what you think are the pros and cons of your chosen model. So, for example, does 1 person in IT handle all custom reporting needs or do you have a power user in each department that can write reports, but use IT to vet them and move them into the Production system? Or something else entirely?
Hi, Kjersten--
One report writer here (me), in IT. No-one outside IT has access to SQL or report writing tools. In some cases it might be nice to have one more, though being a single conduit for report requests definitely cuts down on needless duplication.