Updating the Data API Builder

September 2, 2026

·

I was updating my session for the Data API Builder (DAB) recently, mostly to work with the MCP server capabilities. As I was trying to get this working, I realized that the MCP capabilities were newer than my DAB version. I had v1.4

Wow, that’s old. The Overview page for the SQL Server MCP site says v1.7 is needed and 2.0+ has bug fixes. I need an update.

I had this in my slide deck, but the dotnet tool is used to update the DAB. The command is

dotnet tool update –-global Microsoft.DataApiBuilder

This showed a download and then in a few minutes it was done. I could see I had an updated version.

And an MCP server!

A Further Update

I checked a few weeks later and couldn’t remember the command, but I decided to try the install command. That worked as well, and I got an even newer, 2.0.12, version.

Still no timestamps from the logs, but I’m every hopeful.

DAB syndicated

Currently Reading

Reshuffle — My current business book recommended by our CEO

Comments

4 responses to “Updating the Data API Builder”

September 9, 2026

Rolph

For me the –global option needed to be behind te packageId to work, like this:
dotnet tool update Microsoft.DataApiBuilder –global

LikeLike

Reply
September 9, 2026

Rolph

oops… like this: dotnet tool update Microsoft.DataApiBuilder –global

LikeLike

Reply
September 9, 2026

Rolph

Mmm… your comment tool removes double dashes, so writing them before global doesn’t work.
There need to be two dashes before global in my case

LikeLike

Reply
1. September 9, 2026
  
  way0utwest
  
  Thanks, yeah most tools use double dashes if the parameter is more than one char. I’ve corrected it.
  
  LikeLike