res00f0j2
asked on
is there a way to identify which program is using SQL server?
We are using a Win SBS 2003 server. there are currently processes that are running on it that I'm unsure of what they are. is there a way to identify the program or process that the sqlservr.exe belongs to?
MSSystems
I would recommend that you run sp_who2 or try the activity monitor in SQL Server Management Studio
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can also try the following from command prompt to view the executables. Then just find the executables with destination port 1433. (Or available SQL ports) . view the following website for sql ports.
http://support.microsoft.com/kb/287932
http://support.microsoft.com/kb/287932
Sorry...
I misunderstood your question. FDiskWizard is right. This is Microsoft SQL Server. A database engine, it comes standard with Small Business Server.
I misunderstood your question. FDiskWizard is right. This is Microsoft SQL Server. A database engine, it comes standard with Small Business Server.
ASKER
MSSystems:
So far, I have tried to run sp_who2. but I'm not sure how to do it. I tried just running sp_who2 but windows states that it can't find it. is this something I have to purchase or download? I also did not see what to try from the command prompt on your last comment.
Sorry, but I have almost no experience with SQL. I also cound not figure out activity monitor in SQL Server Management Studio.
FDiskWizard:
Services.msc does not give enough information to determine which program is using SQL.
Currently downloading Sysinternals Suite
So far, I have tried to run sp_who2. but I'm not sure how to do it. I tried just running sp_who2 but windows states that it can't find it. is this something I have to purchase or download? I also did not see what to try from the command prompt on your last comment.
Sorry, but I have almost no experience with SQL. I also cound not figure out activity monitor in SQL Server Management Studio.
FDiskWizard:
Services.msc does not give enough information to determine which program is using SQL.
Currently downloading Sysinternals Suite
My apologies I thought I attached it as code. Here it is: netstat –bnaov
Sp_who2 is a SQL system stored procedure. This needs to be executed within sql server management studio as a query. The activity monitor is also part of SQL Server Management Studio (SSMS). The SSMS can be access by clicking on start - All Programs – Microsoft SQL Server – Microsoft SQL Server Management Studio.
Sp_who2 is a SQL system stored procedure. This needs to be executed within sql server management studio as a query. The activity monitor is also part of SQL Server Management Studio (SSMS). The SSMS can be access by clicking on start - All Programs – Microsoft SQL Server – Microsoft SQL Server Management Studio.
netstat –bnaov
ASKER
FDiskWizard:
Wow! you where not kidding when you said Sysinternals Suite (from Microsoft) Procexp.exe can you give you more info on processes than you ever want to know...
I can spend all day looking at interesting data from all processes. Thanks a lot for this tip. I'm sure I will use this utilities often. Unfortunately for now, I don't have the time though. the only thing it tells me about the sqlservr.exe process is "MSSQL$SBSMONITORING" for both Service and Display name.
Wow! you where not kidding when you said Sysinternals Suite (from Microsoft) Procexp.exe can you give you more info on processes than you ever want to know...
I can spend all day looking at interesting data from all processes. Thanks a lot for this tip. I'm sure I will use this utilities often. Unfortunately for now, I don't have the time though. the only thing it tells me about the sqlservr.exe process is "MSSQL$SBSMONITORING" for both Service and Display name.
ASKER
Let me elaborate a bit on why or what started me on this quest.
We have a SBS 2003 server that I'm sure it's starting to be pushed to it's limit. However, up until just a few weeks ago. everything has been working smoothly. Nothing new has been installed or changed on the server, hardware or software. but now for some reason, every few minutes, it seems like the server freezes for a few seconds. Freeze time can vary from like 5 to 15 seconds, and I can't figure out why.
I noticed it when I was trying to stream music from a network drive and the music started pausing two or three times during each track. Also noticed that when people login, sometimes even though the drive mappings all seem to work and be created, some data was not accessible or visible. but if you waited for some time, the data became visible. Kind of weird.
Don't know if this helps but I though I would mention it.
We have a SBS 2003 server that I'm sure it's starting to be pushed to it's limit. However, up until just a few weeks ago. everything has been working smoothly. Nothing new has been installed or changed on the server, hardware or software. but now for some reason, every few minutes, it seems like the server freezes for a few seconds. Freeze time can vary from like 5 to 15 seconds, and I can't figure out why.
I noticed it when I was trying to stream music from a network drive and the music started pausing two or three times during each track. Also noticed that when people login, sometimes even though the drive mappings all seem to work and be created, some data was not accessible or visible. but if you waited for some time, the data became visible. Kind of weird.
Don't know if this helps but I though I would mention it.
ASKER
Oh yea! one more thing.
I also noticed that the process sqlservr.exe grows with time. from about 500,700K to about 1.5GB with time. The only thing that seems to reduce the size is when I reboot the server. Then the memory being used by this process start again at around 500,700k
I also noticed that the process sqlservr.exe grows with time. from about 500,700K to about 1.5GB with time. The only thing that seems to reduce the size is when I reboot the server. Then the memory being used by this process start again at around 500,700k
SQL Server always assigns memory dynamically. SQL will always keep the memory after assigning it to prevent paging and unnecessary disk IOs. Do you know if someone is actually making use of this SQL instance? (Databases)
Also are you running some application like backup exec? You will get some applications that require SQL to function. Also, how much disk space is available? See in your performance monitor if you are experiencing excessive paging.
Also are you running some application like backup exec? You will get some applications that require SQL to function. Also, how much disk space is available? See in your performance monitor if you are experiencing excessive paging.
ASKER
I'm sure the application using the SQL instance is necessary. But there are a few applications on the server.
That's why I was wondering if there was an easy way to identify which application is the one using the sqlservr.exe.
I guess that I could start stopping the services and see what application is the one that uses it once the app/service is stopped. but I was trying to avoid doing it this way.
That's why I was wondering if there was an easy way to identify which application is the one using the sqlservr.exe.
I guess that I could start stopping the services and see what application is the one that uses it once the app/service is stopped. but I was trying to avoid doing it this way.
Did you try running netstat –bnaov in command prompt?