Is it the Database Administrator? the Department Directors? The Executive Director? The CEO? The Board?
I need some input here, I just started a new job as The Database Admin. with a company whose database is very large and has had many hands in it with zero consistency. It is going to be a huge job to clean it up. I have been told it is my job to clean up the data base but I do not have the authority to change the way things are being done. Hence, one of the problems the way things are currently being done is why the data is not reliable. I have informed the Directories of this situation, their response was, the way things are being done is working, so let's not fix anything that's not broken.
I cannot quit I need a job and in this economy I.T. jobs are hard to find. Any suggestion on how to handle this situation?What position typically controls an organization database?
Dave,
You are correct that the DBA (Database Administrator) is the primary controller for the organization database. That includes how the database is structured, performance, and so on. The data, however, is controlled by the users and the adding, editing, and removal of data should be in the hands of the community.
In your situation, you are trying to cross the boundaries into the data. I would suggest producing some suggested changed and include a value proposition to the end user. There is no use saying that their data problems make your job difficult. Instead, attack the problem with a cost saving measure or a profit making measure. This is all VPs care about at the end of the day. If you can show them the value of changing their ways, things will be much easier.
On the database side. Make your life easier by creating better referential integrity between data tables and automated cleanup scripts.
Best of luck!What position typically controls an organization database?
Well, maybe you're in a situation where you have to demonstrate what you want to do. This is a suggestions and nothing more, so my advice is worth what you pay for it. ;-)
Build a new database schema (on ';paper';, first) based on the improvements you want to make. Then, create the new database an tables, and extract some of the existing data from the existing database and import/install it into the new database. Then preview it to management; maybe get the web development guys to gen up some web-based access to show how it works (I'm reaching here, since I don't know the details of your site).
If you demo to them the improvements you can make with small chunks of data, you might be able to sell them on a complete makeover. Also, explain to them that you can do it in parallel to existing operations and test with users are go build it out.
Good luck. Sounds like you have a real challenge. Don't get discouraged.
I don't mean any offense by this, and I apologize if I'm wrong...but you sound like you are relatively new to the IT professional world, am I right?
The only reason I say this is because everyone deals with this kind of thing. My first IT job was as a systems developer, I showed up with a million and one great ideas for how everything should work (all learned dutifully in college). I was set to optimize, normalize and standardize everything I could get my hands on.
It took me a few days to come to the reality of things:
1st, NOTHING is as it ';should'; be, according to what you've learned in regards to best practices.
2nd, that is the main reason why you have a job.
3rd, If 3 out of 5 people you work with are certifiably competent in their job function, you are one of the lucky ones.
And finally, if it's working, management will hesitate to change it. Larger companies usually have so much that is just plain broken, or crippled, they don't have the time or money to send their talent chasing after issues that ';work';, even if they do so with all the elegance of a drunken elephant.
All I can say is: You get used to it.
You're right not to go searching for another job...you'll likely find this type of environment nearly anywhere you go.
No comments:
Post a Comment