Today in the group saw someone asked this question, then I summed up the knowledge to share it with you. There may be something wrong, of course, and I would like to point out:
Msbase.jar, Mssqlserver.jar, Msutil.jar (Support sql2000):
Early Connection Database jar package: You need to manually import the driver package when connecting data. That is, manually import class.forname (driver name);
SQL Server JDBC Driver 2.0----Sqljdbc.jar and Sqljdbc4.jar
New JDBC Connection database jar package, support sql2005,sql2008
Sqljdbc.jar
When using the Sqljdbc.jar class library, the application must first register the driver by Class.forName (the driver name). Jdk1.6 above version is not recommended for use.
Sqljdbc4.jar
In JDBC API 4.0, the Drivermanager.getconnection method is enhanced to automatically load JDBC Driver. Therefore, when using the Sqljdbc4.jar class library, the application does not need to invoke the Class.forName method to register or load the driver. When the Getconnection method of the DriverManager class is invoked, the appropriate driver is found from the registered JDBC Driver set. The Sqljdbc4.jar file includes the "Meta-inf/services/java.sql.driver" file, which contains the. Sqlserver.jdbc.SQLServerDriver as a registered driver. Existing applications, which currently load drivers by using the Class.forName method, continue to work without modification.
Note: The Sqljdbc4.jar class Library requires a version 6.0 or later Java Runtime Environment (JRE).