Opinions on sizing of SQL databases in EV10
Just reviewing the SQL best practive guide - which I do from time to time :o)
And looking at the very comprehensive and somewhat complex formula's on calculating the disk size requirement for each database.
My question is really - 'Does anyone realistically utilise these calculations when designing an EV solution?' or is it more the case of 'Let's create a, say 250GB, volume on fast disk for everything and keep an eye on it' - obviously separating Logs and Dbs onto different spindles.....
So effectively base it less on the maths but more on the features (FSA, Email\Journal archiving, Sharepoint etc) and number of users (<1000, 1000 - 5000, >5000) etc
And which DB's should always exist separate from each other regardless of environment size etc
I'd be interested if anyone has any rules of thumb that they have found successful which requires less intial metrics than the best practice guide suggests.