This is totally awesome! As if I weren't already excited about SQL Server 2005! ;)
One of my all time favorite games (played the original a ton back in college on my PII-233Mhz machine [all 3 semesters of it :P]) just came out on XBox and I had to post it...if anybody else is going to get this game, let me know...Gamer Tag: HumanCompiler
Worms 3D
So I finally got around to installing Beta 2 of SQL2K5 (it's about time, been so busy with work). I open up management studio and go to create a new database so I can start playing. By the way, I'd recommend you install it and get to playing. As the betas evolve, SQL Server is starting to get REALLY cool. There are lots of goodies to make it all easier for you all over the place. Anywho, so I create a new Database and then create a new Table and I noticed an interesting property for the table. Text/Image Filegroup
First off, I am a huge believer in storing images, documents, files of any sort in the DB. I haven't actually done it much yet because performance is sometimes a problem. My limited understanding of the performance problem is that storing huge amounts of data like a big binary chunk splits up data pages when it normally would've have been necessary. So I'm wondering if splitting off the binary data (anything big really) onto a separate file group will help with the performance and storage. Regardless if it will help or not, at some point I'm just going to start doing it anyway, because in 5 years, everything we're always soooo worried about from a performance standpoint almost always ends up not being an issue anymore.
Thoughts? Opinions? Religious battles? I'm curious about the subject and what everybody thinks...