go-sqlcmd icon indicating copy to clipboard operation
go-sqlcmd copied to clipboard

The new sqlcmd, CLI for SQL Server and Azure SQL (winget install sqlcmd / sqlcmd create mssql / sqlcmd open ads)

Results 128 go-sqlcmd issues
Sort by recently updated
recently updated
newest added

The credentials stored for a sql container are being persisted in ADS and not overwritten when a new container is created. This causes a login failure in ADS and forces...

bug
ADS
Security

Imagine a sample that tries to setup a developer’s environment with one, two, or three different containers – only one is SQL. Docker commands are enough, but sqlcmd is easier...

enhancement
Security

If there are any switches left from the old ODBC sqlcmd that are not yet implemented in the new go-sqlcmd, please put in a stub implementation for go-sqlcmd now, which...

enhancement
sqlcmd switch

If a sql text file is encoded as ANSI (as opposed to UTF-8 or similar) the newer Go version of sqlcmd will not correctly parse non-ASCII characters. For example, if...

bug
Localization

As the title says, Secure Enclaves with Azure Databases appears to be unsupported at this time. It would be a great benefit to support Secure Enclaves for sqlcmd queries for...

enhancement
Security

Sometimes in a script you want to clean up an environment before running. **_sqlcmd delete --remove-all_** would be helpful for bat scripts. **_sqlcmd delete --context-only_** would be useful for environments...

enhancement

Will go-sqlcmd support LocalDB connections on Windows? (Basically the equivalent to `sqlcmd -S (localdb)\MSSQLLocalDB -E`.) On Windows I get the following error with the latest go-sqlcmd 1.4.0: "no named pipe...

bug
connectivity

Implement support for the docker -v flag in SQLCMD container management. Being able to attach a volume on creation and later delete the container, deleting the volume only with --force...

enhancement

When running with Podman in a rootless environment, the daemon configuration can get tricky. If we have a daemon failure and are able to somehow detect they are running podman...

bug
documentation

Rename the --name flag to --container-name to make it clearer to read and eliminate confusion from it being right next to --host-name. Keep --name as an alias to --container-name so...

documentation
enhancement