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 |
|
mrpreethi
Starting Member
10 Posts |
 Posted - 2010-05-24 : 04:10:17
|
| Hi ,I have a table with 3 lakh records.That table contains 60-70 columns .We are giving an update statement for all columns and in where condition we use primary key column .FOr ex:update col1=somevalue,col2=somevalue,col3=somevalue...........col1=somevalue where prim_key_col='12';This update statement was very fast earlier in production.Now update is very slow in prod.Same update stmt is faster in NPE and DEv environment .Please let me know the issue .Thanks,Preethi MR |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-05-24 : 05:09:02
|
| Reads blocking Writes? Consider READ_COMMITTED_SNAPSHOTNo maintenance routines? if so Statistics will become stale and Indexes are fragmented. If so set up scheduled tasks for INDEX REBUILD an UPDATE STATISTICS (and consider using FULLSCAN on Update Statistics)Hardware sub-optimal? Move LDF file onto different drive from MDF file, and keep both separate from O/S drive. For further benefits you could move Backup files onto another drive, and use yet another drive for TEMPDB - that's a very general statement, unless you database is HUGE you probably won't have the budget for that many drives, but I have listed them in the order that they are likely to make a difference. |
 |
|
|
|
|
|
Update statement very slow