September 29, 2010 at 11:54 am
Hi,
We have 2 servers Server A and Server B with SQL Server 2005 EE SP3.
On Server A, We have a Share Point Content database of size 60 GB and when I perform Weekly Index De-fragmentation (Avg.Index Fragmentation%<30-> Index Reorganize and >30-->Index Rebuild) and after the Index De-fragmentation task, the next log backup is generating 700 MB log backup file.
On Server A, We have a in house database of size 25 GB and when I perform Weekly Index De-fragmentation (Avg.Index Fragmentation<30-> Index Reorganize and >30-->Index Rebuild) and after the Index De-fragmentation task, the next log backup is generating 22 GB log backup file almost equal to the database size.
So I'm wondering why a 60 GB database is generating only 700 MB log backup file and 25 GB database is generating 22 GB log backup file after Index defrag?
What factors decides the log generation while performing Index reorg/rebuild? Basically, I'm looking for the ways to reduce the HUGE log backup file size (22 GB) generating for the 25 GB database.Because its involved in Log shipping configuration and the 22 GB log file is taking 15 Hrs to copy to secondary location which is NOT feasible.
Please provide your inputs
September 29, 2010 at 12:03 pm
Sharepoint is more a reporting tool than a real oltp system.
It's a fair bet that you are reindexing 90% of the index in server b and only 5-10% in server A.
Maybe you should run the defrad manually on fridays but only printing what is being done, I'm sure you'll see how little needs to be done on your sharepoint server.
September 29, 2010 at 12:04 pm
Oh and there's no deciding point... if the page is modified in any way, then it HAS to be logged.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply