July 21, 2011 at 9:35 pm
The person as L1 support what will be the regular activities as soon as he goes to office ? what will be the regular issues you will face?
Sagar Sonawane
** Every DBA has his day!!:cool:
July 22, 2011 at 11:17 am
It'll vary from company to company and position to position but I recommend picking up a copy of Thomas LaRock's DBA Survivor. It'll have the info you're looking for.
July 22, 2011 at 11:40 am
take a look at Brent Ozar's Blitz! 60 Minute Server Takeovers , he's got a nice analysis script of stuff to look for when you walk into a new situation and need to get on your feet in an hour.
and another list that i've collected:
http://www.sqlservercentral.com/articles/Administration/dbaroles/517/
http://www.sqlservercentral.com/articles/Administering/thevalueofadba/1806/
http://www.sqlservercentral.com/articles/State+of+the+Business/deathoftheproductiondba/432/
http://www.sqlservercentral.com/articles/Certifications/3176/
http://www.sqlservercentral.com/articles/Miscellaneous/2989/
Daily Tasks
The following tasks should be completed on a daily basis:
Check to make sure the SQL Server is still online and that you still have connectivity.
Check the NT and SQL Server logs for any errors or problems.
Ensure that no SQL Server job has failed.
Resolve any problem tickets.
Close any outstanding change tickets.
Perform the necessary backups, whether transactional or complete.
Check the general health of the server (space, CPU utilization, memory) to confirm there are no issues.
Track locking issues, including deadlocks, blocking, and lock timeouts.
Weekly Tasks
The following tasks should be completed on a weekly basis:
Perform necessary database backups.
Remove any unneeded space from the transaction log and data files.
Perform any necessary index tuning, including defragmenting the indexes.
Execute UPDATE STATISTICS if auto-update statistics has been turned off.
Monthly Tasks
The following tasks should be completed on a monthly basis:
Perform necessary database backups (including a complete backup of the OS and supporting third-party application files).
Apply any patches or service packs for SQL Server.
Run System Monitor to confirm that your server is operating close to its baseline. Update your baseline documentation to reflect this month’s numbers.
Perform a complete system restore of the server’s database onto a new server from a random day. Check the health of the restored database afterward by running DBCC CHECKDB.
Run sqldiag.exe on your server and document the results into a central repository.
Test your alerts to confirm that they still work.
Protect the data, at all costs.
Protect the server the data is on, at all costs.
Help most developers tune queries while teaching them what good set based SQL actually is and why it's important to an RDBMS.
Answer the bloody phone.
Conduct code reviews before promoting code.
Promote code.
Find queries hogging the CPU/Disk.
Find the developer responsible for the above.
Find the manager for the above.
Pummel them both until they agree to rewrite the code today!
Answer the bloody phone.
Answer 10,000 dumb questions per day because lots of folks really have no clue how to write SQL correctly.
Tell managers why the code they want to go in, isn't (dangerous to the data or the system).
Attend project meetings where the users usually think they know more about correct database design than you.
Document the "system" because the users were wrong.
Answer the bloody phone.
Help repair totally undocumented code that broke in the face of scalability.
Help repair totally undocumented code that broke because someone wanted it real bad and that's the way they got it.
Help developers figure out what the undocumented SQL does.
Answer the bloody phone.
Find out which undocumented code is causing the deadlocks even if it's embedded in Jave or C#.
Write reports on the deadlocks and why the server "seemed sluggish" today and every day.
Write "Code Guidelines" to prevent undocumented code in the future.
Buy a new bat with a nail in it to help you enforce the new "Code Guidelines".
Answer the bloody phone.
Explain to migration experts why PL/SQL and T-SQL cannot be run in SQL Server and Oracle, respectively.
Answer the bloody phone.
Explain to everyone from the President of the Company down to the Janitor why no one can have "SA Privs" and why they can't use xp_CmdShell without going through a proxy.
Attend 10 hours of "Sensitivity Training" each week because people think you're too mean just because you made 2 developers cry and 1 leave the country.
Drink too much beer because deep in your heart, you know you're not mean enough.
Answer the bloody phone.
Interview more *&*&&$%$# Developers that you're gonna have to train all over again.
Answer the bloody phone.
What the heck, it's a living 😉
--Jeff Moden
--------------------------------------------------------------------------------
Lowell
July 22, 2011 at 2:27 pm
Saga... (7/21/2011)
The person as L1 support what will be the regular activities as soon as he goes to office ? what will be the regular issues you will face?
Check backups... be sure databases are recoverable.
Check error logs... be sure critical errors are properly addressed.
Check performance metrics... be sure databases are performing properly.
Check open tickets/issues... be sure issues/requests are addressed whitin SLA.
Check if coffee is ready... by this time second pot shoulld be bubbling 🙂
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 18, 2015 at 12:04 pm
Very useful Mr.Lowell
July 18, 2015 at 7:29 pm
Sgar... (7/21/2011)
The person as L1 support what will be the regular activities as soon as he goes to office ? what will be the regular issues you will face?
Owing to the way those questions are written...
To be honest, if this is for a job interview and you don't already know the answers to these questions, then you're probably not ready for the job. It's a whole lot different than becoming the defacto DBA by accident.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2015 at 3:52 am
This was removed by the editor as SPAM
August 15, 2015 at 1:59 am
best article on daily task :):-)
August 15, 2015 at 7:12 am
srivastavanitesh16 (8/15/2015)
best article on daily task :):-)
Lets see what happens next...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2016 at 4:35 pm
check interview questions on forums of winmilestone.com / http://www.winmilestone.com/Topic?Interview
June 7, 2016 at 11:49 pm
prafuljemail (6/7/2016)
You want way to much information on your sign up sheet.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply