You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@guacamole.apache.org by necouchman <gi...@git.apache.org> on 2017/10/24 14:41:44 UTC
[GitHub] incubator-guacamole-manual pull request #61: GUACAMOLE-363: Documentation fo...
GitHub user necouchman opened a pull request:
https://github.com/apache/incubator-guacamole-manual/pull/61
GUACAMOLE-363: Documentation for SQL Server JDBC module.
Updated the jdbc-auth.xml page to include SQL Server/TDS-specific options.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/necouchman/incubator-guacamole-manual GUACAMOLE-363
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-guacamole-manual/pull/61.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #61
----
commit de0311d1f244c377ae5a5bb5d5c255e91c81026c
Author: Nick Couchman <vn...@apache.org>
Date: 2017-10-24T14:41:05Z
GUACAMOLE-363: Documentation for SQL Server JDBC module.
----
---
[GitHub] incubator-guacamole-manual pull request #61: GUACAMOLE-363: Documentation fo...
Posted by mike-jumper <gi...@git.apache.org>.
Github user mike-jumper commented on a diff in the pull request:
https://github.com/apache/incubator-guacamole-manual/pull/61#discussion_r153056442
--- Diff: src/chapters/jdbc-auth.xml ---
@@ -299,6 +321,59 @@ Type "help" for help.
to run any database upgrade scripts.</para>
</important>
</section>
+ <section xml:id="jdbc-auth-sqlserver">
+ <title>SQL Server</title>
+ <para>If using SQL Server, the database and schema must be created first. The example below assumes
+ that you are running SQL Server on Linux, using the command-line tools to manage it.</para>
+ <informalexample>
+ <screen><prompt>$</prompt> <userinput>/opt/mssql-tools/bin/sqlcmd -S localhost -U SA</userinput>
+<prompt>Password:</prompt> <userinput><replaceable>password</replaceable></userinput>
+<prompt>1></prompt> <userinput>CREATE DATABASE <replaceable>guacamole_db</replaceable>;</userinput>
+<prompt>2></prompt> <userinput>GO</userinput>
+<prompt>1></prompt> <userinput>CREATE LOGIN <replaceable>guacamole_user</replaceable> WITH PASSWORD = '<replaceable>S0me_Password</replaceable>';</userinput>
+<prompt>2></prompt> <userinput>GO</userinput>
+<prompt>1></prompt> <userinput>USE <replaceable>guacamole_db</replaceable>;</userinput>
+<prompt>2></prompt> <userinput>GO</userinput>
+<prompt>1></prompt> <userinput>CREATE USER <replaceable>guacamole_user</replaceable>;</userinput>
+<prompt>2></prompt> <userinput>GO</userinput>
+<prompt>1></prompt> <userinput>ALTER ROLE db_owner ADD MEMBER <replaceable>guacamole_user</replaceable>;</userinput>
--- End diff --
Would this result in `guacamole_user` having all privileges on the database, not just `SELECT`, `INSERT`, `UPDATE`, and `DELETE` on the tables within `guacamole_db`?
---