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.
| Author |
Topic |
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
 Posted - 2006-12-06 : 16:41:43
|
| I have one program that is from our vendor erp system andthe locks on one table only go up to 13018 if not higher than this.That seems a high amount.....does each lock consume memoryOur CPU will sit at 100% aswell and this is the only thing running.Im trying to figure out why and what i need in order to support the SQL Server....Increase locks or increase memoryAny advice is appreciated |
|
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2006-12-08 : 08:49:34
|
| So i sent the information to our vendor and said there is x number of locks on one table and no index.Guess what there was 10 indexes missing for one function. I installed them and it took 4 minutes as apposed to 1.5 - 2 hours....I had to run it twice to make sure ....Wow i know about indexes but really did not take into account it really does improved the processThank you all so much.Im liking indexes now lol |
 |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2006-12-08 : 11:37:21
|
| Indices help pinpoint required records faster.....otherwise the SQL statement has to scan through the entire table....including creating loads of locks 'thinking' it has records processed which are updated.Now go look at other jobs/tables which could use indices!!!! |
|
|
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2006-12-09 : 07:22:13
|
| Thanks.....i will do know i understand indexes and how much they actually reduce the processing. I could not answer why the cpu shot to 100% and when the vice president was asking i was im working on it now i can tell him i fixed it.. |
|
|
|
|
|
|
Excessive Locks