Solved! Go to Solution.
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
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.
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?