Dbeaver драйвера для mssql



Connect to SQL Server with DBeaver

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.

Источник

Как настроить DBeaver для подключения к серверу ms sql

У меня была аналогичная проблема, и я выполнил:

Надеюсь, что это поможет!

3 ответа

Итак, у нас была та же проблема. Я не хочу, если это все равно поможет вам, я просто нашел ваш вопрос. И чтобы решить мою проблему, я также искал в Интернете, но, к сожалению, не нашел решения (по крайней мере, в моем быстром поиске). Итак, что я сделал, чтобы решить эту проблему, я просто ее прикрыл. Надеюсь, вы сможете воспроизвести это.

Шаг 1. Запустите dbeaver

Шаг 2. Выберите новый тип подключения, в вашем случае, MS SQL Server -> Драйвер Microsoft -> Далее.

Шаг 3. Когда я сделал свою конфигурацию, JDBC URL, Port и Host были уже заполнены. Итак, что вы будете делать здесь, это ввести ваши User name и Password для SQL Server. Затем нажмите Test Connection. Вам будет предложено загрузить драйверы, сделайте это.

Шаг 4. Я ничего здесь не делал. Просто нажмите Next

Шаг 5. Я просто нажал Finish здесь.

Шаг 6. Закончив, вы увидите окно DBeaver — General. Теперь вы можете получить доступ к своему SQL Server.

Итак, у нас была та же проблема. Я не хочу, если это все равно поможет вам, я просто нашел ваш вопрос. И чтобы решить мою проблему, я также искал в Интернете, но, к сожалению, не нашел решения (по крайней мере, в моем быстром поиске). Итак, что я сделал, чтобы решить эту проблему, я просто ее прикрыл. Надеюсь, вы сможете воспроизвести это.

Шаг 1. Запустите dbeaver

Шаг 2. Выберите новый тип подключения, в вашем случае, MS SQL Server -> Драйвер Microsoft -> Далее.

Шаг 3. Когда я сделал свою конфигурацию, JDBC URL, Port и Host были уже заполнены. Итак, что вы будете делать здесь, это ввести ваши User name и Password для SQL Server. Затем нажмите Test Connection. Вам будет предложено загрузить драйверы, сделайте это.

Шаг 4. Я ничего здесь не делал. Просто нажмите Next [!d4]

Шаг 5. Я просто нажал Finish здесь. [!d4]

Шаг 6. Закончив, вы увидите окно DBeaver — General. Теперь вы можете получить доступ к своему SQL Server.

Итак, у нас была та же проблема. Я не хочу, если это все равно поможет вам, я просто нашел ваш вопрос. И чтобы решить мою проблему, я также искал в Интернете, но, к сожалению, не нашел решения (по крайней мере, в моем быстром поиске). Итак, что я сделал, чтобы решить эту проблему, я просто ее прикрыл. Надеюсь, вы сможете воспроизвести это.

Шаг 1. Запустите dbeaver

Шаг 2. Выберите новый тип подключения, в вашем случае, MS SQL Server -> Драйвер Microsoft -> Далее.

Шаг 3. Когда я сделал свою конфигурацию, JDBC URL, Port и Host были уже заполнены. Итак, что вы будете делать здесь, это ввести ваши User name и Password для SQL Server. Затем нажмите Test Connection. Вам будет предложено загрузить драйверы, сделайте это.

Шаг 4. Я ничего здесь не делал. Просто нажмите Next [!d4]

Шаг 5. Я просто нажал Finish здесь. [!d4]

Шаг 6. Закончив, вы увидите окно DBeaver — General. Теперь вы можете получить доступ к своему SQL Server.

Источник

Admin Manage Drivers

General User Guide

  • Installation
  • Application Window Overview
  • Views
    • Database Navigator
      • Filter Database Objects
      • Configure Filters
      • Simple and Advanced View
    • Projects View
    • Project Explorer
    • Query Manager
    • Background Tasks
  • Database Object Editor
    • Properties Editor
  • Data Editor
    • Navigation
    • Data View and Format
    • Data Filters
    • Data Refresh
    • Data Viewing and Editing
    • Panels
    • Managing Charts
    • Data Search
    • SQL Generation
    • Working with spatial/GIS data
    • Working with XML and JSON
    • Managing Data Formats
    • Virtual column expressions
  • SQL Editor
    • SQL Templates
    • SQL Assist and Auto-Complete
    • SQL Formatting
    • SQL Execution
    • SQL Terminal
    • Variables panel
    • Query Execution Plan
    • Visual Query Builder
    • Script Management
    • Client Side Commands
      • Export Command
    • Debug
      • PostgreSQL Debugger
  • ER Diagrams
    • Database Structure Diagrams
    • Custom Diagrams
    • Edit mode
  • Search
    • File Search
    • DB Full-Text Search
    • DB Metadata Search
  • Schema compare
  • Data compare
  • MockData generation
  • Dashboards, DB monitoring
  • Projects
    • Project security
    • Team work (Git)
  • Bookmarks
  • Shortcuts
  • Sample Database
  • Database Connections
    • Create Connection
    • Edit Connection
    • Connect to Database
    • Invalidate/Reconnect to Database
    • Disconnect from Database
    • Change current user password
    • Advanced settings
      • SSH Configuration
      • Proxy configuration
      • SSL configuration
      • Kerberos authentication
      • Network Profiles
  • Connection Types
  • Transactions
    • Auto and Manual Commit Modes
    • Transaction Log
    • Pending transactions
  • Database drivers
  • Tasks
    • Data export/import
    • Data migration
    • Data Import and Replace
    • Database backup/restore
    • Database maintenance tools
    • Task management
    • Task scheduler
    • Composite tasks
    • Sending results by e-mail
  • Cloud Explorer
    • AWS
    • AWS Credentials
    • AWS SSO
    • GCP Credentials
    • GCP SSO

Enterprise Databases support

  • MongoDB
  • Cassandra
  • InfluxDB
  • Redis
  • AWS (Amazon Web Services)
    • DynamoDB
    • DocumentDB
    • Athena
    • Keyspaces
  • GCP (Google Cloud Platform)
    • Bigtable
  • Couchbase
  • CouchDB
  • Apache Hive/Spark/Impala
  • Netezza
  • Oracle
  • SQLite Crypt
  • Informix

License management

  • License Administration
  • How to Import License
  • How to Reassign License
Clone this wiki locally

Configure drivers with pre-installed jars

You can customize drivers configuration in the workspace/.metadata/.plugins/org.jkiss.dbeaver.core/drivers.xml file. If you have some pre-installed jar files you can reference them in drivers.xml. Example:

Also in drivers.xml you can use the following variables to specify relative paths:

Variable Meaning
drivers_home Standard DBeaver drivers location — ($workspace/drivers by default)
dbeaver_home DBeaver installation folder
home User home folder
workspace DBeaver workspace path

Full drivers.xml example:

Provide predefined drivers configuration

In some cases you may need to provide a driver’s configuration or driver jar files for a number of DBeaver installations automatically.
This can be done by adding a special parameter in the dbeaver.ini file: -Ddbeaver.drivers.configuration-file=c:\some-path\dbeaver-drivers-config.xml

This file has the same structure as drivers.xml file (see above) and it will be loaded before drivers.xml .

You can specify partial driver configuration. For example if you need to configure only the jar path then it may look like this:

Источник

Database drivers

