5 Replies Latest reply on Feb 10, 2010 12:34 PM by mwilke

    Group Scan Schedules?

      Does anyone have real world experience for Group Scanning on the database? Is there a schedule best practice? Does it depend on the number of nodes (objects) that is on the database? The EEPC Best Practice guide touches a little on this

        • 1. Re: Group Scan Schedules?

          Do it on a backup database at regular maintenance schedule (once per week). If backup show no orphans, your primary should be good too. Frequency depends on many factors, mostly on how often orphans are found (an that depends on connections reliability and if database was much in use during backup). Do never perform it on live database!

          • 2. Re: Group Scan Schedules?

            Is it because running the scan on a live database slows down performance during the day? Can I simply run it after work hours without issue?

            • 3. Re: Group Scan Schedules?

              It is because objects that are in the process of being created/updated could be marked as orphans. It is better not to take any chances.

              • 4. Re: Group Scan Schedules?

                DB w/ ~24,000 objects, I run it once/month or so, after business hours. (I don't have a maintenance window defined"). If you can stop the database service while you do it, it's faster/cleaner.

                 

                According to the Orphan Report (which runs once/week), I have 2 orphans right now.

                • 5. Re: Group Scan Schedules?
                  mwilke

                  It for sure would be best to run group scans with the services down so nothing is locked or trying to do work while you are scanning.  That being said, not everyone can shut their services down for something like this.  I have ran group scan on live DBs many many times.  Never had an issue with it but Peter is right... should be done during down times or maint windows for safer results.