No anchor member was specified for recursive query Problem

Recently I've been playing around with Common Table Expressions (CTE) and I've had a little difficulty figuring out exactly what the syntax is for it.
The main problem I was having was figuring out how the recursive member integrates with the CTE table. I kept getting the following error.

No anchor member was specified for recursive query "MemberRelation".

After a few hours of troubleshooting I realized that I didnt fully understand what the first line of code for the CTE was doing. In actuality, it is describing the table layout of the result set. (Not a table in the database.) Now the expression is working and making sense:

with MyRelation
(
ID1,
ID2,
Level
)
as
(
-- Anchor member definition
select ID1
,ID2
,0 as Level
from relation as e
UNION ALL
-- Recursive member definition
select e.ID1
,e.ID2
,Level + 1
from relation as e
join MyRelation R on R.ID2 = e.ID1
)
-- Statement that executes the CTE
select top 1 * from MyRelation
where Level = 3
option(Maxrecursion 3)
GO

TFS - Getting files that have changed since a particular date

One of the most annoying parts of source control in visual studio is the lack of some basic features that are in other source control systems. One such feature is to get files that have changed since a particular date. You can do this in TFS, but it isnt straightforward.

Here is how you do it:

1. Create a new folder on your local hard drive to be used temporarily.

2. In visual studio, create a new workspace mapping the directory in source control you want to get the changes on, to the folder created in step 1 above.

3. Under source control, right-click on the folder and select "Get Specific Version..." on the directory that you want to get the changes on.

4. From the Version checkbox, choose "Changeset" and enter the changeset that has the files without the changes you are retrieving.

5. Click Get to get all the files.

6. Once complete, go to the directory on your local hard drive (created in step 1) and delete all the files you just retrieved.

7. Under source control, right-click on the folder you wish to get the changes on and select "Get Latest Version"

After all the files are done downloading, your local folder will only have files that have changed since you last retrieved the files in step 3. Why? - "Get Latest Version" doesnt actually look at the files on your local machine to determine what files need to be updated. Instead, it keeps track of the files you downloaded on the server and gets any changes from your previous download.

GenerateAndPersistNewIndex causing "Not enough storage is available" error

Here is a good “gotcha” for the GenerateAndPersistNewIndex setting in the Fuzzy Lookup component delivered with SSIS and SQL 2005.

Problem: MaxMemoryUsage set to 0 (Unlimited) - When this is set to 0, and the MatchIndexOpetion set to GenerateAndPersistNewIndex, the package will fail stating: "Not enough storage is available to complete this operation"

Fix: Set MaxMemoryUsage to 256

There are a few things really odd things that I've discovered:

· The description of MaxMemoryUsage from MS says it applies to the transformation process, not the index creation process.

· With MaxMemoryUsage set to 0 and plenty of RAM, the package may still fail even though it isnt close to maxing out the RAM.

· Even with MaxMemoryUsage set to 256, it is going past this memory requirement. (although I can see it is using a lot less memory than with a setting of 0)