Contents
What are the most common SQL Server performance problems?
Diagnose problems. To start troubleshooting, you have to define the symptoms first. The most common SQL Server performance symptoms are CPU, memory, network, and I/O bottlenecks, and slow running queries. CPU bottlenecks are caused by insufficient hardware resources.
What’s the first step in troubleshooting SQL Server?
First Step: Pull Yourself Together. You are the person to solve the problem, so you need to be calm even when the people around you aren’t calm. You can’t provide a solution if you don’t work in an orderly fashion even if you are the person who should know how to fix the problem.
What kind of problem can a SQL Server Administrator face?
A situation that a SQL Server database administrator can face is solving an incident in a production environment. An incident involving an online service with high concurrent usage could be one of the most challenging tasks you will face.
Why is it important to be on top of SQL Server performance?
Performance is always one of the DBA’s top priorities, and there’s one thing every DBA knows about SQL Server ® performance: if there’s a problem you’re going to hear about it. It’s far better to be proactive and stay in top of your system’s performance than it is to be reactive when it comes to addressing user complaints.
What are the security considerations for SQL Server?
Typically, there are three entity types participating to such data flow: Clients (i.e. Application server or direct client connections) To secure your application, you can perform the below: Do not expose user passwords in code or in external files (i.e. file with connection strings) that are used by the application.
What should I do if someone is using my SQL Server?
Unless the involved databases are Contained Databases, these users create a risk because potential attackers might get access to them and inherit their permissions on the database. The recommended practice is after verifying that these users are not used in any way, to first disable them (REVOKE CONNECT) and eventually remove them.
Why is it important to have encrypted connection to SQL Server?
Establish an encrypted connection to your SQL Server instance. With an encrypted connection, even if a potential attacker intercepts the network traffic between your client and the SQL server instance, he or she will not be able to read the data because it will not be just clear text but rather encrypted data packets.