We have a web application with multiple users connecting to SQL Server 2005 database.
Once the users start using the system, I could see in the Process Info from the activity monitor with a several process with status as sleeping and command as Awaiting Command.
I have few questions regarding this for which simple answers would help me ( I searched and couldnt understand from the pages that explained the process information )
My questions are,
1. Does the processes with status sleeping and command as Awaiting Command are needed for the application even after the operations specific to them are complete?
2. Does these process affect the performance ?
3. Does killing these process would affect the application connectivity ?
4. Why do we get several process with status sleeping and command as Awaiting Command? Is this because of the front end programming errors ?
5. What should we do to avoid the increasing number of process with status sleeping and command as Awaiting Command?
I have processes running on the server that show a status of "sleeping" from sp_who and sysprocesses, however they are still running. I run sp_who over and over again and only occasionally the process status shows running, and then switches back to "sleeping" or "defwakeup". I know what all the statuses mean, I just don't know why a running process would ever show as "sleeping". The processes take a very very long time to run as well.
I may be asking a foolish question but I really need an answer for it.. We have our centralized servere where SQL Server 2005 is installed.... Whenever open the management studio from our desktops, execute some queries (It may be any simple query such as select * from) I find the status of that process 'sleeping'...untill we close the studio or in other words untill that process is killed..
I find the status by Management -> Activity monitor...
Please help me with it...
Has there been anything wrong while setting up Sql Server ?
what does the sleeping process will do I am running the following stored procedure the cpu value is increasing by time. I am killing old process manually. How to stop the sleeping processing.
CREATE PROCEDURE SP_MONITOR2 AS select spid, hostname,cpu,status,datediff(mi,last_batch,getdate ())Diff_in_Min from sysprocesses where hostname <>'' and last_batch <>'1900-01-01 00:00:00.000' order by Diff_in_Min desc
I have SQL Server 7.0 and I am not able to kill one of the SPID's who is running a SELECT Statement and showing as sleeping. When I saw in the current activity in EM I see the STATUS as sleeping COMMAND as SELECT, APPLICATION as Microsoft Transaction server, WAITTIME as 7877 and WAITTYPE as EXCHANGE and CPU 10074 Thanks in advance.
During our DR drill we found that the same code which used to run perfectly fine on our Primary Data Centre is running very slow on Disaster Recovery DB Server and there are Lot's of open transaction with sleeping status and waittype as 'AWAITING COMMAND'.CPU, Memory and disk utilization are good. The ping reply between the app server and the DB server is well within the limit's even blocking is not their, also nothing is reported in the error logs. We are using SQL server 2014 STD 64 BIT on Windows Server 2012.
If an MS SQL 2005 Connection is sleeping in the activity monitor, does it mean it's not closed? I'm pretty sure it's closed, just want to confirm. Lately, our DB server got hammered with requests and it reached max-pool size (we implemented caching after that).
I have written an application in VB6 connecting to a SQL Server 2000 database using ADO. This app is running on the same computer as SQL Server.
What I am seeing now is that each day 2-3 new connections are being created by SQL and these connections have a "sleeping" status and "AWAITING COMMAND" command. Also, when double-clicking a connection, it's last TSQL statement is empty... This way, connections are piling up.
Does anyone have an idea why this is happening and what I can do to avoid this ? Also, how can I determine what is causing this ?
I was trying to find the bottle neck on our server while we wererunning a couple very large updates.I ran the following query and noticed there were a couple sleepingspid's that were really eating up the memory. One had a value of16000.I guess my question is was this query still holding on to that memoryeven though the query had finished? Why didn't SQL Server clean it up?select spid,substring(Loginame,1,10) Login,memusage,substring(hostname,1,15) Host,program_name,cmd,statusfrom master..sysprocessesorder by memusage desc
HelloI've prepared a small aplication in VS.NET and I use SqlConnection class.Everything is ok, but when I'm trying to disconnect from server usingif (cnSQL->State != ConnectionState::Closed) cnSQL->Close()there is still connection do server present. I have to close connectionbecause I'm trying to drop this database.Have you ever heard about this kind of problem??Trociu--Plain-text over all!!!/**********/write me : trociu@autonom ict pwr wroc plsearch me : gg: 1382729
Dear, Our ASP.NET scripts send SQL statements (as inline SQL or SP) to process the requested job. After the job execution, the process ID stays in the server and waits for next command with sleeping status.Since this process does not go away, next job adds another process and eventually, the server is overloaded with these processes and dies. How can I kill this sleeping processes?Regards,Echo
We just installed SQL service pack 4. I am now finding that when doing a sp_who2 active, there are a lot of connections that are blocked by itself. The common factor is they all have a status of 'sleeping'. The strange thing is that even though it shows the connection is blocked, it is in fact not and will still return results. Below is a snapshot of a portion of what the sp_who2 active returns:
SPID Status Login HostName BlkBy DBName 53 sleeping sa TRACKER 53 dbABC 58 sleeping sa TRACKER 58 dbCDE 64 sleeping sa TRACKER 64 dbSTA 66 RUNNABLE User12 PC24 . master 70 sleeping User5 ANALYSIS 70 dbBML 74 sleeping sa TRACKER 74 dbCDE 76 sleeping sa TRACKER 76 dbPTS 83 sleeping User5 ANALYSIS 83 dbANA 86 DORMANT User11 CPTDB . NULL
Has anyone seen this? Is it related to the installation of service pack 4? (We have installed the services pack on many other SQL servers, but have not come accross this before.
I am using SQL Server 2000. In Enterprise Mgr, under Management/CurrentActivity, I see a list SPIDs.I have a multi-tiered .NET web app that uses ADO.NET to connect to thedatabase. Each time a Stored Proc is called, a new connection is opened, thedata retreieved, and the connection closed and set to Nothing (in VB.NET).Yet, I see several (15 or so) SPIDs for the user ID that the web app uses toconnect to the database.The database is local and private, so I know all connections are from me.What does Status=SLEEPING Command=Waiting Command mean?What will happen when we get 1000's users on the web app?Is SQL doing some kind of connection pooling?
Has anyone done this and about pulled thier hair out?
I downloaded visual express for web development with sql express. Running fine. Like SQL so much, decided to pop for the Developer package. I don't know what I was thinking, maybe I was going to pay for popcorn for billy g & family in the home theatre that night...but I digress.
After much consternation and a 4:00 a.m. adventure, I managed to get rid of SQL Express and install the developer edition. Now were fine. Even ran the aspnet_regsql and set up the aspnetdb database.
I'm thinking, back to development here.
I select APP_DATE and if I try to add the ASPNETDB.mdf file I get the application is being used by another process. Please close all applications that might access this file and try again. So, I then try to create a new database file. I get this error:
Connections to SQL Server Files ( *.mdf) require the SQL Server Express 2005 to function properly.
I can create a connection to the aspnetdb database in the database connections. However, as I work with some of the new ASP NET Membership/Role code, I find it doesn't work.
Will most code work if the ASPNETDB.mdf is not set up int he APP_DATA section?
Come on Microsoft, I can't be the only shoe-string developer that is going to try this.
Has anyone done this and resolved how to get these two to play along.
If I upgrade to Visual Studio, will I still be straddled with SQLExpress.
Can I run SQLExpress side by side with SQL Developer addition?
Hello all. I have many connections that are sleeping. I can rightclick, kill, up to 2 at a time. It takes about 20 seconds to kill it.Is that normal? I tried to make a stored procedure to kill them but itate all the power of the server, (all users yelled at me at the sametime :o) )Is this length of time normal for killing these processes?ThanksJeff
At one of your client sides we have configured Always on with synchronous mode.Also we have schedule rebuild index and update statistics job which runs in night every alternate day. the issue is there are more then 100 sleeping queries which is blocking update statistics job.
I have to stop update statistics job manually once i come to office manually.
Once I have killed blocking sleeping query but then other sleeping query blocked it and so on.
I was trying to extract data from the source server using OLEDB Source and SQL Server Destination when i encountered this error:
"Transaction (Process ID 135) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.".
What must be done so that even if the table being queried is locked, i wouldn't experience any deadlock?
Hello all, I am running into an interesting scenario on my desktop. I'm running developer edition on Windows XP Professional (9.00.3042.00 SP2 Developer Edition). OS is autopatched via corporate policy and I saw some patches go in last week. This machine is also a hand-me-down so I don't have a clean install of the databases on the machine but I am local admin.
So, starting last week after a forced remote reboot (also a policy) I noticed a few of the databases didn't start back up. I chalked it up to the hard shutdown and went along my merry way. Friday however I know I shut my machine down nicely and this morning when I booted up, I was in the same state I was last Wenesday. 7 of the 18 databases on my machine came up with
FCB:pen: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataTest.mdf'. Diagnose and correct the operating system error, and retry the operation. and it also logs FCB:pen failed: Could not open file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataTest.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
I've caught references to the auto close feature being a possible culprit, no dice as the databases in question are set to False. Recovery mode varies on the databases from Simple to Full. If I cycle the SQL Server service, whatever transient issue it was having with those files is gone. As much as I'd love to disable the virus scanner, network security would not be amused. The data and log files appear to have the same permissions as unaffected database files. Nothing's set to read only or archive as I've caught on other forums as possible gremlins. I have sufficient disk space and the databases are set for unrestricted growth.
Any thoughts on what I could look at? If it was everything coming up in RECOVERY_PENDING it's make more sense to me than a hit or miss type of thing I'm experiencing now.
Dear list Im designing a package that uses Microsofts preplog.exe to prepare web log files to be imported into SQL Server
What Im trying to do is convert this cmd that works into an execute process task D:SSIS ProcessPrepweblogProcessLoad>preplog ex.log > out.log the above dos cmd works 100%
However when I use the Execute Process Task I get this error [Execute Process Task] Error: In Executing "D:SSIS ProcessPrepweblogProcessLoadpreplog.exe" "" at "D:SSIS ProcessPrepweblogProcessLoad", The process exit code was "-1" while the expected was "0".
There are two package varaibles User::gsPreplogInput = ex.log User::gsPreplogOutput = out.log
How do I use the execute process task? I am trying to unzip the file using the freeware PZUnzip.exe and I tried to place the entire command in a batch file and specified the working directory as the location of the batch file, but the task fails with the error:
SSIS package "IngramWeeklyPOS.dtsx" starting.
Error: 0xC0029151 at Unzip download file, Execute Process Task: In Executing "C:ETLPOSDataIngramWeeklyUnzip.bat" "" at "C:ETLPOSDataIngramWeekly", The process exit code was "1" while the expected was "0".
Then I tried to specify the exe directly in the Executable property and the agruments as the location of the zip file and the directory to unzip the files in, but this time it fails with the following message:
SSIS package "IngramWeeklyPOS.dtsx" starting.
Error: 0xC002F304 at Unzip download file, Execute Process Task: An error occurred with the following error message: "%1 is not a valid Win32 application".
The command in the batch file when run from the command line works perfectly and unzips the file, so there is absolutely no problem with the command, I believe it is just the set up of the variables on the execute process task editor under Process. Any input on resolving this will be much appreciated.
I am designing a utility which will keep two similar databases in sync. In other words, copying the new data from db1 to db2 and updating the old data from db1 to db2.
For this I am making use of the 'Tablediff' utility which when provided with server name, database, table info will generate .sql file which can be used to keep the target table in sync with the source table.
I am using the Execute Process Task and the process parameters I am providing are:
The customer.bat file will have the following code: tablediff -sourceserver "LV-SQL5" -sourcedatabase "TC_CTI" -sourcetable "CUSTOMER_1" -destinationserver "LV-SQL2" -destinationdatabase "TC_CTI" -destinationtable "CUSTOMER" -f "c:SQL_bat_Filessql5TC_CTIsql_filescustomer1"
the .sql file will be generated at: C:SQL_bat_Filessql5TC_CTIsql_filescustomer1.
The Problem: The Execute Process Task is working fine, ie., the tables are being compared correctly and the .SQL file is being generated as desired. But the task as such is reporting faliure with the following error :
[Execute Process Task] Error: In Executing "C:SQL_bat_FilesSQL5TC_CTIpackage_occurrence.bat" "" at "C:Program Files (x86)Microsoft SQL Server90COM", The process exit code was "2" while the expected was "0". ]
Some of you may suggest to just set the ForceExecutionResult = Success (infact this is what I am doing now just to get the program working), but, this is not what I desire.
I'm pulling data from Oracle db and load into MS-SQL 2008.For my data type checks during the data load process, what are options to ensure that the data being processed wouldn't fail. such that I can verify first in-hand with the target type of data and then if its valid format load it into destination table else mark it with error flag and push into errors table... All this at the row level.One way I can think of is to load into a staging table then get the source & destination table -column data types, compare them and proceed.
should I just try loading the data directly and if it fails try trouble shooting(which could be a difficult task as I wouldn't know what caused error...)
I am having this table locking issue that I need to start paying attention to as its getting more frequent.
The problem is that the data in the tables is live finance data that needs to be changed and viewed almost real time so what I have picked up so far is that using 'table Hints' may not be a good idea.
I have a guy at work telling me that introducing a data access layer is the only way to solve this, I am not convinced but havnt enough knowledge to back my own feeling up. (asp system not .net).
Hi, I'm trying to upload the ASPNETDB.MDF file to a hosting server via FTP, and everytime when it was uploaded half way(40% or 50%) I would get an error message saying: "550 ASPNETDB.MDF: The process cannot access the file because it is being used by another process" and then the upload failed. I'm using SQL Express. Does anybody know what's the cause? Thanks a lot
Hi. When I try to start a package manually clicking the Start Debugging button I get this after a little while:
Cannot process request because the process (3880) has exited. (Microsoft.DataTransformationServices.VsIntegration)
How can I prevent this from happening? This happens every time I want to start the package and every time the process id is different. Here it is 3880.
I have had a full lock on my sql server and I have a few logs to found the origin of the lock.
I know the process at the head of the lock is the 55 process.
Here are the information I have on this process: Spid 55 55 ecid 5 5 Ecid 0 0 ObjId 0 1784601646 IndId 0 0 Type DB PAG Resource 1:1976242 Mode S IS Status TransID GRANT GRANT TransID 0 16980 TransUOW 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000
lastwaittype PAGEIOLATCH_SH CMD AWAITING COMMAND Physycal id 1059 Login time 2007-07-05 04:29:53.873 nat address DFF06EBF974D Wait type 0x0046 HostName . BlkBy . DBName grpprddb CPUTime 54331 DiskIO 1059 ProgramName
Would someone know a way to identify the origin of the process 55?
I have already tried to execute the following request: select * from SYSOBJECTS where id=1784601646
I have a File System Task Copy file operation to copy a file in an SSIS package. The package when scheduled as a job fails with the following error:
The process cannot access the file 'C:ETLConsignmentAppleAppleRawFile.txt' because it is being used by another process.".
However when I right click on the package and execute it manually from the Integration Services it runs successfully without any problem. I am not certain on how to resolve this issue any inputs will be much appreciated.
Error: 0xC002F304 at Rename file 1, File System Task: An error occurred with the following error message: "The process cannot access the file because it is being used by another process.".
When running two File System Tasks after each other, with the same file, the file is still locked when running the second task. Resulting in an error: 0xC002F304 at Rename file 1, File System Task: An error occurred with the following error message: "The process cannot access the file because it is being used by another process.".
I found a workaround by addind a Execute Process Task before the second File System Task that pings to the localhost. This results in a 5 second delay, but there must be a better solution. Anyone?
