Description
From feedback from a customer using SQL Server Functions and Stored Procedures implemented in C#:
Basically, would be good to have an API like the following:
.SaveModelToDb()
.LoadModelFromDb()
The reasons and scenarios are because you run C# code only as code running within SQL Server such as a C# SQL Server Function or a Stored Procedure that is scoring an ML.NET model while doing a query or transactions.
And not just for scoring but also for saving the model after training close to the database.. and since it is a table you could also have multiple model versions..
Another scenario would be for traditional client/server apps with the client apps directly accessing a database...
Doing it that way everything would be held, and more importantly, secured in the database server without external dependencies.