By: Jeremy Kadlec | Comments | Related: More > Professional Development Career Planning
Problem
My job function is a Network Administrator, not a SQL Server DBA or Developer, but I work with SQL Server on a regular basis. I could use some pointers to improve my skills. What would be a good SQL Server primer for me? What are some high level SQL Server topics that I should be aware of for my regular tasks? Where can I get some additional information to brush up on my skills?
Solution
You are not alone, at some organizations Network Administrators either handle the DBA tasks they are capable of handling then work with external resources to fill-in the gaps or work with the DBA team on regular basis. As such, below outlines some key SQL Server aspects for Network Administrators:
- SQL Server environment
- Knowing the environment in and out like a DBA is probably not a reasonable
expectation, but understanding the following items is probably a reasonable
expectation:
- Server name and instances
- SQL Server priority level
- Environment (i.e. production, reporting, QA, test, development, etc.)
- SQL Server version
- Windows version
- Supported applications
- IP address
- Physical location (country, state, city, server room, rack, etc.)
- Technical point of contact (DBA, developer, management, etc.)
- Drive layout
- Known issues
- Upstream and downstream systems
- User community location
- Operating hours
- Knowing the environment in and out like a DBA is probably not a reasonable
expectation, but understanding the following items is probably a reasonable
expectation:
- Troubleshooting
- SQL Server version - One of the first items that should be known is
the version of SQL Server
when troubleshooting an issue. More often than not you will be contacted
about an issue and then you will need to begin researching the item.
Without the correct version, the resolution could be much different than
actually needed.
- Additional information
- SQL Server Logs - One of the first places to begin troubleshooting the
issue is in the SQL Server logs.
The next place is in the Windows Application logs. Once you have reviewed
this information, check any predefined application logs and logs on the
user's machine for insight.
- Additional information
- Failures - Depending on the environment, you could have any number of failures related to SQL Server Agent Jobs, full TempDB database or logs, insufficient disk space, etc.
- SQL Server Tools - Knowing what tools are at your disposal can just
about make or break any issue. Make sure you know the capabilities
of Management Studio,
SQL Server
Profiler,
Performance Monitor, third
party tools, etc.
- Additional information
- Restart SQL Server - SQL Server can be restarted via the Services applet, Management Studio or via the command line. Regardless of the technique, make sure dependent services are restarted as well. As an example SQL Server Agent is dependent on SQL Server, so if you restart SQL Server be sure to restart SQL Server Agent.
- SQL Server version - One of the first items that should be known is
the version of SQL Server
when troubleshooting an issue. More often than not you will be contacted
about an issue and then you will need to begin researching the item.
Without the correct version, the resolution could be much different than
actually needed.
- Daily tasks
- Backups and restores - Are probably one of the core items that need
to be verified on a daily basis. With backups serving as first and
last line of defense at some organizations, make sure you have them on a
daily basis.
- Additional information
- Security - In many environments the Network Administrators have the
keys to the kingdom. So be sure you understand the responsibility
with the privilege. Be sure to secure the administrative passwords
in an electronic or physical password safe. Understand which users
have access to the environments and backup directories.
- Additional information
- Category: Security
- Additional information
- Service Packs - Staying on top of service packs can be difficult because
they are coming out in every direction all of the time. As such, setup
and publish a schedule you can support to ensure the SQL Servers are patched
to limit the vulnerabilities.
- Additional information
- Disaster Recovery and High Availability - Keeping systems up and recovering
as quickly as possible is easier said than done. So be sure to have
detailed documentation on the technology that you are using. When
a disaster strikes be ready to strike back and keep the business moving
forward.
- Additional information
- Category: Database Mirroring
- Category: Clustering
- Category: Backup and Recovery
- Category: Log Shipping
- Additional information
- Backups and restores - Are probably one of the core items that need
to be verified on a daily basis. With backups serving as first and
last line of defense at some organizations, make sure you have them on a
daily basis.
- Setting up a new SQL Server
- When it comes to setting up a new SQL Server, be sure to understand the user needs (response time, storage growth, availability, reporting, etc.) over a predefined period of time before getting too far into the process. In addition, establish a budget for both hardware and software then explain the value for each component so the business knows exactly what is being purchased.
Next Steps
- As a Network Administrator do not be intimidated by SQL Server but also know your limitations. Many of the topics in this tip are just scratching the tip of the iceberg so if you are faced with a situation you are not comfortable with, do not afraid to consult with external resources.
- As you grow as a Network Administrator be sure to grow your skills by attending user group meetings, SQL Saturday's, web casts and SQL PASS as well as reading technical tips, articles, white papers, etc. on a regular basis.
- Keep in mind that with each version of SQL Server a new set of opportunities exist to learn about the product and implement options to benefit the organization.
- Check out these related MSSQLTips:
- SQL Server DBA Checklist
- SQL Server Backup Checklist
- SQL Server Index Checklist
- SQL Server Index Maintenance Checklist
- SQL Server Code Review Checklist
- SQL Server Database Integrity Checks Checklist
- Checklist to Re-Architect a SQL Server Database
- SQL Server Product Selection Checklist
- SQL Server DBA database management checklist
About the author
Jeremy Kadlec is a Co-Founder, Editor and Author at MSSQLTips.com with more than 300 contributions. He is also the CTO @ Edgewood Solutions and a six-time SQL Server MVP. Jeremy brings 20+ years of SQL Server DBA and Developer experience to the community after earning a bachelor's degree from SSU and master's from UMBC.This author pledges the content of this article is based on professional experience and not AI generated.
View all my tips
