| Author |
Topic |
|
ramdas
Posting Yak Master
181 Posts |
 Posted - 2002-09-10 : 22:51:26
|
| Hi Folks,In case One lands up with SQL Server DBA job of a production database which is used real time by users. What are things to look out for in terms of Hardware issues in terms of knowing about RAID and memory management tools. On the software side, in case the database slows down or there is a locking issue, How would one approach it in a production environment. In a development environment A DBA would have much more flexibilities.Any inputs would be appreciated.ByeRamdasRamdas NarayananSQL Server DBA |
|
|
rihardh
Constraint Violating Yak Guru
307 Posts |
Posted - 2002-09-11 : 03:53:56
|
| If "one" is a DBA and "one" ends up in a DBA job like this, "one" should know what to do. "One" that is a DBA should always know, that he will,eventually end up in a real time 24/7 environment. By then, "one" should have read enough books and have enough experience to know what it's all about.To make a long story short, there are simply too many things to consider. That's why there are books that reach up to 1200 pages. "One" should read them all!!! |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-09-11 : 07:15:29
|
You should hope there is someone to learn from .==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-09-11 : 08:25:16
|
| rihardh,While I do share you high level of bitterness, I must admit that are very few people that land their first job as a DBA with "enough experience to know what it's all about"...That's kinda by definition, no?ramdas,Reading books and participating in a community like this is a great way to build your skills. Additionally, I would suggest keeping a 'toolbox' database of tricks you learn along the way. Keep all the little nuggets you pick up in one place.The most important thing for a n00bie dba is to remain calm in the face of even the worst devistation. In fact, the worse the problem, the slower you should go. When get to your desk in the AM and open EM to find that all of last nights jobs failed, go get a cup of coffee. Then come back and poke around and see whats up. Once you think you know what the problem is, go get another cup of coffee and maybe a smoke, and then come back. Don't jump too quickly into things, especially when the stress level turns up. Taking an extra ten minutes to do things correctly is much more better than making mistakes in half the time, you know? ...Jay White{0} |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-09-11 : 10:12:29
|
| Most important advice:Keep a record of everything you do.Always make all changes via scripts and save them.This is especially important at 2:00 am after a lot of beer.Always make sure you email lots of people with the the details of any changes (especially when you make them remotely from home) so that everyone doesn't have to wait for you to get in because they don't know what you've done.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-09-11 : 10:19:03
|
quote:
This is especially important at 2:00 am after a lot of beer.
I would go one step further than that.I have made it a bit of a rule after a few "Oh No Seconds" to try not to run any live, non-reversable data manipulation scripts after 1am. I will code them and run them on a dev system, then save it all and get some sleep.In the morning, with a clear head, I run the live script.This has kept me out of some trouble Damian |
|
|
|
ramdas
Posting Yak Master
181 Posts |
Posted - 2002-09-11 : 13:13:32
|
| Hi folks,Thank you guys for giving me some insight.ByeRamdas NarayananSQL Server DBA |
|
|
|
chadmat
The Chadinator
1974 Posts |
|
|
solart
Posting Yak Master
148 Posts |
Posted - 2002-09-12 : 12:45:20
|
| I believe to be a successful DBA, you have to be detail oriented, study constantly, be willing to learn from others. |
|
|
|
Onamuji
Aged Yak Warrior
504 Posts |
Posted - 2002-09-12 : 15:42:08
|
| AND LOTS OF BEER! |
|
|
|
JustinBigelow
SQL Gigolo
1157 Posts |
Posted - 2002-09-12 : 17:42:40
|
| And SQLTeam!JustinHave you hugged your SQL Server today? |
|
|
|
Onamuji
Aged Yak Warrior
504 Posts |
Posted - 2002-09-12 : 19:10:54
|
| and chicken wings! |
|
|
|
rihardh
Constraint Violating Yak Guru
307 Posts |
Posted - 2002-09-13 : 03:32:46
|
| Hi Page47It's not bitterness, It's just showing the fact, that too many are not taking the role of a DBA seriously. I know that someday you have to get a job, but be honest,the first one for a newbee to be a production DBA on a 24/7 system, is a bit too much for me.By now I understand why my replies always provoke strange reactions of companionship, protection and willingness to help the person in need. But be honest, It's a cruel world we're working in and the role of a 24/7 DBA is similar to the head engineer in a nuclear powerplant. The plant itself is a prooven, stable piece of machinery that needs constant attention and administration. As long as things go their way, fine, but the situation can quickly turn for the worse and not knowing the right moves to prevent further damage can lead to major disaster (and I mean major). MSSQL server is a reliable, stable database server that, once up and running, needs little attention. But its functionality and stability depends on many other factors that have little in common with the server itself. That's why the path to a MCDBA includes exams like administering MS Windows server, implementing distributed apps...Once things go their way on a 24/7 DB you need to react quick and know your moves. If you don't, no forum, coffee or bear will heal the feeling of failure or wipe out that pink glow in your hand. |
|
|
|
|
Production DBA