Time for another episode of the SQL Friday, The Best SQL Server Links Of The Past Week show.
Here is what I found interesting this past week in SQL Land:

Is CHECKDB A Necessity?
I’m often asked by professionals whether CheckDB is still recommended on SQL2k8. SQL is calculating a checksum to avoid physical page corruption since 2k5. However in my experience (starting with SQL 7.0) I’ve never been able to clearly say that CheckDB is not necessary .. Does anyone have a good advice? Read the post to find out the answer

Run-time Execution Plan Options
Joe Chang made a post and hes sks “What are the top core SQL Server engine performance issues today, after all the improvements that have gone into 2005 and 2008? (I am excluding matters beyond the power of Microsoft, like eliminating bad developers.)”

Enabling Data Compression By Default in a SQL Server 2008 Database
Aaron Alton show us how you could have every table in your database have data compression on by default. Of course he also warns you that this is not necessarily a good thing

SQL in the Cloud and SQL Server In The Cloud Vaporware Or Inevitable?
Two links dealing with SQL Server in the cloud and if it will happen, see also our poll here: Poll: Your Database in The Cloud?

Always Test Your Assertions – Calendar Tables vs. Table Valued Functions
Aaron Alton shows us performance differences between Calendar Tables and Table Valued Functions

And this week we have a bonus link, it is not SQL Server but MySQL, a very interesting post

How FriendFeed uses MySQL to store schema-less data
Bret Taylor writes: We use MySQL for storing all of the data in FriendFeed. Our database has grown a lot as our user base has grown. We now store over 250 million entries and a bunch of other data, from comments and “likes” to friend lists.

As our database has grown, we have tried to iteratively deal with the scaling issues that come with rapid growth. We did the typical things, like using read slaves and memcache to increase read throughput and sharding our database to improve write throughput. However, as we grew, scaling our existing features to accomodate more traffic turned out to be much less of an issue than adding new features.

That is it for this week, I will tag the weekly posts with SQL Friday in case you want to see the whole archive in the future

*** If you have a SQL related question try our Microsoft SQL Server Programming forum or our Microsoft SQL Server Admin forum