SQL Server for Network Administrators
October 16th 2008 11:39
SQL Server for Network Administrators
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
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
How to tell what SQL Server version you are running
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
SQL Server 2005 Log File Viewer
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.
Additional information
Finding SQL Server Agent Job Failures
Troubleshooting Performance Problems in SQL Server 2005
Tempdb Configuration Best Practices in SQL Server
Script to determine free space to support shrinking SQL Server database files
Monitoring SQL Server database transaction log space
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
Free SQL Server Troubleshooting Tool from Microsoft
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.
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
Script to retrieve SQL Server database backup history; last week, most recent and no backups
SQL Server Backup History Analysis
Do you really know if your SQL Server database backups are successful?
SQL Server point in time recovery
Simple script to backup all SQL Server databases
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
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
Applying SQL Server Service Packs
Issue with SQL Server 2005 SP2
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
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.
Additional information
Properly Sizing the SQL Server TempDB Database
Easing the Capacity Planning Burden
Hard Drive Configurations for SQL Server
Hardware 101 for SQL Server DBAs
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
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.
How to tell what SQL Server version you are running
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
SQL Server 2005 Log File Viewer
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.
Additional information
Finding SQL Server Agent Job Failures
Troubleshooting Performance Problems in SQL Server 2005
Tempdb Configuration Best Practices in SQL Server
Script to determine free space to support shrinking SQL Server database files
Monitoring SQL Server database transaction log space
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
Free SQL Server Troubleshooting Tool from Microsoft
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.
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
Script to retrieve SQL Server database backup history; last week, most recent and no backups
SQL Server Backup History Analysis
Do you really know if your SQL Server database backups are successful?
SQL Server point in time recovery
Simple script to backup all SQL Server databases
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
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
Applying SQL Server Service Packs
Issue with SQL Server 2005 SP2
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
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.
Additional information
Properly Sizing the SQL Server TempDB Database
Easing the Capacity Planning Burden
Hard Drive Configurations for SQL Server
Hardware 101 for SQL Server DBAs
| 44 |
| Vote |
Shared on
Subscribe to this blog
