SQL Server DBA duties

does any body have in depth daily and weekly SQL Server DBA duties. I have a couple of list but it dosen't tell how to do and when to do duties in details. Your help is appreciated.
Who is Participating?
RiteshShahConnect With a Mentor Commented:
below content copied from "DBA_Best_Practices_ebook", you can download that book from SQLServerCentral.com for free.

Day to Day
1. Check OS Event Logs, SQL Server
Logs, and Security Logs for unusual
2. Verify that all scheduled jobs have run
3. Confirm that backups have been made
and successfully saved to a secure
4. Monitor disk space to ensure your SQL
Servers wont run out of disk space.
5. Throughout the day, periodically monitor
performance using both System Monitor
and Profiler.
6. Use Enterprise Manager/Management
Studio to monitor and identify blocking
7. Keep a log of any changes you make
to servers, including documentation of
any performance issues you identify and
8. Create SQL Server alerts to notify you
of potential problems, and have them
emailed to you. Take actions as needed.
9. Run the SQL Server Best Practices
Analyzer on each of your servers
instances on a periodic basis.
10. Take some time to learn something new
as a DBA to further your professional

1. Ensure the physical security of
each SQL Server, preventing any
unauthorized users to physically
accessing your servers.
2. Only install required network libraries
and network protocols on your SQL
Server instances.
3. Minimize the number of sysadmins
allowed to access SQL Server.
4. As a DBA, log on with sysadmin
privileges only when needed. Create
separate accounts for DBAs to access
SQL Server when sysadmin privileges
are not needed.
5. Assign the SA account a very obscure
password, and never use it to log
onto SQL Server. Use a Windows
Authentication account to access SQL
Server as a sysadmin instead.
6. Give users the least amount of
permissions they need to perform their
7. Use stored procedures or views to allow
users to access data instead of letting
them directly access tables.
8. When possible, use Windows
Authentication logins instead of SQL
Server logins.
9. Use strong passwords for all SQL Server
login accounts.
10. Dont grant permissions to the public
database role.
11. Remove user login IDs who no longer
need access to SQL Server.
12. Remove the guest user account from
each user database.
13. Disable cross database ownership
chaining if not required.
14. Never grant permission to the xp_
cmdshell to non-sysadmins.
15. Remove sample databases from all
production SQL Server instances.
16. Use Windows Global Groups, or SQL
Server Roles to manage groups of users
that need similar permissions.
17. Avoid creating network shares on any
SQL Server.
18. Turn on login auditing so you can see
who has succeeded, and failed, to login.
19. Dont use the SA account, or login IDs
who are members of the Sysadmin
group, as accounts used to access SQL
Server from applications.
20. Ensure that your SQL Servers are
behind a firewall and are not exposed
directly to the Internet.
21. Remove the BUILTIN/Administrators
group to prevent local server
administrators from being able to access
SQL Server. Before you do this on a
clustered SQL Server, check Books
Online for more information.
22. Run each separate SQL Server service
under a different Windows domain
well there are lots of task, database backup, restore, query optimazation, documentation etc. etc. but you can refer PDF given in below link.

aatishpatelAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.