inusual reindexing behavior in SQL 2000
- From: "zoli" <car.hunt@xxxxxxxxxxxx>
- Date: 27 Mar 2006 23:48:03 -0800
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
.
- Follow-Ups:
- Re: inusual reindexing behavior in SQL 2000
- From: m . bohse
- Re: inusual reindexing behavior in SQL 2000
- Prev by Date: install problems
- Next by Date: Re: inusual reindexing behavior in SQL 2000
- Previous by thread: install problems
- Next by thread: Re: inusual reindexing behavior in SQL 2000
- Index(es):
Relevant Pages
|
