Groups | Blog | Home
all groups > sql server programming > february 2004 >

sql server programming : Stopping indexing


Derek
2/8/2004 9:56:06 PM
I created 4 single column indexes on a table with about 20,000 rows. This table is replicated out to about 4 other databases

The CPU usage went up to flat out. That was two hours ago and the server will need to be used in about another 2 hours

I'm assuming that the process won't finish before I need the server and I don't care if I lose the indexes. How do I kill the process

Yours urgentl
Derek
2/8/2004 10:41:07 PM
I've just started running profiler. I have no experience in this. Any suggestions
I created them in EM
Uri Dimant
2/9/2004 8:12:41 AM
Derek
Have you ran SQL Server Profiler to find out what's going on ?
How did you create these indexes ? By EM or QA?
To kill the process use KILL command (For more details please refer to BOL)



[quoted text, click to view]

Uri Dimant
2/9/2004 8:44:36 AM
Derek
http://www.sql-server-performance.com/sql_server_profiler_tips.asp



[quoted text, click to view]
(it wouldn't go in - it would time out earlier). I've killed one process,
but CPU usage has just gotten worse???

Mike Kruchten
2/9/2004 4:45:25 PM
What kind of machine is this running on? Indexing 20,000 rows should take
any time at all.

Mike Kruchten

[quoted text, click to view]

AddThis Social Bookmark Button