As you probably know by now, we intend to support versioning even very large files in Team System. Last I checked, I believe the only hard limit was a question of how big your database's hard disk is.
We've had to fix a few issues (and had to get ASP.Net and SQL 2005 to fix a few issues) along the way. One of those fixes lets the Source Control Proxy download very large files faster than it used to (and using less memory in the process, as well) - the difference with a 2GB+ file was rather dramatic.
So, I'm curious. We've gotten data from a few folks on how big their versioned data is "in total" - as in, how much space the whole repository needs, or how much space the latest version of everything represents. But, how big do individual files get for you? What kinds of files are those? I know we've checked in some big crash dumps before, and zips of large collections of files. What other sorts of "big data" do you find yourself want to keep around/version/track history of?
In dreams I see myself flying...