locked
Local database cache - SQL Server 2008 settings RRS feed

  • Question

  • When a create a new "Local Database cache component", retention period is configured in SQL Server 2008.
    For testing purpose, I set a short retention period. But I have always to wait about 3 days to see the cleanup task doing its job.
    Here is the query I use to test if cleanup job was executed:
    select ID, sys_change_operation from CHANGETABLE(CHANGES dbo.T_TEST, 1) AS CT
    What is going wrong?

    Sorry for posting here, I get no answer on SQL Server 2008 forums...
    • Moved by Max Wang_1983 Thursday, April 21, 2011 11:59 PM forum consolidation (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Tuesday, August 4, 2009 6:48 AM

Answers

All replies

  • How short was the retention peiod you have set?  Try to set up 30 minutes and restart SQL server and see if the cleanup works.

    Thanks.
    Leo Zhou ------ This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 5, 2009 6:40 PM
    Answerer
  • Hi Leo Zhou,

    Thanks for your answer.
    I've set a retention period of 10 min. I'm going to follow your advice and try to restart SQL Server after changing settings.
    It sounds that cleanup cannot occur in smaller period than 30min?
    I'll confirm if I succed in cleaning every 30 min with your advice.

    Thank you

    Olivier
    Thursday, August 6, 2009 1:01 PM
  • Hi Leo Zhou,

    I did many tests, use SQL Server Management Studio GUI and T-SQL statements to configure change tracking (35 minutes).
    Each time I restarted SQL Server Instance.
    But I still need to wait more than 2 days to see cleanup working.

    Thanks
    Olivier
    Monday, August 10, 2009 9:32 AM
  • Ho Omonney,
    I am trying to repro this locally. WIll post an answer by EOD

    Maheshwar Jayaraman - WCF -- http://blogs.msdn.com/dotnetremoting
    Tuesday, August 11, 2009 7:13 PM
    Moderator
  • It looks like to be a bug in Sql Server.
    I posted a request here:
    http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=482258
    I got an answer:
    "We are seeing a similar issue which we are issuing a hotfix . We need to confirm if it is the same."

    Thanks for your help
    • Marked as answer by omonney Saturday, August 15, 2009 7:03 AM
    Saturday, August 15, 2009 7:03 AM