This question has already been asked, but the answer didn’t give detail as to what the problem could be, so I’m asking the following.
Our application currently runs using SQL Server 2005. We are in the process of testing using 2008.
The application is used for bulk data changes and database merges. The application does not login to a database when it starts up, the user needs to select one to login to first to check that no others users are logged in. At this point, a Checkpoint process is started. So far we have left this to run for over 2 hours, and still it continues to run. Restarting the server service sometimes clears this process.
We have found a solution outside of the application. Using SQL Server Management Studio, we increase the DB’s log file Autogrowth %, and then decrease it back to the original value. We then restart the server service. The checkpoint process is no longer running on the DB and we’re also able to run a manual checkpoint process (Checkpoint 1) outside of the application with it completing.
When we use the application on the DB again, the checkpoint process starts up and continues to run.
Is this a problem with SQL Server 2008, or are there settings in 2008 that we can use? The only one I’ve found is the recovery interval, and from what I’ve read I don’t think it will resolve our current problem.
If this is a problem with 2008, we could make changes to our application to ignore the checkpoint process when checking for logged on users. Would this be a concern to have the process running in the background while the application runs. Our application allows users to change code values across several related tables and merge two database together. This process uses insert into.
Sorry, I know this is an oldish question, but I'm curious as to why you want to run a checkpoint under that scenario?
answered May 20, 2010 at 09:17 PM
Matt Whitfield ♦♦