Sorry if this is not the right newsgroup to out this in (let em know
and I will put it in the correct group)

We have SQL 2000 standard edition (with the SP4) installed on windows
2003 server. we have transactional replication occuring on a regular
basis to 2 servers (1 remote and 1 local).

Our backup strategy is dailybackup at 8PM and incremental log backups
every 20 minutes between 2am and 11pm (i know the timings needs to
change).

Over the weekend we had an interesting set of circumstances where the
drive space was eaten up by SQL. It would appear that the database
server has done a reindex of a number of tables on one of the
databases. This manefested itself as a massive log backup of 7GB at
2am.
I have checked all the maintenance jobs, and manual jobs that run on
the database and NONE of them have anything set for reindexing to
occur.

The only reason that I know it has happened at all was by reading the
7GB transaction log backup using ApexSQL Log reader.

Is there any other reason that the database would be reindexed without
any user interaction? or is there something that would cause this
behavior. I know it is the weekend where the clocks went forward, but I
know of no reason that this behavior should occur.

Any help would be appreciated,

Perplexed Regards,

Z

zoli,

I can't think of a reason why reindexing should start spontanously
other that maybe your application started it. I know some applications
like SAP schedule maintenance tasks themselves and you won't find it in
EM.
But if you can read the T-log with ApexLogreader you should also see
which login/user has started the transaction.

Markus

Thanks Markus,

That was my thought too, the login is the one we use for the SQL Server
Agent, hense why I wondered what was going on. In my opinion I think it
is either internal to SQL or an administrator/power user has done
something explicitly (which they all deny). I just wanted to eliminate
the internal SQL option from the equation.

If you have any more thoughts I am open to suggestion.

Regards
Z