11-25-2009 08:58 AM
Solved! Go to Solution.
12-10-2009 04:54 AM
11-25-2009 11:18 AM
11-25-2009 12:11 PM
11-25-2009 04:38 PM
SELECT cc = count (*), ii = sum (itemsize/1024), jj = sum (itemsize/1024)/count (*) INTO #temptable FROM saveset GROUP BY iddatetime,idchecksumhigh,iduniqueno,idchecksumlow ORDER BY cc DESC SELECT "Total files archived" = sum(cc), "Number of files after sharing" = count (CC), "Total size before sharing" = sum (ii), "Total size after sharing" = sum (jj), "Estimated size after archiving" = sum (jj) + (count (*)*5) + (sum (cc)*2) FROM #temptable DROP TABLE #temptable
11-26-2009 03:09 AM
11-26-2009 04:42 AM
11-26-2009 05:41 AM
11-26-2009 07:24 AM
11-26-2009 09:10 AM
11-26-2009 09:16 AM
11-26-2009 12:00 PM
11-26-2009 12:31 PM
11-26-2009 12:40 PM
Thanks Wayne.
I'll also try to get some figures from other implementations to see how they correspond and match the 3,8,12 percent guideline.
If others have had the strength to read all the way to this post I'd appreciate som reference data.
Thanks again,
/Tobbe
12-10-2009 02:01 AM
Hi again.
Now I have more reference number from three other implementations but they don't make me any wiser. All of these implementations are, and have been running Full Indexing from start but the resulting size varies greatly.
Implementation 1: Index size is 6.5% of Vaultstorage
Implementation 2: Index size is 5.8% of Vaultstorage
Implementation 3: Index size is 15% of Vaultstorage
This makes future capacity planning...hmmm..fuzzy?
12-10-2009 04:54 AM
12-11-2009 01:28 AM
Thanks Liam.
It nice to have more references that indicates that full indexing can generate such low ratio as 3%.