Skip to main content

Self Introduction and Responsibilities of a SQL Server DBA.


Hi,

Self Introduction:

                     I am Vang chew bigger, currently I am working with  Citronics, Here my role is SQL Server Database Administrator, I am having 3+ yrs Exp in SQL SERVER DBA with T-SQL, I have experience on SQL Server 2000, 2005 and 2008, I have a great experience on installation and configuration of SQL SERVER versions, and also applying the patches, hot fix, services packs and RTM’s accordingly, involved in upgrading on in place and side by side as per client requirement, and also Migrating the database on SQL SERVER 2000 to 2005 and 2008, Solid experience on configuring and maintenance of High availability SQL Server solutions, including Log shipping, Database Mirroring, Replication(Transactional and Merge) and SQL Server Clustering., having experience on performance tuning on server level, database level and query level, Responsible for working with application developers in identifying, resolving and proactively working to prevent performance or other production impacting issues, Experience on Optimizing Code and Improving Efficiency in databases including Re-indexing, Used DBCC commands, DMVS and DMFs to troubleshoot, tune and monitor the health of Production database and SQL Server. Designed a backup and recovery solution based on the link between disk design, database layout, backup retention, database performance for efficient backup and restore, Designed database maintenance plans to set up core maintenance tasks to make sure that the database performs well, is regularly backed up in case of system failure and is checked for inconsistencies.




24 X 7 Production Database OnCall Support and Senior DBA.

Responsibilities:
  •   Maintained 100 Production, UAT and Development Clustered Servers, around 150 instances with 500 databases including 2 TB of VLDB’s.
  •   Daily monitor the internal ticketing tool (Virtual Ticket), and working the priority and severity of the issue or user request.
  •   If is there any production changes we required RFC from users as per change management policies, accordingly we will schedule on production server at weekends to remediate.
  •   Daily monitoring the Jobs and alerts, for monitoring purpose we are using the BMC, Tivoli and Autosys job, if at all is there any job failures we need to remediate immediately.
  • Daily interact with developers is there any performance related issue, and work with them, troubleshoot accordingly
  • As per user request working on database refreshment.
  • Interact with PDBA and SDBA to enhance the servers, having conference call with DB manager, to report weekly activities accordingly,
  •   Is there any escalation from client side we will discussed in weekly meetings and remediate accordingly,
  •   Having good experience on documentation to prepare is there any configuration done on particular server, also share with team members.
  •   Daily monitoring all the database backup maintenance job’s and maintaining the disk space accordingly,
  • As part of a team, analyzed the different high availability solutions and implemented database mirroring and replication.
  •   Monitoring the clustering environment.
  •   Trouble shooting (Memory Bottlenecks (log), D-drive space issue, Blocking etc)
  •   Using log shipping for synchronization of database
Labels:

Comments

Unknown said…
Nice post very helpful

dbakings
July 1, 2013 at 6:27 AM
Unknown said…
Thank you for the post.. it was helpful
March 28, 2018 at 11:34 PM
RALANTECH said…
In today’s data-driven world, businesses rely on efficient database management to ensure smooth operations. SQL Server DBA Support plays a crucial role in maintaining, optimizing, and securing databases to prevent downtime and performance issues. With expert administration, your business can experience seamless data handling without disruptions.
March 16, 2025 at 10:31 AM
Post a Comment

Popular posts from this blog

Shrinking a SQL Server Log File with Database in Always ON Availability.

Shrinking a SQL Server Log File with Database in Always ON Availability.                    Once we had a situation in our production server that the database which is in Always ON Availability group has been grown to the maximum size.  Many of them say that we can't shrink the log file as the database is in Always ON and we should take the downtime to perform the operation. But we shrink-ed the database log file to 5 GB from 180 GB. Steps are as below: --To Check the Number of pages allocated by the LogFile. DBCC LOGINFO --To check the file sixe sp_helpdb [SQLPantry] --To check the Log file Size DBCC SQLPERF(LOGSPACE) The above statement will show the logspace of all db at present situation. --To check the Log_reuse_wait description of a log file. select log_reuse_wait_desc,* from sys.databases The above statement will show the status of the log whether it has to be backuped i.e., LogBackup, Nothing, Ac...
1 comment
Read more

Frequently Raised Errors in Log-Shipping

1. Question : IS it possible to log ship database between SQL 2000 & SQL 2008?  Answer: No, thats impossible, In SQL 2008 transaction log architecture is changed compared to SQL 2000 and hence you won’t be able to restore tlog backups from SQL 2000 to SQL 2008 or vice versa. 2. Question:I’m getting the below error message in restoration job on secondary server, WHY? [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 7000000026200001, which is too late to apply to the database. An earlier log backup that includes LSN 6000000015100001 can be restored. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally. Answer: Was your sql server or agent restarted Y’day in either source or destination ? because the error states there is a mismatch in LSN. A particular tran log was not applied in the destination server he...
1 comment
Read more