7pace Timetracker是否会更新TFS2017数据库？

Great question—let’s break this down clearly:

Core Behavior: 7pace doesn’t directly modify the TFS database by default #

7pace Timetracker is designed to keep its time-tracking data separate from TFS’s native database (which is why you see the dbo.WorkLog table in its own dedicated database, with the PeriodLength field storing actual logged hours). This is intentional: it avoids risking TFS stability by not altering Microsoft’s supported database schema, and keeps third-party time data isolated.

That’s exactly why you don’t see those logged hours in the default TFS interface—TFS’s native tools don’t read data from 7pace’s independent storage.

When might 7pace interact with TFS data? #

While it won’t directly write to TFS database tables, 7pace can sync time data to TFS via the official TFS API if you configure it to do so. For example:

• You can set up 7pace to push logged hours to TFS’s native work item fields like Completed Work or Remaining Work
• This sync happens through TFS’s supported API endpoints, not direct database writes (which is critical for maintaining TFS supportability)

Generating your estimate vs actual time report #

Since you’re looking to build an estimate vs actual report, you have two solid options:

1. Use 7pace’s built-in reporting tools: It can natively pull estimate data from TFS work items (like your original estimate fields) and combine it with its own PeriodLength actual hours to generate pre-built or custom comparison reports.
2. Build a custom report: Connect both the TFS database (to pull estimate values) and 7pace’s database (to fetch dbo.WorkLog entries) in a reporting tool (like SSRS, Power BI), then link the data via work item IDs to create your own tailored report.

内容的提问来源于stack exchange，提问作者Bill Greer