General User Guide

  • Installation
  • Application Window Overview
  • Views
    • Database Navigator
      • Filter Database Objects
      • Configure Filters
      • Simple and Advanced View
    • Projects View
    • Project Explorer
    • Query Manager
    • Background Tasks
  • Database Object Editor
    • Properties Editor
  • Data Editor
    • Navigation
    • Data View and Format
    • Data Filters
    • Data Refresh
    • Data Viewing and Editing
    • Panels
    • Managing Charts
    • Data Search
    • SQL Generation
    • Working with spatial/GIS data
    • Working with XML and JSON
    • Managing Data Formats
    • Virtual column expressions
  • SQL Editor
    • SQL Templates
    • SQL Assist and Auto-Complete
    • SQL Formatting
    • SQL Execution
    • SQL Terminal
    • Variables panel
    • Query Execution Plan
    • Visual Query Builder
    • Script Management
    • Client Side Commands
      • Export Command
    • Debug
      • PostgreSQL Debugger
  • ER Diagrams
    • Database Structure Diagrams
    • Custom Diagrams
    • Edit mode
  • Search
    • File Search
    • DB Full-Text Search
    • DB Metadata Search
  • Schema compare
  • Data compare
  • MockData generation
  • Dashboards, DB monitoring
  • Projects
    • Project security
    • Team work (Git)
  • Bookmarks
  • Shortcuts
  • Sample Database
  • Database Connections
    • Create Connection
    • Edit Connection
    • Connect to Database
    • Invalidate/Reconnect to Database
    • Disconnect from Database
    • Change current user password
    • Advanced settings
      • SSH Configuration
      • Proxy configuration
      • SSL configuration
      • Kerberos authentication
      • Network Profiles
  • Connection Types
  • Transactions
    • Auto and Manual Commit Modes
    • Transaction Log
    • Pending transactions
  • Database drivers
  • Tasks
    • Data export/import
    • Data migration
    • Data Import and Replace
    • Database backup/restore
    • Database maintenance tools
    • Task management
    • Task scheduler
    • Composite tasks
    • Sending results by e-mail
  • Cloud Explorer
    • AWS
    • AWS Credentials
    • AWS SSO
    • GCP Credentials
    • GCP SSO

Enterprise Databases support

  • MongoDB
  • Cassandra
  • InfluxDB
  • Redis
  • AWS (Amazon Web Services)
    • DynamoDB
    • DocumentDB
    • Athena
    • Keyspaces
  • GCP (Google Cloud Platform)
    • Bigtable
  • Couchbase
  • CouchDB
  • Apache Hive/Spark/Impala
  • Netezza
  • Oracle
  • SQLite Crypt
  • Informix

License management

  • License Administration
  • How to Import License
  • How to Reassign License
Clone this wiki locally

You can use a pre-configured database driver or create a new driver.

DBeaver has a lot of pre-configured drivers including SQL, NoSQL, key-value databases, graph databases, search engines, etc. But sometimes you need to connect to a database which was not configured in DBeaver yet.

All you need is a JDBC driver of your database. The rest is easy.

Obtaining JDBC driver

JDBC driver is a program (in Java) which can connect and operate with some local or remote database server. It usually provides all needed functionality to cover 100% of database functionality. The JDBC driver is usually provided by database vendors to allow customers to work with their databases.

The JDBC driver consists of one or multiple jar files. The Jar file is a library which contains program code and some other files. You need to download the driver’s jar files before adding them to DBeaver. Sometimes the jar files are included in the database server distribution — in that case you need to refer to your database documentation or ask your DBA.

Adding driver configuration in DBeaver

Open driver manager dialog

You can open the driver manager from the main menu:

or from Database Navigator drop-down menu.

Add a new driver

Just click the button New and create a new driver. On the driver edit dialog you need to enter all required information:

Parameter Description
Driver Name Name of your driver. It can be any name you like
Driver Type Driver provider. In 99% cases you will need a generic driver (JDBC provider)
Class Name JDBC driver class name. You can get it from the documentation or find it in the jar files (see «Find Class» button description)
URL Template Template of driver URL. You can leave it empty. But in this case you will be ready to set JDBC URL for each your connection. It is better to define a valid template, which will greatly simplify the connections creation. See «URL Templates» for a detailed description
Default Port Default database port. You can get it from the documentation or leave it empty
Embedded Enable it for server-less databases. This flag affects a few config options related to the network/connections management
No Authentication This means that driver does not require authentication (no user/password fields will be shown)
Category Driver category, deprecated
ID Driver unique ID, ignore it
Description Driver description, it is shown in some dialogs/wizards as a hint

This is the list of jar files, binary libraries (dll or so) and any other files required by the driver. In most cases you only need the jar files.
Click «Add File» to add a single jar file, «Add Folder» to add to the folder with Java classes/resources and «Add Artifact» to add the Maven artifact (see below).

After you add the jar files you will be able to find all JDBC driver classes which are found in these jars. Just click on the «Find Class» button and DBeaver will show all of them. In most cases there is just one driver class in the driver. If there are many of them, you need to refer to the driver’s documentation.

DBeaver can download driver jars directly from the Maven repository (it is a global public repository of Java libraries, usually an open-source). If your database driver is published on some public repository you can use this feature. Maven artifacts are better than plain jar files because you can see all existing driver versions and can change the driver version in runtime without any driver properties reconfiguration.

Saving driver, adding connection

After you have finished configuring your driver, just press the Ok button.
Now you can create connection.

If you need to change some driver properties later you can access them directly from connection properties dialog:

JDBC drivers use URLs to identify remote servers — strings similar to classic web URLs. Usually, URL has form jdbc:vendor:host:port/database , for example `jdbc:postgresql:localhost:5432/postgres’. It is not very convenient to edit such a long and an unobvious string. DBeaver can construct this URL from connection parameters (like host, port, etc).

For example above the URL template is: jdbc:postgresql://:/
Host, port and database are parameters which you will need to enter on the connection configuration page.

Supported URL variables:

Parameter Description
Database server host name
Database server port number
Target database name
Target server name (rarely used)
Folder path (on the local file system). Used for embedded drivers
File path (on the local file system). Used for embedded drivers

For most drivers you do not need to change any advanced properties. But in some cases you can use this as driver tuning, e.g. for better performance or for structure fixing.

Parameter Description
Driver supports indexes Driver supports table indexes
Driver supports stored code Whether this driver supports stored code (procedures, functions, packages, etc)
Driver supports references Driver supports table references (foreign keys)
Driver supports SELECT count(*) clause Driver supports SELECT count(*) clause
Driver supports views Driver supports table views
Split procedures and functions Show procedures and functions in different folders
Script delimiter Literal for SQL queries separation in scripts
Script delimiter redefiner SQL clause which redefines script delimiter value
Use script delimiter after query Keep SQL script delimiter after each SQL query
Use script delimiter after SQL block Keep SQL script delimiter after SQL script blocks (BEGIN/END)
String escape character Character used to escape special symbols in strings
Meta model type Type of metadata reading model — standard or indexed
All Objects Pattern SQL pattern for all metadata objects
Omit catalog(s) Do not read and use catalog (aka database) information
Omit single catalog Hide catalog (database) if there is only one catalog on server
Omit schema(s) Do not read and use schemas information
Omit single schema Hide schema if there is only one schema on the server
Use schema filters Use JDBC schema filters when the database does not support catalogs. Otherwise just read all database schemas and filter on client-side
Omit type cache Do not use data types provided by driver
Shutdown parameter Database shutdown URL parameter
Create database parameter Database create URL parameter
Driver supports multiple results Driver supports multiple results for a single query
Driver supports result set limit Driver supports multiple result set limit (max rows)
Driver supports structure cache Driver supports structure cache reading. Enables schema columns, keys, etc
Driver supports TRUNCATE operation Driver supports TRUNCATE command. It is much faster than DELETE without criteria

Queries (Custom driver queries)

Parameter Description
Get active database Query to obtain active database name
Set active database Query to change active database
Shutdown database Query to shutdown active database connection. Used for some embedded databases
PING query Query to check connection state
Dual table name Name of dummy ‘DUAL’ table which is used for expressions evaluation
Active object type Type of selectable object (schema, catalog)
Driver supports results scrolling Driver supports resultset scrolling
Quote reserved words Quote columns/table names if they conflicts with reserved SQL keywords
Escape LIKE masks in search queries Use to access JDBC metadata API. Enabled by default but should be disabled for some (broken) drivers

DDL (DDL generation options)

Parameter Description
Drop column short syntax Use ‘ALTER TABLE DROP column-name’ instead of standard syntax
Drop column — use brackets Use ‘ALTER TABLE DROP (column-name)’ instead of standard syntax
Use legacy SQL dialect for DDL Use legacy SQL dialect for DDL
Add COLUMN keyword in alter table query Add COLUMN keyword after keyword ADD and before column name in alter table query

Formatting (SQL values formats)

Parameter Description
Timestamp format Format pattern for timestamp columns
Date format Format pattern for date columns
Time format Format pattern for time columns

If you have configured some driver, it works well and you think that it makes sense to have this driver configuration in standard DBeaver, please send your configuration to us. Just create a feature request issue on GitHub and copy/paste driver description to the ticket (in any suitable form).

Источник

You may also like...