- DBeaver-Driver-AllDBeaver-Driver-All ( DBeaver驱动包 )整合所有DBeaver的JDBC驱动包，供DBeaver使用，无需每次都搜索和下载，只需clone本项目即可，一个包包含几乎所有的驱动，如果有缺漏的驱动欢迎提Issue补充。DBeaver-Driver-All, a DBeaver JDBC Driver Package, contains all jdbc drivers for dbeaver,no need to download it ev.
- DBeaver 是一个通用的数据库管理工具和 SQL 客户端，支持 MySQL, PostgreSQL, Oracle, DB2, MSSQL, Sybase, Mimer, HSQLDB, Derby, 以及其他兼容 JDBC 的数据库。DBeaver 提供一个图形界面用来查看数据库结构、执行SQL查询和脚本，浏览和导出数据，处理BLOB/CLOB 数据，修改数据库结构等等。.
This section provides quickstart instructions for making a simple connection to a SQL Server database by using the Microsoft JDBC Driver for SQL Server. Before you connect to a SQL Server database, SQL Server must first be installed on either your local computer or a server, and the JDBC driver must be installed on your local computer.
DBeaver社区版(可视化数据库管理工具) v7.2.2 64位 免费绿色解压版,Beaver是一个免费和开源（GPL）为开发人员和数据库管理员通用数据库工具和SQL客户端，免费、跨平台、基于开源框架和允许各种扩展写作（插件），欢迎下载使用. The Update table1 set (a,b,c) = (select x,y,x) syntax is an example of the use of row-value constructors, Oracle supports this, MSSQL does not. ( Connect item ) Share.
Choosing the right JAR file
The Microsoft JDBC Driver provides different Jars to be used in correspondence with your preferred Java Runtime Environment (JRE) settings, as under:
Dbeaver Mssql Driver Download
The Microsoft JDBC Driver 9.2 for SQL Server provides mssql-jdbc-9.2.1.jre8.jar, mssql-jdbc-9.2.1.jre11.jar, and mssql-jdbc-9.2.1.jre15.jar class library files.
The Microsoft JDBC Driver 8.4 for SQL Server provides mssql-jdbc-8.4.1.jre8.jar, mssql-jdbc-8.4.1.jre11.jar, and mssql-jdbc-8.4.1.jre14.jar class library files.
The Microsoft JDBC Driver 8.2 for SQL Server provides mssql-jdbc-8.2.2.jre8.jar, mssql-jdbc-8.2.2.jre11.jar, and mssql-jdbc-8.2.2.jre13.jar class library files.
The Microsoft JDBC Driver 7.4 for SQL Server provides mssql-jdbc-7.4.1.jre8.jar, mssql-jdbc-7.4.1.jre11.jar, and mssql-jdbc-7.4.1.jre12.jar class library files.
The Microsoft JDBC Driver 7.2 for SQL Server provides mssql-jdbc-7.2.2.jre8.jar, and mssql-jdbc-7.2.2.jre11.jar class library files.
The Microsoft JDBC Driver 7.0 for SQL Server provides mssql-jdbc-7.0.0.jre8.jar, and mssql-jdbc-7.0.0.jre10.jar class library files.
The Microsoft JDBC Driver 6.4 for SQL Server provides mssql-jdbc-6.4.0.jre7.jar, mssql-jdbc-6.4.0.jre8.jar, and mssql-jdbc-6.4.0.jre9.jar class library files.
The Microsoft JDBC Driver 6.2 for SQL Server provides mssql-jdbc-6.2.2.jre7.jar, and mssql-jdbc-6.2.2.jre8.jar class library files.
The Microsoft JDBC Drivers 6.0 and 4.2 for SQL Server provide sqljdbc41.jar, and sqljdbc42.jar class library files.
The Microsoft JDBC Driver 4.1 for SQL Server provides the sqljdbc41.jar class library file.
Your choice will also determine available features. For more information about which JAR file to choose, see System requirements for the JDBC driver.
Dbeaver Mssql Create User
Setting the classpath
The Microsoft JDBC driver jars are not part of the Java SDK and must be included in Classpath of user application.
If using JDBC Driver 4.1 or 4.2, set the classpath to include sqljdbc41.jar or sqljdbc42.jar file from respective driver download.
If using JDBC Driver 6.2, set the classpath to include the mssql-jdbc-6.2.2.jre7.jar or mssql-jdbc-6.2.2.jre8.jar.
If using JDBC Driver 6.4, set the classpath to include the mssql-jdbc-6.4.0.jre7.jar, mssql-jdbc-6.4.0.jre8.jar, or mssql-jdbc-6.4.0.jre9.jar.
If using JDBC Driver 7.0, set the classpath to include the mssql-jdbc-7.0.0.jre8.jar or mssql-jdbc-7.0.0.jre10.jar.
If using JDBC Driver 7.2, set the classpath to include the mssql-jdbc-7.2.2.jre8.jar or mssql-jdbc-7.2.2.jre11.jar.
If using JDBC Driver 7.4, set the classpath to include the mssql-jdbc-7.4.1.jre8.jar, mssql-jdbc-7.4.1.jre11.jar, or mssql-jdbc-7.4.1.jre12.jar.
If using JDBC Driver 8.2, set the classpath to include the mssql-jdbc-8.2.2.jre8.jar, mssql-jdbc-8.2.2.jre11.jar, or mssql-jdbc-8.2.2.jre13.jar.
If using JDBC Driver 8.4, set the classpath to include the mssql-jdbc-8.4.1.jre8.jar, mssql-jdbc-8.4.1.jre11.jar, or mssql-jdbc-8.4.1.jre14.jar.
If using JDBC Driver 9.2, set the classpath to include the mssql-jdbc-9.2.1.jre8.jar, mssql-jdbc-9.2.1.jre11.jar, or mssql-jdbc-9.2.1.jre15.jar.
If the classpath is missing an entry for the right Jar file, an application will throw the common Class not found exception.
For Microsoft JDBC Driver 9.2
The mssql-jdbc-9.2.1.jre8.jar, mssql-jdbc-9.2.1.jre11.jar, or mssql-jdbc-9.2.1.jre15.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 9.2 for SQL Serversqljdbc_9.2enumssql-jdbc-9.2.1.jre11.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_9.2/enu/mssql-jdbc-9.2.1.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-9.2.1.jre8.jar, mssql-jdbc-9.2.1.jre11.jar, or mssql-jdbc-9.2.1.jre15.jar.
For Microsoft JDBC Driver 8.4
The mssql-jdbc-8.4.1.jre8.jar, mssql-jdbc-8.4.1.jre11.jar, or mssql-jdbc-8.4.1.jre14.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 8.4 for SQL Serversqljdbc_8.4enumssql-jdbc-8.4.1.jre11.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_8.4/enu/mssql-jdbc-8.4.1.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-8.4.1.jre8.jar, mssql-jdbc-8.4.1.jre11.jar, or mssql-jdbc-8.4.1.jre14.jar.
For Microsoft JDBC Driver 8.2
The mssql-jdbc-8.2.2.jre8.jar, mssql-jdbc-8.2.2.jre11.jar, or mssql-jdbc-8.2.2.jre13.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 8.2 for SQL Serversqljdbc_8.2enumssql-jdbc-8.2.2.jre11.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_8.2/enu/mssql-jdbc-8.2.2.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-8.2.2.jre8.jar, mssql-jdbc-8.2.2.jre11.jar, or mssql-jdbc-8.2.2.jre13.jar.
For Microsoft JDBC Driver 7.4
The mssql-jdbc-7.4.1.jre8.jar, mssql-jdbc-7.4.1.jre11.jar, or mssql-jdbc-7.4.1.jre12.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 7.4 for SQL Serversqljdbc_7.4enumssql-jdbc-7.4.1.jre11.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_7.4/enu/mssql-jdbc-7.4.1.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-7.4.1.jre8.jar, mssql-jdbc-7.4.1.jre11.jar, or mssql-jdbc-7.4.1.jre12.jar.
For Microsoft JDBC Driver 7.2
The mssql-jdbc-7.2.2.jre8.jar or mssql-jdbc-7.2.2.jre11.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 7.2 for SQL Serversqljdbc_7.2enumssql-jdbc-7.2.2.jre11.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_7.2/enu/mssql-jdbc-7.2.2.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-7.2.2.jre8.jar or mssql-jdbc-7.2.2.jre11.jar.
For Microsoft JDBC Driver 7.0
The mssql-jdbc-7.0.0.jre8.jar or mssql-jdbc-7.0.0.jre10.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 7.0 for SQL Serversqljdbc_7.0enumssql-jdbc-7.0.0.jre10.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_7.0/enu/mssql-jdbc-7.0.0.jre10.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-7.0.0.jre8.jar or mssql-jdbc-7.0.0.jre10.jar.
For Microsoft JDBC Driver 6.4
The mssql-jdbc-6.4.0.jre7.jar, **mssql-jdbc-6.4.0.jre8.jar, or mssql-jdbc-6.4.0.jre9.jar files are installed in the following location:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 6.4 for SQL Serversqljdbc_6.4enumssql-jdbc-6.4.0.jre9.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_6.4/enu/mssql-jdbc-6.4.0.jre9.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-6.4.0.jre7.jar, **mssql-jdbc-6.4.0.jre8.jar, or mssql-jdbc-6.4.0.jre9.jar.
For Microsoft JDBC Driver 6.2
The mssql-jdbc-6.2.2.jre7.jar or mssql-jdbc-6.2.2.jre8.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 6.2 for SQL Serversqljdbc_6.2enumssql-jdbc-6.2.2.jre8.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_6.2/enu/mssql-jdbc-6.2.2.jre8.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-6.2.2.jre7.jar or mssql-jdbc-6.2.2.jre8.jar.
For Microsoft JDBC Driver 4.1, 4.2, and 6.0
The sqljdbc.jar file, sqljdbc4.jar file, sqljdbc41.jar, or sqljdbc42.jar file are installed in the following location:
The following snippet is an example of the CLASSPATH statement that is used for a Windows application:
CLASSPATH =.;C:Program FilesMicrosoft JDBC Driver 6.0 for SQL Serversqljdbc_4.2enusqljdbc42.jar
The following snippet is an example of the CLASSPATH statement that is used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_4.2/enu/sqljdbc42.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either sqljdbc.jar, sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar.
Dbeaver Mssql Dump
Note
On Windows systems, directory names longer than the 8.3 filename convention or folder names with spaces may cause problems with classpaths. If you suspect these types of issues, you should temporarily move the sqljdbc.jar file, sqljdbc4.jar file, or the sqljdbc41.jar file into a simple directory name such as C:Temp, change the classpath, and determine whether that addresses the problem.
Applications that are run directly at the command prompt
The classpath is configured in the operating system. Append sqljdbc.jar, sqljdbc4.jar, or sqljdbc41.jar to the classpath of the system. Alternatively, you can specify the classpath on the Java command line that runs the application by using the java -classpath option.
Applications that run in an IDE
Each IDE vendor provides a different method for setting the classpath in its IDE. Just setting the classpath in the operating system will not work. You must add sqljdbc.jar, sqljdbc4.jar, or sqljdbc41.jar to the IDE classpath.
Servlets and JSPs
Servlets and JSPs are run in a servlet/JSP engine such as Tomcat. The classpath must be set according to the servlet/JSP engine documentation. Just setting the classpath in the operating system will not work. Some servlet/JSP engines provide setup screens that you can use to set the classpath of the engine. In that situation, you must append the correct JDBC Driver JAR file to the existing engine classpath and restart the engine. In other situations, you can deploy the driver by copying sqljdbc.jar, sqljdbc4.jar, or sqljdbc41.jar to a specific directory, such as lib, during engine installation. The engine driver classpath can also be specified in an engine-specific configuration file.
Enterprise Java Beans
Enterprise Java Beans (EJB) are run in an EJB container. EJB containers are sourced from various vendors. Java applets run in a browser but are downloaded from a web server. Copy sqljdbc.jar, sqljdbc4.jar, or sqljdbc41.jar to the web server root and specify the name of the JAR file in the HTML archive tab of the applet, for example, <applet ... archive=mssql-jdbc-***.jar>.
Making a simple connection to a database
Using the sqljdbc.jar class library, applications must first register the driver as follows:
Class.forName('com.microsoft.sqlserver.jdbc.SQLServerDriver');
When the driver is loaded, you can establish a connection by using a connection URL and the getConnection method of the DriverManager class:
Starting from JDBC API 4.0, the DriverManager.getConnection() method is enhanced to load JDBC drivers automatically. Therefore, applications do not need to call the Class.forName method to register or load the driver when using driver jar libraries.
When the getConnection method of the DriverManager class is called, an appropriate driver is located from the set of registered JDBC drivers. sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar file includes 'META-INF/services/java.sql.Driver' file, which contains the com.microsoft.sqlserver.jdbc.SQLServerDriver as a registered driver. The existing applications, which currently load the drivers by using the Class.forName method, will continue to work without modification.
Note
sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar class library cannot be used with older versions of the Java Runtime Environment (JRE). See System requirements for the JDBC driver for the list of JRE versions supported by the Microsoft JDBC Driver for SQL Server.
For more information about how to connect with data sources and use a connection URL, see Building the connection URL and Setting the connection properties.
See also
Step-by-step tutorial on connecting to SQL Server with DBeaver.
Once you've installed DBeaver, you'll probably want to connect to a database. below are instructions for connecting to SQL Server using DBeaver on a Mac.
Note that, although this tutorial uses SQL Server, DBeaver supports many different database management systems.
Launch DBeaver
Click on the DBeaver icon (either in your Launchpad or the Applications folder) to launch the DBeaver application.
Launch the New Connection Wizard
If this is the first time you've launched DBeaver, you'll probably be prompted with the Create new connection dialog.
Expand the SQL Server node, select jTDS driver, and click Next >.
For this tutorial I selected jTDS driver, but by all means select another driver if you prefer.
If the Create new connection wizard doesn't automatically appear when you open DBeaver, go to Database > New Connection to initiate this wizard.
Enter Connection Settings
Enter the connection settings for the SQL Server instance that you'd like to connect to.
If the SQL Server instance is running on your local machine, use localhost.
Also click Test Connection to see if there are going to be any problems with the connection or not.
Download Driver Files (if required)
The connection wizard will tell you if you need to download any driver files. If you do, select the file/s and click Download.
Success Dialog Box
Once the driver has downloaded, a Success dialog is displayed. Click OK.
This dialog box would have appeared at the previous step if you didn't need to download a driver.
Continue with the Connection
Now that the driver has been downloaded, click Next > to continue with the connection.
Network Settings
This step gives you the option of entering any network settings that are required to access the SQL Server.
In this case, the SQL Server is running locally, so leave the default settings and click Next >.
Finish
Change any settings as required. For this tutorial, I left them all at the default settings.
Click Finish to create the connection.
That's it. We just made a new connection to SQL Server with DBeaver.
The DBeaver interface is now displayed: