Add script command to sql-cache tool

[glatzert]

Is your feature request related to a problem? Please describe.

I am trying to create the tables for distributed sql cache via the dotnet tool "sql-cache".
This works well, as long a I am developing and have full database access, but it's not working for scenarios, where I lack of access rights.

Describe the solution you'd like

Add dotnet sql-cache script, so the neccessary commands are written to the stdout and can easily be copied to an textfile.

[mkArtakMSFT]

@ajcvickers who is best positioned to handle this?

[ajcvickers]

@mkArtakMSFT Ownership of the SQL caching tool was transferred to @ericstj's team. I'll move this to dotnet/runtime.

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ericstj]

@ajcvickers we don't own this tool. I believe the tool still lives here and is owned and maintained by @Pilchie s team: https://github.com/dotnet/aspnetcore/tree/master/src/Tools/dotnet-sql-cache

[ajcvickers]

@mkArtakMSFT @Pilchie I thought this was part of Caching.SqlServer, but apparently it is not. It's not an EF thing, so I'm out of ideas.

[mkArtakMSFT]

@Tratcher, @pranavkm, @javiercn do you happen to know who owns this tool in our team?

[javiercn]

@JunTaoLuo maybe?

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[glatzert]

Btw, if you'd mark it up-for-grabs, I'd provide an implementation for
a) the script, which would be executed on SQL Server
b) an alternate script, which would create Statements for a memory optimized table

[Pilchie]

We don't (yet), have an up-for-grabs label, but I don't think we'd be against a contribution here. It's quite late for the .NET 5 release, so it's likely something that would end up in .NET 6 though.