You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2024. It is now read-only.
Exporting domain-users on MacOS results in broken file.
user is exported as DOMAIN\USERNAME.
On windows the "\" in the username is replaced with a space, but on Mac it's not replaced which leads to an apparent error where the file is either empty or broken.
Results:
Windows: DOMAIN USER.User.sql - Works and file has data!
Mac: DOMAIN\USER.user.sql - corrupted or empty file.
Is there an existing workaround for this?
The executing command is: mssql-scripter -U [user] -P [password] -S [server] -d [database] --file-per-object --object-permission --exclude-headers --display-progress --file-path [filepath]
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Exporting domain-users on MacOS results in broken file.
user is exported as DOMAIN\USERNAME.
On windows the "\" in the username is replaced with a space, but on Mac it's not replaced which leads to an apparent error where the file is either empty or broken.
Results:
Windows: DOMAIN USER.User.sql - Works and file has data!
Mac: DOMAIN\USER.user.sql - corrupted or empty file.
Is there an existing workaround for this?
The executing command is:
mssql-scripter -U [user] -P [password] -S [server] -d [database] --file-per-object --object-permission --exclude-headers --display-progress --file-path [filepath]
The text was updated successfully, but these errors were encountered: