Maintenence Plan Questions

I wanted to know at what time should I be scheduling the data optimization and data integrity jobs? Will these jobs hinder performance? If so then I should probably schedule the jobs after work hours.

Also, we were not going to use the backup/recovery jobs that sql server offer, we have our own backup software. So, will the data integrity or data optimization job affect backups? Should I perform these jobs before or after backups?

Thanks,
LauraThat is a good plan. The optimizations are NORMALLY non-intrusive, but particularly the first time they are run after significant changes they can hit the database like a freight train.

Your plan to start the optimizations after the backup finishes is a good one.

-PatP|||I would recommend not to use 3rd-party backup tools (unless it's SQLLiteSpeed) to backup live database/transaction log. Use native or purchase SQLLiteSpeed to create OS backup files, and only then use other tools to backup to a tape, for example.|||Ok thanks for the responses, it helped me alot

-laura

maintenance schedule and option

Hi all:
I've been using the maintenance scheduler to setup backup
routines. My question is should one use any of the:
1.) Optimization Options in the wizard ie...
--reorg data and indexes
--update stats
--kill unused space
2.) Check db integrity
I thought sql did all of these services on a maintenance
routine of its own automatically. Please advise. Thanks.If you reorg, then you don't have to update stats (and stats are
auto-updated anyhow).
Whether you should reorg really depends on if you get any better performance
out if it. Whether you do or not depends on a lot of factors, so testing
might be the most practical solution for you. You could always check
fragmentation level for your indexes using DBCC SHOWCONTIG etc, but unless
you understand physical database architecture, indexes etc well, then it
might just be easier to give it a try.
I do not recommend removing unused space. Chances are that the space will
grow between period anyhow, and growing costs performance.
I prefer to check integrity as often as I can. If you can do it once per
night - go for it.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"steve" <anonymous@.discussions.microsoft.com> wrote in message
news:145201c3a880$7180c2d0$a501280a@.phx.gbl...
> Hi all:
> I've been using the maintenance scheduler to setup backup
> routines. My question is should one use any of the:
> 1.) Optimization Options in the wizard ie...
> --reorg data and indexes
> --update stats
> --kill unused space
> 2.) Check db integrity
>
> I thought sql did all of these services on a maintenance
> routine of its own automatically. Please advise. Thanks.|||reorg data and indexes - most likely depending upon the size of your
databases. the larger your databases, the more concerned you should be
with when and how often you can run this.
update stats - no, if you reorg data and indexes regularly. yes if you
don't choose to reorg using the maintenance plan.
kill unused space - never
check db integrity - yes
steve wrote:
> Hi all:
> I've been using the maintenance scheduler to setup backup
> routines. My question is should one use any of the:
> 1.) Optimization Options in the wizard ie...
> --reorg data and indexes
> --update stats
> --kill unused space
> 2.) Check db integrity
> I thought sql did all of these services on a maintenance
> routine of its own automatically. Please advise. Thanks.