Very well put by Sarah. I've been very fortunate to have met many of my SQL heroes, either at local events, Tech-ed, PASS, or SQLBits. My first conference quite literally...

what's the size of the data you're transferring? I believe that there is a size limit on access 2k databases being 2gb

joint

can you post the output from sys.dm_db_index_physical_stats to give us more information to go on?

take a look at Ezequiel's blog

http://blogs.msdn.com/b/blogdoezequiel/archive/2011/05/24/sql-swiss-army-knife-9-vlfs-revisited.aspx

He's created an excellent script for dealing with large volumes of VLF's...

I concur with Robert that this should be raised with PSS...

Previously Kaushik posted on his blog the work-around for 2008, perhaps this will also work with 2012?

http://saveadba.blogspot.co.uk/2012/02/could-not-open-global-shared-memory-to.html

Just in case the obvious has been missed... The max server memory setting won't take effect until you restart the sql server instance. 🙂

I always find the forfiles command useful in these instances...

http://technet.microsoft.com/en-us/library/cc753551.aspx

I'm not using powershell; but use the agent on the associated SQL Server with SQL Server Analysis command option. It executes under the SQL Server Agent Service Account as default......