May 17, 2005 at 11:30 am
Hi DBA's and Developers
We added a bit column to a 7 million plus row Transactions table in our production database. After that our Payment Processor job started timing out for some reason. I ran a native UPDATE STATS on the Transactions table and the problem went away. But then, I ran my weekly scheduled DB Maint Plan Optimizations job (Reorganize data and index pages, change free space to 10%) and the Payment Processor job times out again. Then to fix it I will run the native UPDATE STATS job on the Transactions table and the problem will go away again.
Any ideas from you would be greatly appreciated!
DBA Dave
May 18, 2005 at 6:05 am
There was a bug in pre-SP3 SQL Server that caused issues with bit columns included in indexes (ours was the last column in the index). If either situation exists, I would suggest two things:
May 18, 2005 at 6:11 am
Well, that didn't work... the suggestions were: Install SP3a or SP4 and/or remove the bit column from the index (just in case).
May 18, 2005 at 1:43 pm
R2ro,
I made a mistake. The last column is NOT a bit field, it's an int and it's not indexed.
DBA Dave
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply