I think, for the time being, we're looking into calling that Builds_PromoteBuild Stored Proc. It was good to have you verify it, for us.
our current issue:
using the stored proc Builds_PromoteBuild as is, we've been encountering errors running it through SQL Server Management Studio, and it's related to not having a populated User Name. The DB function Session_GetUserName is supposed to do this for us, but we're not sure where that function's "CONTEXT_INFO()" is coming from, and we're not sure if we'll have that in the application we'll be using to launch the stored proc.
I'm not entirely sure how to address this, but we do know setting the '[PromotedBy_Name]' as something with an edited version of the proc works fine. We just didn't think it would be kosher to make that our solution.