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

### Discussed in https://github.com/microsoft/go-sqlcmd/discussions/206 Originally posted by **0x7FFFFFFFFFFFFFFF** February 2, 2023 Right now, both `sqlcmd` and `go-sqlcmd` don't allow you to specify `-q` and `-i` options together. Below is the...

enhancement
sqlcmd switch

Cobra provides the ability to group flags, if so we should probably group them, top group being the very commonly used one, then a group on authenication flags etc.  Possible...

enhancement
sqlcmd switch

nit: there is a captial O in the flag --login-timeOut (this is a change from previous build) Also with --login-timeout, we set the default to -1, but then say in...

bug
sqlcmd switch

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...

enhancement
sqlcmd switch
spec

# Passing Passwords Insecurely After typing 'export SQLCMDPASSWORD=...', the environment variable is visible to all child processes (any command and background process started by the shell). When creating a user...

bug
sqlcmd switch
Security

I had two contexts set up, and when I tried this code, I got an error: sqlcmd stop mssql2 I would expect to be able to specify a context and...

enhancement
sqlcmd switch

It would be create if sqlcmd could support the creation of database users/logins. For example, something like ``` sqlcmd user add -u Davide -p ``` for adding a SQL user...

enhancement
sqlcmd switch

As a follow up to #299 we should add functional tests for scenarios such as verifying that all types of public and SAS URLs work well for specifying .bak files

enhancement
sqlcmd switch
testing

Viper automatically reflects SET SQLCMD_ env vars into the sqlconfig file. So when a user SET SQLCMD_EULA, accept_eula is getting persisted into the sqlconfig file. I don't think it is...

bug

Queries that have user input should be executed with parametrized queries and should possibly use sp_executesql

enhancement
Security