Yesterday, Microsoft released a tool to migrate from IBM ClearCase to TFS.

Find more information on TFS migration topics, keep an eye on this blog.

Microsoft has published a detailed KB article about the problems fixed by SR1. The article includes a link to download the update.

Aside from many fixes, there are three major improvements found in this release:

• Cross-database references - support is improved so that you can reference objects within different databases by using database project references or by referencing a database metafile (.dbmeta). This support reduces or eliminates the cross-database reference warnings within a database project
• Improved file support within SQL Server file groups - you can define files within file groups as database project properties instead of having to create files and file groups within the pre-deployment storage script.
• Variables - a Variables page is added to the database properties. This new page enables you to define setvar variables for use in the deployment scripts.

Over the past few years, a few of my clients have deployed Team Foundation Server Proxy to improve the performance of their remote/distributed teams. It boosts network performance by caching copies of source control files in a remote location, local to the developer needing the files but away from the main source control location. In short, the proxy helps each user avoid a costly download of the files to their workspace across the slower connection.

So why wouldn't this work for Team Build?

In today's VSTS chat, I asked if anyone had done this. I should have expected that Buck Hodges would have, and even blogged about it.

Microsoft just released their Team System Web Access Power Tool (formerly known as TeamPlain). This is a Web interface to Team Foundation Server.

If you have team members that don't want Visual Studio/Team Explorer installed on their desktop, but they still want to participate with the project lifecycle, this is a great, web-based approach to getting everyone connected quickly/easily. Here are some of the features:

• Add new work items or edit existing ones
• Work with any type of work item, including custom ones
• Add new work item queries or edit existing ones
• View, download, upload, check-in and check-out documents on SharePoint team portal
• View reports, export as PDF or Excel
• Browse source control repositories, download files, view changesets, diffs, histories, and annotated views
• View build results, start or stop builds
• Search for keywords in work items
• Authentication Modes: Integrated Windows Authentication or Forms Based Authentication (Recommended to use with SSL)

Read more about it in Brian Harry's blog posting.

Ok, I finally got fed up with all of the spam in my historical dasBlog postings. It's really embarrassing to send a link to a a colleague, only to have them snicker at all of the spam comments and trackbacks.

For those of you who don't know what a trackback is, it's basically an acknowledgement that enables authors to keep track of who is linking to, or referring to their articles. When used properly, trackbacks form a communication link between the two blogs, so that new comments on one blog can basically ping the other, allowing readers to easily follow discussions on both. The problem is that spammers have abused this mechanism and bloggers end up with trackbacks and pingbacks to various gambling, herbal medication, and adult sites.

Earlier this year I joined the ranks, and disabled my trackback and pingback services in dasBlog. I then followed Scott Hanselman's advice on using Akismet spam blocking service.

The big effort was then how to cleanup the <Comment> and <Trackback> elements that were spam, so, like others before me, I built a tool to assist with this.

1. Download ScrubDasBlog.zip or ScrubDasBlogSource.zip to your hard drive
2. Edit the blacklist.txt to include your own blacklisted URLs *
3. Backup your existing feedback files: \content\*.dayentry.xml
4. Run the ScrubDasBlog utility, specifying the path to your \content folder and the path to your blacklist.txt file, for example:

scrubdasblog c:\inetpub\wwwroot\mydasblog\content c:\scrubdasblog\blacklist.txt

* If you have predominately more SPAM comments and trackbacks in your dasBlog history, then you can generate a starter blacklist by going into your \content sub-folder and typing the following:

type *.xml | find "AuthorHomepage" > blacklist.txt

After you generate the blacklist.txt file, you should remove any good sites and remove any duplicates, before running the ScrubDasBlog utility.

I would recommend downloading the Source code version and reading through my code. Please comment on any improvements you might make.

I saw a demo of these at Tech-Ed, and thought I would share with my friends.

Essentially, the Database Operations team at Microsoft uses a suite of jobs on all their servers for performing backups, automated database maintenance, improve performance , and improving disaster recovery. I'm sure every SQL Server expert/consultant out there has his or her own bag of tricks, but Microsoft is finally sharing theirs.

These SQL maintenance jobs provide automated tasks such as database or transaction logs backup, performing database optimization like Index defrag or update statistics, cleaning MSDB backup history and recycling the SQL error log. Each of these jobs runs stored procedures that are installed when the jobs are created.

The following are the jobs get installed with this package.

• SQLBackupAll
• SQLBackupDiffAll
• SQLBackupTranAll
• SQLBackupChecker
• SQLDBCCAll
• SQLIndexDefragAll
• SQLUpdateStatistics
• SQLCleanupMsdbBackupHistory
• SQLCycleErrorLog

Download the automation jobs here, and then refer to the Word document inside.

Today's chat was well attended, with many experts and well over a hundred guests. The quests came fast and furious, with some great answers given by the experts. It seems people are really anticipating Orcas (and Rosario) for those features that didn't make it into v1.

I have captured the entire transcript (both expert and guest chats) in this PDF document.

Note: this is the raw content, copied and pasted from the chat, so you are getting it "as is".