templates and eager zeroed disk

[Buck1967]

I'm working on a template for a SQL server. Using the best practices I would eager-zero the disk. I'd have a 400G template if I build it out like our basic physical SQL server:

I was think of create eager-zeroed virtual disks and follow MS's best practice with formatting NTFS with a 64kb Cluster size. If I create smaller disk and grow them larger, does that negate the eager-zero that I did. Anyone else tring to create templates for an optimized SQL configuration?

Standard Drive Letters and Functions for MSSQL  (Physical)

Drive Letter	Qtree	Type	Description	Size
C: (SAN BOOT/LOCAL)	SQLROOT	LUN	SQL Installation	40GB
M:	SQLDATA	LUN	Database Files	200GB
N:	SQLLOGS	LUN	Transaction Logs/Index/Full Txt Catalogs	100GB
O:	SQLTEMPDB	LUN	SQL TempDB	50GB
P:	SNAPINFO	LUN	SMSQL SnapInfo (NetApp backups)	25GB

If I create my SQL template with smaller drives (say 20G) and grow them larger, are they still going to have the benefit of the eager-zeroed?

Any suggestions welcomed.

[raj196]

Hi

but its 90% related to SQL , so i am suggesting you put this post in vmware developers  .

________________________________
If at first you don't succeed, skydiving is not for you

[Buck1967]

This has nothing to do with SQL other than my scenario uses it. The question is basically can you maintain an eager zeroed disk when using a template?