January 23, 2017 at 8:11 am
Daily we populate a swap table in our production environment and rename it with the original table. During this process, we disable the indexes and load the data and rebuild the indexes on swap table to speed up the process. From last few weeks we are observing page file corruption on this table after rename process and all the queries hitting the main table are failing throwing error-Could not continue scan with NOLOCK due to data movement. Any help would be appreciated.
January 23, 2017 at 11:44 am
muth_51 - Monday, January 23, 2017 8:11 AMDaily we populate a swap table in our production environment and rename it with the original table. During this process, we disable the indexes and load the data and rebuild the indexes on swap table to speed up the process. From last few weeks we are observing page file corruption on this table after rename process and all the queries hitting the main table are failing throwing error-Could not continue scan with NOLOCK due to data movement. Any help would be appreciated.
What were the errors when you ran dbcc checkdb? With no_infomsgs all_errormsgs if you haven't run it yet.
Sue
January 23, 2017 at 12:11 pm
muth_51 - Monday, January 23, 2017 8:11 AMDaily we populate a swap table in our production environment and rename it with the original table. During this process, we disable the indexes and load the data and rebuild the indexes on swap table to speed up the process. From last few weeks we are observing page file corruption on this table after rename process and all the queries hitting the main table are failing throwing error-Could not continue scan with NOLOCK due to data movement. Any help would be appreciated.
This is not an error related to page file corruption - this is an error you can get when using NOLOCK inappropriately. In this situation - because you have used NOLOCK and at the same time someone is updating the table causing a page split which then causes the above issue.
If this is happening a lot then you need to review the code and figure out how to execute that code without using NOLOCK.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
January 25, 2017 at 8:03 am
Sue_H - Monday, January 23, 2017 11:44 AMmuth_51 - Monday, January 23, 2017 8:11 AMDaily we populate a swap table in our production environment and rename it with the original table. During this process, we disable the indexes and load the data and rebuild the indexes on swap table to speed up the process. From last few weeks we are observing page file corruption on this table after rename process and all the queries hitting the main table are failing throwing error-Could not continue scan with NOLOCK due to data movement. Any help would be appreciated.What were the errors when you ran dbcc checkdb? With no_infomsgs all_errormsgs if you haven't run it yet.
Sue
no error messages reported.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply