- Jdbc Driver Class For Sql Server
- Sql Server Jdbc Driver Classpath
- Java Sql Server Driver
- Cannot Load Jdbc Driver Class Sql Server
- Jdbc Driver Class For Ms Sql Server 2008
The driver class for the Type 4 JDBC MS SQL Server driver is weblogic.jdbc.sqlserver.SQLServerDriver. This is a non-XA driver. This is a non-XA driver. Microsoft SQL Server URL.
I try to create simple application for testing hibernate. I use ms sql server as database
I download sqljdbc4 from microsoft official site and add to build path of my sts(eclipse):
And it locates on maven dependencies
When I invoke my application I saw:
I don't understand the cause if this messages. If in code I write:
and type ctrl+left mouse click I saw ![enter image description here][2]
Therefore I can made output, that this class exists, but hibernate doesn't see its.
Can you help me?
UPDATE
How do you invoke your application?
I have so class:
and so:
right click for Main.java -> run as->java Application
UPDATE 2
project structure:
![enter image description here][3]
pom.xml:
UPDATE FOR Vinay
But I have old problems(((
UPDATE
st>
content sqljdbc.jar
Solving:
WRONG:
RIGHT:
3 Answers
very simple mistake:
Solution:
WRONG:
RIGHT:
It is very funny)
kapex- Add sqljdbc driver as maven dependency. Please refer this
- Invoke mvn eclipse:eclipse
- Run your application
I am pretty sure this will solve your problem.
The following snippet works well for connecting and querying database in Microsoft SQL SERVER. Please note that Microsoft does not make jar file 'sqljdbc42.jar'(which is jdbc driver) available on any online repo like MavenCentral(). Therefore, you would need to download this jar from Microsoft's website and save in project workspace directory. Download 'sqljdbc_4.2.6420.100_enu.exe'
Unzip the downloaded file and go to Microsoft JDBC Driver 4.2 for SQL Server-->sqljdbc_4.2-->enu. Here you will see the file sqljdbc42.jar. Copy the file into project workspace. I copied into dir name 'lib'.
Not the answer you're looking for? Browse other questions tagged javahibernatemaven or ask your own question.
-->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.
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:
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.
Jdbc Driver Class For Sql Server
Your choice will also determine available features. For more information about which JAR file to choose, see System requirements for the JDBC driver.
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 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 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.
Sql Server Jdbc Driver Classpath
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:
Java Sql Server Driver
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
Cannot Load Jdbc Driver Class Sql Server
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.
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
Jdbc Driver Class For Ms Sql Server 2008
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.