Is this some structural problem?
From: MZeeshan (mzeeshan_at_community.nospam)
Date: 01/10/05
- Next message: Fredrik Celin: "Sql Server 2000 Mulitlingual Best Practices (Collations and sorting)"
- Previous message: John Lantz: "understanding server trace statistics in query analyzer"
- Next in thread: Sophie Guo [MSFT]: "Is this some structural problem?"
- Reply: Sophie Guo [MSFT]: "Is this some structural problem?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 10 Jan 2005 08:13:04 -0800
Hello-
We were on SQL 7.0 / Windows NT and have moved to SQL 2000 sp4a / Windows
2003. Since upgrade, we have seen some strange behavior.
Following are some of the observations so far:
1. We have witnessed exceedingly large database restoration timings. With
SQL 7.0, it used to take around 1.5-2.0 hours to restore database sized 125+
GB (with around 70 GB of data... we had some fragmentation problems!). Now,
the whole process takes from 4 to 9 hours. The restoration times are very
large when restored the first time (true, I am trying to create a database as
well).
2. We are using a vertical solution that used to have high level of
fragmentation. The fragmentation used to be so high that it used to increase
data device to 122+ GB with actual data of ~ 65+ GB. This forces me to
rebuild indexes and run the maintenance DBCC on every weekend. Since
upgrading to SQL 2000, this problem has reduced a lot. But, the maintenance
job timings since upgrade have also increased by 50% (it used to take ~ 8
hours and now the job is taking ~ 12 hours).
3. On at least two occasions (the latest on last Friday), the database has
generated exceedingly large transaction log backups. True, the application
system administrator has told me there was a runaway process that might have
created exceedingly large logs. But, the backups were so huge (+61 GB) that
it filled up the whole backup drive resulting in failures for other
transaction log backups till I cleaned the drive and took a full backup. The
normal hourly transaction log backups have total of size of 600+ MB (624 MB
as of now).
My question is: Am I seeing some kind of structural problems and has anyone
encountered similar problems?
Please share your experiences and expertise.
-- Regards, MZeeshan
- Next message: Fredrik Celin: "Sql Server 2000 Mulitlingual Best Practices (Collations and sorting)"
- Previous message: John Lantz: "understanding server trace statistics in query analyzer"
- Next in thread: Sophie Guo [MSFT]: "Is this some structural problem?"
- Reply: Sophie Guo [MSFT]: "Is this some structural problem?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
