DB Maintenance job

I have 2 SQL 7 servers. First one is NT. I created job using default. Like
reorganize data and Index, remove unused spaceand attempt to repair any minor
index problem. Win NT machine take more than 3 hours for the part check data
and Index Linkage.
For Win 2k machine, I am doing the same thing. Here check data and Index
Linkage finishes in a second. Or doing nothing.
Please give me an idea why it is happening. Because my 2 database are acting
different in term of performance.
Probably there are users in the database and "repairing" can't set to single user mode, result it
does nothing and you get a warning from the job. Don't use this setting. If you have a corruption,
you ant to be there, do root causes analysis and handle the situation based on the he circumstances:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Astros" <Astros@.discussions.microsoft.com> wrote in message
news:A44FADEF-FD22-45E7-BC29-A13F16A16A56@.microsoft.com...
>I have 2 SQL 7 servers. First one is NT. I created job using default. Like
> reorganize data and Index, remove unused spaceand attempt to repair any minor
> index problem. Win NT machine take more than 3 hours for the part check data
> and Index Linkage.
> For Win 2k machine, I am doing the same thing. Here check data and Index
> Linkage finishes in a second. Or doing nothing.
> Please give me an idea why it is happening. Because my 2 database are acting
> different in term of performance.
>
|||This repair has nothng to do with reindex. My reindex part of the job ran
fine. Still I have performance issue. What do you think?
Thank you for your reply.
"Tibor Karaszi" wrote:

> Probably there are users in the database and "repairing" can't set to single user mode, result it
> does nothing and you get a warning from the job. Don't use this setting. If you have a corruption,
> you ant to be there, do root causes analysis and handle the situation based on the he circumstances:
> http://www.karaszi.com/SQLServer/inf...suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Astros" <Astros@.discussions.microsoft.com> wrote in message
> news:A44FADEF-FD22-45E7-BC29-A13F16A16A56@.microsoft.com...
>
>
|||Perhaps some bug in maint wiz? Are you current on service packs? Same service pack on both? If you
specify a report file for the maint plan, any errors or warnings?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Astros" <Astros@.discussions.microsoft.com> wrote in message
news:4145C478-EAF4-43C0-8E16-F5E6B030972F@.microsoft.com...[vbcol=seagreen]
> This repair has nothng to do with reindex. My reindex part of the job ran
> fine. Still I have performance issue. What do you think?
> Thank you for your reply.
> "Tibor Karaszi" wrote: