http://sqlblog.com/blogs/linchi_shea/archive/tags/space+allocation/default.aspxTags: space allocationenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/linchi_shea/archive/2011/07/04/performance-impact-sqlbulkcopy-writetoserver-and-interesting-space-allocation-behavior.aspxTue, 05 Jul 2011 02:35:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:36626Linchi Shea2http://sqlblog.com/blogs/linchi_shea/comments/36626.aspxhttp://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=36626After reading Adam Machanic’s comment to my previous post , I started to wonder if what I saw was all due to the fact that SQL Server blindly chooses to allocate at least one extent in response to each call to WriteToServer(), perhaps in its zeal to achieve...(<a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/07/04/performance-impact-sqlbulkcopy-writetoserver-and-interesting-space-allocation-behavior.aspx">read more</a>)<img src="http://sqlblog.com/aggbug.aspx?PostID=36626" width="1" height="1">PerformanceData LoadSqlBulkCopyspace allocationhttp://sqlblog.com/blogs/linchi_shea/archive/2011/07/02/performance-impact-how-to-waste-time-and-space-with-sqlbulkcopy-writetoserver.aspxSun, 03 Jul 2011 02:00:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:36597Linchi Shea10http://sqlblog.com/blogs/linchi_shea/comments/36597.aspxhttp://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=36597If you have some time to kill, you could try to load a tiny amount of data, say ~3GB or 3,000,000 rows, with SqlBulkCopy, but do remember to give the WriteToServer method a very small payload every time it is called. The test results reported in my previous...(<a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/07/02/performance-impact-how-to-waste-time-and-space-with-sqlbulkcopy-writetoserver.aspx">read more</a>)<img src="http://sqlblog.com/aggbug.aspx?PostID=36597" width="1" height="1">PerformanceSqlBulkCopyspace allocationBulk load