Skip to content

Provide ability to direct restore a URL (with a CREDENTIAL) instead of copying to container first  #332

New issue
New issue
Open
Open
Provide ability to direct restore a URL (with a CREDENTIAL) instead of copying to container first #332
Labels
enhancementNew feature or requestspecWould require a spec be writtensqlcmd switchswitch in existing sqlcmd
Milestone
Backlog
@stuartpa

Description

@stuartpa
stuartpa
opened on Apr 27, 2023
Collaborator

Right now the sqlcmd use functionality copies the file to the container, and then before the action to restore/attach etc.

This comment in a code review suggests we enable the ability to restore the URL directly from the sqlservr process in the container (avoiding the need for the copy to container)

"for .bak files using a URL we should provide a way to create a CREDENTIAL to store on the server so it can restore directly from the URL.
SQL 2022 supports both https and s3 URLs"

Activity

grrlgeek
added
enhancementNew feature or request
on May 3, 2023
grrlgeek
added this to the Backlog milestone on May 3, 2023
dlevy-msft
modified the milestones: Backlog, October 2023 on Aug 3, 2023
dlevy-msft
added
sqlcmd switchswitch in existing sqlcmd
specWould require a spec be written
on Aug 11, 2023
dlevy-msft
modified the milestones: October 2023, Backlog on Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestspecWould require a spec be writtensqlcmd switchswitch in existing sqlcmd

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @stuartpa@grrlgeek@dlevy-msft

        Issue actions
          Provide ability to direct restore a URL (with a CREDENTIAL) instead of copying to container first · Issue #332 · microsoft/go-sqlcmd