Shamil Salakhetdinov
shamil at smsconsulting.spb.ru
Mon Sep 21 08:44:14 CDT 2009
Hi John and Stuart, I do not plan to keep production and large test databases on my VPC therefore virtual HDD expanding feature would be useful here. --Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Monday, September 21, 2009 4:58 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] OT: Virtual PC 2007 (MS), CITRIX XenServer, CITRIX HDX... Stuart, You are correct, you can set the VM up to expand as necessary. The advantage is that it can start small and get really big if needed. The disadvantage is that it is slow when expanding. Once expanded though it remains that size until it needs to expand again. If you set up a fixed size, it is always as fast as it will ever be but be unable to grow if need be. I set up mine as a fixed size, because my machines were performing a specific job and I knew what I needed. John W. Colby www.ColbyConsulting.com Stuart McLachlan wrote: > VirtualBox can either allocate all the required disk space when you first set up a VM or > expand the image when required. > > I made the mistake of doing the first and then trying to benchmark building big tables in > Access in the VM. It turned out to be very slow. Creating the full sized disk up front > resulted in much better results. > > I suspect that VMWare and VPC will be the same. > > So if you are using the VM to create large record sets, it will certainly pay to allocate the full > space initially. > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4442 (20090921) __________ The message was checked by ESET NOD32 Antivirus. http://www.esetnod32.ru