How to handle jdbc drivers?
Download JDBC driver
This section provides quickstart instructions to make a simple connection to a SQL Server database 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.
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 12.2 for SQL Server provides mssql-jdbc-12.2.0.jre8.jar and mssql-jdbc-12.2.0.jre11.jar class library files.
The Microsoft JDBC Driver 11.2 for SQL Server provides mssql-jdbc-11.2.0.jre8.jar, mssql-jdbc-11.2.0.jre11.jar, mssql-jdbc-11.2.0.jre17.jar, and mssql-jdbc-11.2.0.jre18.jar class library files.
The Microsoft JDBC Driver 10.2 for SQL Server provides mssql-jdbc-10.2.0.jre8.jar, mssql-jdbc-10.2.0.jre11.jar, and mssql-jdbc-10.2.0.jre17.jar class library files.
The Microsoft JDBC Driver 9.4 for SQL Server provides mssql-jdbc-9.4.1.jre8.jar, mssql-jdbc-9.4.1.jre11.jar, and mssql-jdbc-9.4.1.jre16.jar class library files.
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 determine the available features. For more information about which JAR file to choose, see System requirements for the JDBC driver.
The Microsoft JDBC driver jars aren't part of the Java SDK and must be included in Classpath of user application.
If using JDBC Driver 12.2, set the classpath to include the mssql-jdbc-12.2.0.jre8.jar or mssql-jdbc-12.2.0.jre11.jar.
If using JDBC Driver 11.2, set the classpath to include the mssql-jdbc-11.2.0.jre8.jar, mssql-jdbc-11.2.0.jre11.jar, mssql-jdbc-11.2.0.jre17.jar, or mssql-jdbc-11.2.0.jre18.jar.
If using JDBC Driver 10.2, set the classpath to include the mssql-jdbc-10.2.0.jre8.jar, mssql-jdbc-10.2.0.jre11.jar, or mssql-jdbc-10.2.0.jre17.jar.
If using JDBC Driver 9.4, set the classpath to include the mssql-jdbc-9.4.1.jre8.jar, mssql-jdbc-9.4.1.jre11.jar, or mssql-jdbc-9.4.1.jre16.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 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 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 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 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.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 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 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 4.1 or 4.2, set the classpath to include sqljdbc41.jar or sqljdbc42.jar file from the respective driver download.
If the classpath is missing an entry for the right Jar file, an application will throw the common Class not found exception.
The mssql-jdbc-12.2.0.jre8.jar or mssql-jdbc-12.2.0.jre11.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 12.2 for SQL Server\sqljdbc_12.2\enu\mssql-jdbc-12.2.0.jre11.jar
The following snippet is an example of the CLASSPATH statement that's used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_12.2/enu/mssql-jdbc-12.2.0.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-12.2.0.jre8.jar, mssql-jdbc-12.2.0.jre11.jar.
The mssql-jdbc-11.2.0.jre8.jar, mssql-jdbc-11.2.0.jre11.jar, mssql-jdbc-11.2.0.jre17.jar, or mssql-jdbc-11.2.0.jre18.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 11.2 for SQL Server\sqljdbc_11.2\enu\mssql-jdbc-11.2.0.jre11.jar
The following snippet is an example of the CLASSPATH statement that's used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_11.2/enu/mssql-jdbc-11.2.0.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-11.2.0.jre8.jar, mssql-jdbc-11.2.0.jre11.jar, mssql-jdbc-11.2.0.jre17.jar, mssql-jdbc-11.2.0.jre18.jar.
The mssql-jdbc-10.2.0.jre8.jar, mssql-jdbc-10.2.0.jre11.jar, or mssql-jdbc-10.2.0.jre17.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 10.2 for SQL Server\sqljdbc_10.2\enu\mssql-jdbc-10.2.0.jre11.jar
The following snippet is an example of the CLASSPATH statement that's used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_10.2/enu/mssql-jdbc-10.2.0.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-10.2.0.jre8.jar, mssql-jdbc-10.2.0.jre11.jar, or mssql-jdbc-10.2.0.jre17.jar.
The mssql-jdbc-9.4.1.jre8.jar, mssql-jdbc-9.4.1.jre11.jar, or mssql-jdbc-9.4.1.jre16.jar files are installed in the following locations:
The following snippet is an example of the CLASSPATH statement that's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 9.4 for SQL Server\sqljdbc_9.4\enu\mssql-jdbc-9.4.1.jre11.jar
The following snippet is an example of the CLASSPATH statement that's used for a Unix/Linux application:
CLASSPATH =.:/home/usr1/mssqlserverjdbc/Driver/sqljdbc_9.4/enu/mssql-jdbc-9.4.1.jre11.jar
Make sure that the CLASSPATH statement contains only one Microsoft JDBC Driver for SQL Server, such as either mssql-jdbc-9.4.1.jre8.jar, mssql-jdbc-9.4.1.jre11.jar, or mssql-jdbc-9.4.1.jre16.jar.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 9.2 for SQL Server\sqljdbc_9.2\enu\mssql-jdbc-9.2.1.jre11.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 8.4 for SQL Server\sqljdbc_8.4\enu\mssql-jdbc-8.4.1.jre11.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 8.2 for SQL Server\sqljdbc_8.2\enu\mssql-jdbc-8.2.2.jre11.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 7.4 for SQL Server\sqljdbc_7.4\enu\mssql-jdbc-7.4.1.jre11.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 7.2 for SQL Server\sqljdbc_7.2\enu\mssql-jdbc-7.2.2.jre11.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 7.0 for SQL Server\sqljdbc_7.0\enu\mssql-jdbc-7.0.0.jre10.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 6.4 for SQL Server\sqljdbc_6.4\enu\mssql-jdbc-6.4.0.jre9.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 6.2 for SQL Server\sqljdbc_6.2\enu\mssql-jdbc-6.2.2.jre8.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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's used for a Windows application:
CLASSPATH =.;C:\Program Files\Microsoft JDBC Driver 6.0 for SQL Server\sqljdbc_4.2\enu\sqljdbc42.jar
The following snippet is an example of the CLASSPATH statement that's 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.
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 with the java -classpath option.
Each IDE vendor provides a different method to set the classpath in its IDE. Just setting the classpath in the operating system won't work. You must add sqljdbc.jar, sqljdbc4.jar, or sqljdbc41.jar to the IDE classpath.
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 won't 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 (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,
To use 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 with 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 don't 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.
- Copy the program to your workstation.
- Transfer the file from your workstation to your server.
- Make sure you set your classpath to the directory where you put the file in so that your Java commands find the file when you run them.
- Compile the Java file into a class file.
Exception handling allows you to handle exceptional conditions such as program-defined errors in a controlled fashion.
When an exception condition occurs, an exception is thrown. The term thrown means that current program execution stops, and the control is redirected to the nearest applicable catch clause. If no applicable catch clause exists, then the program's execution ends.
JDBC Exception handling is very similar to the Java Exception handling but for JDBC, the most common exception you'll deal with is java.sql.SQLException.
An SQLException can occur both in the driver and the database. When such an exception occurs, an object of type SQLException will be passed to the catch clause.
The passed SQLException object has the following methods available for retrieving additional information about the exception −
By utilizing the information available from the Exception object, you can catch an exception and continue your program appropriately. Here is the general form of a try block −
Study the following example code to understand the usage of try....catch...finally blocks.
Now, let us compile the above example as follows −
When you run JDBCExample, it produces the following result if there is no problem, otherwise the corresponding error would be caught and error message would be displayed −
Try the above example by passing wrong database name or wrong username or password and check the result.
Before you can connect to a DBMS you have to configure the JDBC driver to be used. The driver configuration is available in the connection dialog or through File → Manage Drivers
The JDBC driver is a file with the extension .jar (some drivers need more than one file). See the end of this section for a list of download locations. Once you have downloaded the driver you can store the driver's .jar file anywhere you like.
JDBC drivers should not be stored in the ext directory.
To register a driver with SQL Workbench/J you need to specify the following details:
After you have selected the .jar file(s) for a driver (by clicking on the button), SQL Workbench/J will scan the jar file looking for a JDBC driver. If only a single driver is found, the class name is automatically put into the entry field for the class name. If more than one JDBC driver implementation is found, you will be prompted to select one. In that case, please refer to the manual of your driver or database to choose the correct one.
If you enter the class name of the driver manually, remember that it's case-sensitive: org.postgresql.driver is something different than org.postgresql.Driver
Files that are not found are displayed in red and italics.
The name of the library has to contain the full path to the driver's jar file, so that SQL Workbench/J can find it. Some drivers are distributed in several jar files. In that case, select all necessary files in the file open dialog, or add them one after the other. If an entry is selected in the list of defined jar files when adding a new jar file, the selected entry will be overwritten.
For drivers that require a license file, you have to include the license jar to the list of files for that driver.
You should obtain the required driver files from the database vendor. Once all the required files have been obtained they can be uploaded to the management console. This table lists the requisite JDBC drivers.
Beginning with WebLogic 12.1.3, WebLogic is pre-configured to use a bundled Oracle 12c database JDBC driver. This JDBC driver comes pre-installed with the WebLogic Server installation, and no additional steps are required to connect to an Oracle 12c database.
For the Oracle database, you can locate the driver file in these locations:
The JDBC classes are contained in the Java Package java.sql and javax.sql.JDBC helps you to write Java applications that manage these three programming activities:
Structure of JDBC
JDBC Drivers
JDBC drivers are client-side adapters (installed on the client machine, not on the server) that convert requests from Java programs to a protocol that the DBMS can understand. There are 4 types of JDBC drivers:
Type-1 driver
Type-1 driver or JDBC-ODBC bridge driver uses ODBC driver to connect to the database. The JDBC-ODBC bridge driver converts JDBC method calls into the ODBC function calls. Type-1 driver is also called Universal driver because it can be used to connect to any of the databases.
Type-2 driver
The Native API driver uses the client -side libraries of the database. This driver converts JDBC method calls into native calls of the database API. In order to interact with different database, this driver needs their local API, that’s why data transfer is much more secure as compared to type-1 driver.
Type-3 driver
The Network Protocol driver uses middleware (application server) that converts JDBC calls directly or indirectly into the vendor-specific database protocol. Here all the database connectivity drivers are present in a single server, hence no need of individual client-side installation.
Type-4 driver
Type-4 driver is also called native protocol driver. This driver interact directly with database. It does not require any native database library, that is why it is also known as Thin Driver.
Which Driver to use When?
Related Questions
- How to access amazon mq console?
- How to dispose of old gps?
- How to link atm card with mobile number?
- How to sort ascending in pivot table?
- How to heal sprained knee?
- How to differentiate for ell students?
- How to become oozaru dragon block c?
- How to assemble alto sax?
- How to convert coins into cash?
- How to break in boots?
More Questions
- How to get software developer jobs in amazon?
- What treatment is available for mgus?
- What is transfer music?
- What is the best xs max tempered glass?
- What is fco in trading?
- Amazon aws lightsail pricing?
- What are your weaknesses mba interview?
- What are the best places to freelance?
- What schools have jd mba programs?
- Aws application engineer?
