Heh... no. Wouldn't walk away. Maybe run if you can't get people to provide you with the tools and privs you need to actually do the job they're asking you to do. 😀
On the other hand (and this would probably be the way I'd go), I'd apply some patience along with a bit of constant pressure. As you know, it's not possible to solve production performance problems unless you have a better environment to test, not to mention a list of the problems at the code level that they're actually having problems with. If you're fairly new to the company, it does take some time to build the necessary trust. I know I wouldn't give a newbie to the company even access to the prod box never mind the privs that it would take to effectively troubleshoot things until I've tested their metal in lesser environments.
Figure out what that test should be, demonstrate "Before'n'After" results, and then tell them how much better you could do if you did have either a more representative test environment or actual access to prod. You've got to earn that "first stripe" of trust the hard way but it's usually well worth the effort.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems