Hey! I wanted a way to monitor each databases usage and the users using it be fore I migrate the databases to a new server, which way would you suggest?
It depends on what you are trying to do, how many databases you are trying to move, why you are trying to move them, and if you want to move one at a time or all at once. I would suggest thinking through the plan and then using Activity Monitor to review the usage information. Knowing what you are trying to do and why will help form the questions that hopefully Activity Monitor can help you answer.
I would start by looking at Performance Monitor or Resource Monitor and checking the four most common bottlenecks (processor, memory, disk, and network). If it looks like one of those is creating an issue then you can dig deeper into the issue to clarify it more. You can look at SQL specific information in the SQL Server Activity Monitor. For example, if processor time seems to spike fairly often and cause slowdowns you might look at the list of recent expensive queries. I like to start with the OS tools in case there is an issue outside of SQL that may be causing performance issues.
I'm having to become the database backup for my company and I really appreciate your videos!!!!!!!
Thanks, I am glad they are helpful.
Hey! I wanted a way to monitor each databases usage and the users using it be fore I migrate the databases to a new server, which way would you suggest?
It depends on what you are trying to do, how many databases you are trying to move, why you are trying to move them, and if you want to move one at a time or all at once. I would suggest thinking through the plan and then using Activity Monitor to review the usage information. Knowing what you are trying to do and why will help form the questions that hopefully Activity Monitor can help you answer.
Can you give some insights about Database I/O? Particularly to look at when db performance of the application is slow..
Which is the best way to investigate when an user complains about slow performance in database server?
I would start by looking at Performance Monitor or Resource Monitor and checking the four most common bottlenecks (processor, memory, disk, and network). If it looks like one of those is creating an issue then you can dig deeper into the issue to clarify it more. You can look at SQL specific information in the SQL Server Activity Monitor. For example, if processor time seems to spike fairly often and cause slowdowns you might look at the list of recent expensive queries. I like to start with the OS tools in case there is an issue outside of SQL that may be causing performance issues.
@@ddaltonyvcc Thank you very much David.