 |
| SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005. |
Welcome to the p2p.wrox.com Forums.
You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|

October 14th, 2004, 07:30 PM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 141
Thanks: 1
Thanked 0 Times in 0 Posts
|
|
Cannot stop the process
Hi All,
I was running a sql script in Query Analyzer to delete
the rows from a table. The Deleting process was taking very long time
and I had to close the query analyzer.
I re-started the query analyzer and that process was still running.
When I try to kill the process (kill 51), I got the following message;
"SPID 51: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 155 seconds."
This table is locked and I cannot access the table.
Thanks in advance,
mcinar
__________________
MCinar
Love all the creatures because of the creator.
|
|

October 14th, 2004, 08:06 PM
|
|
Friend of Wrox
|
|
Join Date: Nov 2003
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
If your process have not stop and showing as executing. Stop and restart your SQL Server Agent
Jaime E. Maccou
Applications Analyst
|
|

October 14th, 2004, 10:00 PM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 141
Thanks: 1
Thanked 0 Times in 0 Posts
|
|
Jemacc,
Thank you for your advice.
I tried to stop and restart "MS SQLSERVER",
but I get the following error message during the restart, "MS SQLSERVER stopping. An Error 1056
(An instance of the service is already running. Occured while performing the service operation on the
MS SQLSERVER service."
I also stopped and restarted SQL Server Agent.
Thanks,
MCinar
|
|

October 14th, 2004, 11:29 PM
|
|
Friend of Wrox
|
|
Join Date: Nov 2003
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
What this indicates is the you may have already tried to stop the SQL Server Services and it could not completed communication with the services.
you force a stop manually from the command line
net stop mssqlserver
and to restart a default instance
sqlservr.exe -c
and to restart a name instance
sqlservr.exe -c -s {instancename}
Jaime E. Maccou
Applications Analyst
|
|

October 15th, 2004, 08:50 AM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 141
Thanks: 1
Thanked 0 Times in 0 Posts
|
|
Jemacc,
Thank you for the advice.
I tried to use "net stop mssqlserver", I got the following message;
"This service could not be controlled in its present state.
More help is available by typing NET HELPMSG 2189"
And this help command explains;
"Try the operation again in a minute or two.
If this problem persists,, contact tech support. Be prepared to give the name of the service and
other information about the system. Such as the services and applications that were running, and the type and amount of network activity on the computer at the time of the problem"
I am not sure what else can be tried?
Thanks,
MCinar
|
|

October 15th, 2004, 09:15 AM
|
|
Friend of Wrox
|
|
Join Date: Nov 2003
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
If you are familiar with task manager, check the status of the SQL server (sqlsrv.exe) and try to end the process from there.
Is this your production server? If no, reboot the server and this should clearly and refresh all services.
Jaime E. Maccou
Applications Analyst
|
|

October 15th, 2004, 10:45 AM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 141
Thanks: 1
Thanked 0 Times in 0 Posts
|
|
Jemacc,
It is a test server and I will re-start the computer.
If that doesn't work, I will re-install SQL server and restore the database.
Thanks,
MCinar
|
|

October 15th, 2004, 11:54 AM
|
|
Friend of Wrox
|
|
Join Date: Nov 2003
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
This is also a good time to review your disaster and recovery plan. If you do not have one, I suggest that you put one in place.
I hope everything works out for you.
Jaime E. Maccou
Applications Analyst
|
|

October 15th, 2004, 12:05 PM
|
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 141
Thanks: 1
Thanked 0 Times in 0 Posts
|
|
Jemacc,
Thank you,
MCinar
|
|

October 19th, 2004, 05:09 AM
|
|
Friend of Wrox
|
|
Join Date: Sep 2004
Posts: 109
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
HI,
U can use Current Activity from Enterpise manager to Kill the process selectivel (U must be a member of sysadmin fixed role).
Further I suggest u to use TRUNCATE Table instead of Delete. Its quick but be aware that it doesn't log the Transaction.
I am not sure if u r using transaction block to perform the delete. There may be chnaces where u r Beggining a Transaction and not commiting it. Such case will prevent even opening a table in firehose mode through enterprice manager.
Hope this helps
B. Anant
|
|
 |