network profile
| bio | website | |
|---|---|---|
| location | Barcelona, Spain | |
| age | 32 | |
| visits | member for | 1 year, 10 months |
| seen | Feb 7 at 16:42 | |
| stats | profile views | 4 |
|
Jan 31 |
awarded | Commentator |
|
Jan 31 |
awarded | Scholar |
|
Jan 31 |
comment |
SQL update satement taking a very long time / high disk usage for hours Drop indexes / Update / Rebuild indexes works, and although I'd prefer not to have to do something that drastic, I don't see that I have a choice. Thanks! |
|
Jan 31 |
accepted | SQL update satement taking a very long time / high disk usage for hours |
|
Jan 31 |
comment |
SQL update satement taking a very long time / high disk usage for hours Doesn't hang always on the same id. But the data might be corrupted. |
|
Jan 30 |
revised |
SQL update satement taking a very long time / high disk usage for hours added 744 characters in body |
|
Jan 30 |
comment |
SQL update satement taking a very long time / high disk usage for hours no, it's 31GB free out of 120GB, so I think it's ok |
|
Jan 30 |
comment |
SQL update satement taking a very long time / high disk usage for hours DForck42: I have not tested but I'm quite sure the compiler is going to tell me the identifier X is ambiguous. |
|
Jan 30 |
comment |
SQL update satement taking a very long time / high disk usage for hours For point 1 see my answer to ik_zelf. The cursor is there for investigation reasons and doesn't have that much impact. I am going to implement the rest of your suggestions, I think it's all I have left to do. If it works, I will still be left without an explanation on what happens now though... |
|
Jan 30 |
comment |
SQL update satement taking a very long time / high disk usage for hours I don't think that's the point. I realize the update of indexed records takes time, and I know that, overall, part of the time it takes is due to this. But I expect this, and I'm ok with it: as I said, updating 99% of the lines takes 5 min (even using the cursor), but for some reason, one line (and not always the same) takes 5h. What worries me is this particular behaviour. |
|
Jan 29 |
comment |
SQL update satement taking a very long time / high disk usage for hours @MartinSmith see edits 2 & 3 |
|
Jan 29 |
revised |
SQL update satement taking a very long time / high disk usage for hours deleted 2420 characters in body |
|
Jan 29 |
revised |
SQL update satement taking a very long time / high disk usage for hours deleted 2420 characters in body |
|
Jan 29 |
revised |
SQL update satement taking a very long time / high disk usage for hours deleted 2420 characters in body |
|
Jan 29 |
comment |
SQL update satement taking a very long time / high disk usage for hours @MartinSmith I added some info from procmon and DBCC page. |
|
Jan 29 |
revised |
SQL update satement taking a very long time / high disk usage for hours added 3154 characters in body |
|
Jan 29 |
revised |
SQL update satement taking a very long time / high disk usage for hours added 3154 characters in body |
|
Jan 29 |
comment |
SQL update satement taking a very long time / high disk usage for hours @Stuart Last time I checked it was around 1% (this table usually doesn't get written very often on my machine), but I'll have to stop the query to check it. I'll do that, restore and give the execution plan. |
|
Jan 29 |
comment |
SQL update satement taking a very long time / high disk usage for hours @tschmit007 Its SQL 2008 R2 x64 Dev Edition on Win Server 2008 R2 x64. It is a VM running itself on Hyper-V (host is 2008 R2 x64 too); the VM has 4.2GB physical memory used out of 5GB, and 4.6GB commit out of 10GB max; the host has 7.2GB physical memory used out of 8GB, and 7.8 commit out of 16GB max. Both machines are slower due to HD usage but not clogged. |
|
Jan 29 |
comment |
SQL update satement taking a very long time / high disk usage for hours @MartinSmith There is absolutely nothing since I restored in the SSMS SQL Server Logs and nothing either in the Windows event log |
