Report - developers who are not checking in their code regularly

I would like to create a report showing code that has been checked-out for longer than 2 weeks. I don't see this type of information contained in the BisDWDB, so I would assume I need to access the VSTeamSCC db instead. Is this correct? If so, what tables would I need to select?
[281 byte] By [JasonD.Camp] at [2007-12-16]
# 1

The VSTeamSCC database is not intended (or permissioned) to be queried directly.

Tell me a little bit more about what you're trying to accomplish and I'll see how hard it would be to get the required data exported to the warehouse.

Do you want code checked out in any (at least one) workspace or a specific workspace? (or both)
In one or more workspaces for a particular user?
Should items in shelvesets be considered checked out?
Checked out against the latest version or just checked out? (As in, if there's been a checkin to the item, does the clock restart?)

I'm not actually 100% sure that the time the file was checked out is recorded - I'll find that out first.

CRathjen-MSFT at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 2
I want to be able to run a report on all team projects and get a list of files that are still checked out and have been for over 2 weeks. (Currently we do this with vssreporter.) This lets us know two things: which developers are not checking in their code regularly (one of our development standards) and which files have been temporarily abandoned for higher priority work.

I do hope that check-out/in times are recorded in VSTF.

JasonD.Camp at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 3
So, that sounds like files checked out, per user, in at least one of their workspaces.

Given that shelving is intended to (among other things) allow code to be saved but not checked in, I'm still not sure how you'd want to account for files that aren't checked out but are in shelvesets.

I'll find out whether we record checkout time or not (we definitely record checkin time), and whether we can get this data exported to the warehouse or not if so. Stay tuned...

CRathjen-MSFT at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 4

Checkout time is what I am curious about.

JasonD.Camp at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 5
I don't know whether you can achieve this using the reports feature, but you can use the status command to get the information. If you run "h status $/ /r /user:* /format:detailed" you'll see every pending change in the system and when each change was pended (you need /format:detailed to get the date).

Buck

BuckHodges at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 6

I'm sorry - does this mean run this command from the (VS 2005) command prompt? "h" is not a valid command, nor is "status".

This is exactly what I was looking for, but how do you run it? (I'm running VS 2005 Team Developer)

Thanks,

John

Johnatcg.dna at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 7
Substitute "tf.exe" for "h.exe". When Buck wrote that post we hadn't removed codenames yet (Hatteras -> Team Foundation).
RichardBergMSFT at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...

Visual Studio Team System

Site Classified