Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 small queries tying up db

Author  Topic 

esthera
Master Smack Fu Yak Hacker

1410 Posts

Posted - 2008-07-21 : 02:06:57
ok so i have finally narrowed it down that when i run a certain program that updates my table
update tabel set x=1 where id=34343. Now I could be running this update stament for 4000 rows - it seems that even when i stop running the update statement it's still running in sql and using the cpu to 100%

why would this be? shouldn't a simple update statement run intstantly?
where does it save it in memory that it's running after an hour of being stopped and is there anyway to clear this?

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2008-07-21 : 02:22:27
Use transaction if you are not sure you want to commit the update.



E 12°55'05.25"
N 56°04'39.16"
Go to Top of Page

esthera
Master Smack Fu Yak Hacker

1410 Posts

Posted - 2008-07-21 : 02:36:29
currently it's just a bunch of update statements run from ado connection

any way to clear them from memory?
Go to Top of Page

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2008-07-21 : 03:25:00
Define "Clear them from memory".



E 12°55'05.25"
N 56°04'39.16"
Go to Top of Page

dexter.knudson
Constraint Violating Yak Guru

260 Posts

Posted - 2008-07-21 : 04:41:23
Do you have a primary key or index on X? How many rows does the table have?
Go to Top of Page

esthera
Master Smack Fu Yak Hacker

1410 Posts

Posted - 2008-07-21 : 04:54:47
many rows .. and no index because i have more important fields that i needed to index for other parts of the program
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-07-21 : 22:56:03
May due to table scan then.
Go to Top of Page
   

- Advertisement -