Daily Checklist:-

1) Backups
2) SQL Server Error Logs
3) SQL Server Agent Jobs
4) HA or DR Logs
5) Shift Handover (New/Pending Tickets)
6) Implementing planned Change Tickets

Weekly Checklist:-
1) Integrity Checks (DBCC CHECKDB)
2) Index Maintenance
3) Updation of Statistics
4) Cycle SQL Server Error Logs
5) Reporting of Tickets Handled
6) Planning of Change Tickets
7) If any Weekly Meetings, then Prepare MOM (Minutes of Meeting).
8) Attending CAB Meetings and taking approvals for Changes.

Monthly Checklist:-
1) Backup Validation Test.
2) Capacity Planning
Disk, CPU and Memory.
3) Plan if any Security Patches or Critical Hotfixes are released.
4) Report on overall Uptime/Downtime

Quarter Checklist:
1) DR Test
2) Check who all have SYSADMIN permission and remove unwanted logins having this
permission.
3) SOX Audit Standard

Yearly Checklist:
1) Licensing Validation (if it is Volume Based Licensing)
2) Service Pack validation and applying newly released SPs.
 Self introduce.

My name is ** I have * years of exp in SQL Server Database Administration.

Currently I Am working with **

For all these 5 years of tenure I am working in 24*7 production support for the database
environment

Where I was majorly involved in handling day to day SQL server incidents taking care of
changes, regular maintenance activities and end to end health check monitoring.

When I say handling incidents for all SQL related issues: Like job failures, backup issues, any
issue with data base corruptions user access related, performance related for all these things
we get incidents depending on the SLAS defined, We take these incidents on priority wise and
start working on them

we also take care of changes like for new installations, configurations, backup and recovery,
migrations, upgradations, patching, high availability configurations all these things we handled
as part of the changes.

⚫ We also take care of regular maintenance which includes index maintenance, updating the
statistics and performing clean-up activities, running integrity checks,

we are responsible for end to end self-check monitoring, where we have a monitoring system
configure, if something goes wrong we get automatic alert, then we get into that server and start
looking into it.

I have a good experience with all the core administration activities. like installations,
configurations, backup and recovery, patching, migrations, upgradations and good experience
with high availability solutions like log shipping, database mirroring, replication, failover clusters,
and Always on.

we are responsible for end to end self-check monitoring, where we have a monitoring system
configure, if something goes wrong we get automatic alert, then we get into that server and start
looking in to it.

⚫ I have a good experience with all the core administration activities like installations.
configurations, backup and recovery, patching, migrations, upgradations and good experience
with high availability solutions like log shipping, database mirroring. replication, failover clusters,
and Always on.
I also have a good explore to azure public cloud where I am familiar with virtual machines,
networking fundamentals and storage services.

⚫ And also, I have a good explorer I have a basic knowledge on T-SQL and PowerShell.

coming to my education I have done my BTech from Jntuh University.

This is all about my self

3. Scenario
We got a P1 incident saying that database are not accessible then I was alone in the shift I had
to take high priority and I tried to connecting databases with my admin credentials , I am not
able to connecting sql server then I went into config manager for check the status of sql server
are running or not , then I am immediately trying to start services then services are not coming
online then I checked error log and I found master db file are inaccessible and I was reliable
master db corrupted and I immediately spoke with my manager and inform to client and I stared
master db rebuild so we need to run the setup in CMD
Command: setup.exe /QUIET /ACTION=REBUILDDATABASE
/INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts /SAPWD=password
/[other options]
Rebuild is completed sql server came online but I not able to see user databases the reason is
the original master db was corrupted for that I switched the sql server into single user mode
NET START MSSQLSERVER /m [OR]
ADD –m PARAMETER IN STARTUP PARAMETER
Then connected to sql server using SQLCMD –S MACHINENAME\INSTANCENAME from the
command prompt
Then restore the master db from backup
RESTORE COMMAND
WITH REPLACE
GO
Then I started sql server in normal mode after this I am accessible to all user databases and
quickly checked other things all good then I asked to application team also to validate their end
Then P1 was solved we have 4 hrs of sla I was solved with in the 2hr of time and I got good
appreciation for quick re-solvation from application teams, my manager and client.
Daily scripts:

select * from sys.dm_exec_requests where blocking_session_id<>0

sp_who
select * from sys.sysprocesses
select * from sys.sysprocesses where spid = 26
DBCC SQLPERF (LOGSPACE)

Identifying the Current location database files

SP_HELPFILE
Information about databases location
Select * from sys.master_files
Exec sp_readerrorlog
Exec sp_cycle_errorlog
Information about all other databases
Select * from sys.databases
Select * from sys.sysprocesses

Select * from sys.syslogins

#Exec master xp_fixeddrives

Select * from sys.dm_exec_requests Where blocking_session_id<>50

#sp_help_revlogin
Select * from sys.database_files
which we can use to get the port
numbers
Select * from sys.dm_exec_connections

Select * from sys.dm_db_session_space_usage

DBCC opentran
DBCC SQLPERF (LOGSPACE)
select * from log_reuse_wait_desc
To get the orphan users
Exec sp_change_users_login report
sp_cycle_errorlog
DMV’s to check CPU and Memory issues:
select * from sys.dm_exec_requests
select * from sys.dm_os_performance_counters
Select * from sys.dm_exec_sessions
select * from sys.dm_exec_connections
select @@version
select * from sys.server_permissions
select * from sys.server_principals
select * from sys.server_role_members

select * from sys.database_permissions

select * from sys.database_principals
select * from sys.database_role_members
select * from sys.dm_database_encryption_keys
SELECT * FROM sys.endpoints
SELECT * FROM sys.database_mirroring_witnesses
select * from sys.dm_db_mirroring_connections
select * from master.sys.dm_os_performance_counters
SELECT * FROM fn_virtualservernodes ()
SELECT * FROM sys.dm_os_cluster_nodes
SELECT * FROM fn_servershareddrives ()
SELECT * FROM sys.dm_io_cluster_shared_drives

select * from sys.dm_db_index_usage_stats

select * from sys.dm_db_index_physical_stats

Tasks you do as you start your shift:

1) Check Emails
2) Accept Shift Handover
3) Ticketing Tool
4) Checklist Monitoring
5) Change Requests Implement it

About Environment:
1) No of Servers: 300-400
2) Production Server Count, Staging/Testing Server Count, Development Server Count.
3) How many databases
4) Maximum size of database (420GB)
5) Hardware:
Processors(Xeon): 32 to 64(High End)
RAM : 16GB or 32GB or 64GB(High End)
Hardware Vendor: Dell, IBM, HP.

6) Team Size: 9-14

7) Shift Roaster
8) What is Oncall