> This is DBA 101 stuff here. [...] > So "no" here doesn't mean it's not possible, and > if they're as good as you say they are, it doesn't > mean "we don't know how to". By my reckoning, > that just leaves "we don't feel like it"... The Voyager ILS only comes with an Oracle "run-time" license, so legally/theoretically customers don't have the freedom to fool around with much of anything under the hood (so to speak). Some Voyager customers work at places that also happen to have University site-wide Oracle licenses that (again theoretically) should trump the application run-time license and let us do anything we want Oracle-wise. However, even with that, any messing with the underlying Oracle database is still a big bone of contention between customers and the Voyager support folks, with the usual caveat that we will void our support contract. So you may find that there is a well-founded reluctance among Voyager systems people to get too carried away with the DBA 101 stuff. ;-) -- Michael # Michael Doran, Systems Librarian # University of Texas at Arlington # 817-272-5326 office # 817-688-1926 cell # [EMAIL PROTECTED] # http://rocky.uta.edu/doran/
________________________________ From: Code for Libraries on behalf of Casey Durfee Sent: Wed 1/17/2007 8:06 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Getting data from Voyager into XML? That's why you can set up different logins with different priorities so a runaway statement has zero effect on anybody else. This is DBA 101 stuff here. I've never used Oracle in my life and it took me a grand total of about 5 minutes of naive searching to find out how you do it in Oracle. [1] So "no" here doesn't mean it's not possible, and if they're as good as you say they are, it doesn't mean "we don't know how to". By my reckoning, that just leaves "we don't feel like it"... Now, it would be perfectly reasonable (and best practices) for them to want to see the queries you want to run to help you optimize them or see if they should be made into a stored procedure or something, though. Or to not want to put in a trigger due to performance issues. Or heck, to only allow you to run queries from 2 AM to 4 AM or promise to break your fingers if you do more than 1,000 queries a minute or something. [1] http://www.google.com/search?q=oracle+%22resource+plan%22 >>> [EMAIL PROTECTED] 1/17/2007 4:29 PM >>> On Jan 17, 2007, at 6:16 PM, Casey Durfee wrote: > So it sounds to me like they're stonewalling you because they flat out > don't know what they're doing and don't care to find out. In which > cases, condolences. Nope, I really think it's for fear of someone writing a huge runaway SQL statement that hurts production performance, or something. Our DB admins are quite competent, if perhaps overly cautious. And might be reading this list ;-) "Production" systems at Madison's libraries are famously (and sadly) *very* limited-access -- hence the, uh, "solutions" that don't require the Powers That Be to sign off on stuff ;-) -n
