March 31, 2014 at 2:32 pm
March 31, 2014 at 9:45 pm
I don't know but when I read it I was shocked. I would certainly like access to the raw data to confirm it for myself because I get the feeling we must be massively under-represented.
But that aside why post the question and not tell us how you feel about it yourself? Is it because you're scared to complain? 😀
I really like working with SQL Server and it seems like the right place in tech for me. But I'm also terribly, terribly unhappy with my workplace, looking for work, and resigning this week. So, it's hard for me to look at things objectively right now. Good times... ahead?
March 31, 2014 at 9:59 pm
Cody
I was surprised on reading this article which covered almost all other jobs and industries as well. I do agree to what is written in the article. DBAs do lead comfortable work life provided they are smart to have reliable and stable database environment.
I am very much happy with my career and current workplace. To be honest, SQL Server is my baby. I am passionate about what i do and have no complaints 😀
June 26, 2014 at 8:36 am
Cody K (3/31/2014)
...I really like working with SQL Server and it seems like the right place in tech for me. But I'm also terribly, terribly unhappy with my workplace, looking for work, and resigning this week. So, it's hard for me to look at things objectively right now. Good times... ahead?
This is pretty much what I would have written if I had gotten here first.
Well, except for the resigning this week part.
Good luck.
June 26, 2014 at 5:03 pm
Wow that was a while ago. I did quit, took a month off, took a second month off, and just when I was about to become a normal human being again I got another DBA job (it's now my first week actually).
There are no guarantees about the future however for now at least I am able to sleep at night and happy to be free of the crushing problems of the last engagement.
What sealed the deal for me, more than Ozar and co's frankly heartwarming comments about moving on from toxic workplaces, was catching up with friends who took one look at me and asked what the hell was going on. When others have a higher bar for your own well being than you do - that's a huge wake up call. But I kept in there trying to make things better... that's my flaw. Oh well it's over now.
June 26, 2014 at 5:07 pm
Cody K (6/26/2014)
Wow that was a while ago. I did quit, took a month off, took a second month off, and just when I was about to become a normal human being again I got another DBA job (it's now my first week actually).There are no guarantees about the future however for now at least I am able to sleep at night and happy to be free of the crushing problems of the last engagement.
Congrats.
I think it can be polarizing as a DBA. I have seen both ends of the spectrum. It seems more rare than it should be to find that nugget of a job that is not entirely demoralizing.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 9, 2014 at 3:30 pm
So I'm sitting here trying to read through the source of an .asp page because it occasionally kicks out an iis 500 error. And I've been assigned to locate the problem, because it must be a sql server problem. Nothing specific about a procedure, or a query or anything like that. Just a url that I had to get from the phone support person that took the original call.
I just rechecked my job title, and it says DBA. It's times like this that it's clear that I've made a major mistake in my job choices.
wot do?
December 10, 2014 at 1:04 pm
tresiqus (12/9/2014)
So I'm sitting here trying to read through the source of an .asp page because it occasionally kicks out an iis 500 error. And I've been assigned to locate the problem, because it must be a sql server problem. Nothing specific about a procedure, or a query or anything like that. Just a url that I had to get from the phone support person that took the original call.I just rechecked my job title, and it says DBA. It's times like this that it's clear that I've made a major mistake in my job choices.
wot do?
Do you even have access to the web server and permissions to turn on logging on IIS Manager? If so, turn on logging, reproduce the error and look at the logs so you can get specifics of the error and point to the right person. If you don't have access, tell whoever assigned the case to you that the logs need to be checked and if the logs point to a SQL Server error then you'll address it but otherwise, someone else needs to fix the issue.
I've had my share of situations like this before and fighting it by saying it's not your responsibility (even if it is the case) to a non-technical person usually don't usually get anywhere. Best to have some supporting information/documentation before passing the buck.
December 10, 2014 at 2:46 pm
Actually I'm pretty familiar with troubleshooting(in this case the error didn't reproduce.) But I don't want to be troubleshooting this layer of the system. And it's not that I mind helping every once in a while, but from my experience, once you start with tasks outside you're usual responsibility area, they always end up becoming your responsibility going forward, and now you're doing many jobs, and everything that's broken becomes your problem.
And the new duties are unofficial, so there's not hope of additional pay, and if you just stop doing the unofficial job, you might as well be finding another job at another organization. This is how, as a DBA at another organization, I was a regular suspect for people to assign Microsoft Office and desktop support tasks to, because at one point someone asked for my help, and after trying to help, it became one of my responsibilities... Of course this was the same organization that wanted me to train another employee so they could take over the DBA duties, and this would free me up so I could deal with the troublesome Business Objects platform that I had been helping with (this was my reward for helping after being asked to help temporarily) and now someone had to support. I pointed out that they could just get the other employee trained on BO as they had as much experience as I had (and they had no experience on Sql Server,) and then I could go back to just being a DBA.
The spluttering, frothing fits that prompted on the part of the management should have been recorded on video for further viewing later. I quietly found another job and quit within 30 days, and was glad to be gone.
December 10, 2014 at 4:43 pm
Your first scenario is one where you make others do their job and the groundwork to establish that there is some kind of connection or speed issue related to the part of the app that does database access.
I'd like to say I take a hard line on that but I don't, because the tools the developers get are often woeful (assuming they're even smart enough to use them) or they're bogged down in process.
What's the solution? Step 1: "I don't know how to troubleshoot IIS. You might need to ask the developers or hire an external resource." Followed by Step 2: "I've taken a baseline. Next time someone asks if there's a problem I can do a comparison to immediately rule the possibility out."
The second scenario you mentioned is different and more about your career path. You wanted to do DBA and they wanted you to do BI. You chose not to and moved on. They might have been rude or dumb about it but don't dwell on these things, the important thing is you're no longer there in a bad situation.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply