JDBC MS SQL Server ResultSet Problem

I'm writing a web-app using apache tomcat. I'm using MS SQL Server 2000 as my database. I am having no problem connecting to the database, but whenever I query the database, the ResultSet that is returned never has anything in it. I've tried even the simplest select queries and i'm still getting no results. I thought it might be a problem with the JDBC Driver I've been using, but I'm using the exact same driver for SQL Squirrel Client to connect, and Squirrel Client is returning results just fine from the database. Is there something that I've forgotten in my servlet code? Here's something like what I've been using:
Connection con = DriverManager.getConnection(host, userName, password);
Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery("select * from some_table");

If the select statement returns rows then the loop will execute... Put in some debugging output just before the while() loop, inside the loop, and immediately after the loop.
Are you ignoring exceptions?
Google for "jdbc tutorial". Take the simplest example program there that selects something. Run it as a command line program. Does it work? (Answer: yes.) Now what is different between that example program and your code?

Similar Messages

  • Problem in Creating a JDBC System - SQL Server

    Hi All
    I failed in creating a JDBC System(SQL Server).  I am using SAP EP 7.0 SP 9.  I tried to create the JDBC system with the following properties:
    I am listing them Category wise:
    Connection Properties:
    1. Connection Timeout: 300
    2. Connection URL: jdbc:sap.sqlserver://<server name> : <port name>; DatabaseName=master
    3. Driver Class Name: com.sap.portals.jdbc.sqlserver.SQLServerDriver
    4. Validate Connection: Yes
    UserManagement Properties:
    5. User Mapping Type: admin;user
    Please help me out in making this work. And let me know if any changes to incorporated.
    Regards,
    Vijay.

    Hi vijay,
    I have tried this thing sometime back. But when i create a JDBC system, I never give the <b>Connection Timeout</b> and change the<b> Validate Connection</b> from No to Yes. I just give the <b>Connection URL</b> and the <b>Driver Class Name</b> in the Connection Properties dropdown.
    Try making these changes and check whether the user mapping is done correctly. Also check whether the Connection URL and the Driver Class Name are correct or not. Have a look at the following link:
    <a href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/VC/JDBC%2bConnection%2bSetup">https://www.sdn.sap.com/irj/sdn/wiki?path=/display/VC/JDBC%2bConnection%2bSetup</a>
    Let me know if this works.
    Bye
    Ankur
    Reward points if it helps!!

  • JDBC with SQL Server

    Hi,
    I am trying to connect to a SQL server database by giving table name in (SPVC) database as spvc.dbo.tablename.. If i want to access another database (SPVC_D), how can i do it without changing my java code?? Can i be able to add the database name to the connection string and i can remove the hard coding (spvc.dbo.) from my java code?? How shall i be able to do that..
    Please let me know.. I am very new with JDBC with SQL server..
    Thanks
    Praveen Padala

    In the MS SQL Server that I use, the following syntax
    spvc.dbo.tablename
    Breaks done as follows...
    <database>.<user>.<tablename>
    However connections are always to a database. Thus when one uses the above syntax it basically runs 'in' the one database and accesses another.
    Depending on various attributes of the tables, if and only if, a table called 'tablename' exists in a database called 'spvc_d' then if you connect to 'spvc_d' then you can access 'tablename' just by using 'tablename'.
    So if that is what you are doing you will not have a problem.

  • How to establish a trusted connection with JDBC for SQL SERVER 2000

    Hi!I am using jdk 1.4 and eclipse 3.3.
    I create a servlet in eclipse with in-build tomcat.
    When I run it ,it was working perfectlly has it was suppose to work.
    In this servlet I connect to a sql 2000 database using jdbc-odbc bridge driver.
    But when I tried to deploy the servlet on tomcat 5.5 manully on the same machine ,it gave me error saying
    [Microsoft][SQLServer JDBC Driver][SQLServer]Login failed
    for user 'sa'
    I searched around some post and found that ok ,I need trusted connection
    But I have 2 Questions
    1). Why was in eclipse I was able to connect to the SQL server and why not in the servlet which I deployed manully on tomcat.
    2). How do I create a trusted connection with JDBC for SQL server 2000
    Thnaks for your help in advance.

    Hi! duffymo ,QussayNajjar ,dvohra09 .
    Thank for help.
    The ideas are really great.
    I am trying generate reports for my company.
    When I used eclipse the code worked perfectly.
    below is code which I used
    out.println("Calling For Class Name<br>");
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
    out.println("Calling For Class Name success Now calling database <br>");
    1). jdbcConnection = DriverManager.getConnection("jdbc:odbc:SQLJasper");
    2). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb");
    3). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb","UID=UserName","Password=Password");
    out.println("connecting to database success<br>");
    I had tried to connect the database using this three way.
    In 1st I tried using DSN name .
    Next 2 self explainer for expert like you.
    I used to 2nd variant to connect in eclipse and it worked fine.
    I not an expert in java ,I just doing some research on jasperReport.
    My best guest is that eclipse is using some library files of which I have no clue.
    Thank's for your help,I appretiate it.
    Once again thank a billion.
    Sorry for the messy righting.

  • JDBC MS SQL Server driver catch SQLException on Update statement

    Hi,
    We change the driver for the BEA WebLogic Type 4 JDBC MS SQL Server driver
    driver=weblogic.jdbc.sqlserver.SQLServerDriver
    url=jdbc:bea:sqlserver://db_name:port_number
    since we use this driver we got an error when the application try to update a field date type with a NULL value.
    Before, we use this driver and we didn't have this error
    driver=com.inet.tds.TdsDriver
    url=jdbc:inetdae:ammtl1sqls01:1961
    The stack is:
    Failed to update - id [updateItemBranch] - parameterObject [xxx.domain.store.Item@b0237c].
    Cause:com.ibatis.common.jdbc.exception.NestedSQLException:
    --- The error occurred in com/gildan/ecrm/persistence/sql/Item.xml.
    --- The error occurred while applying a parameter map.
    --- Check the updateItemBranch-InlineParameterMap.
    --- Check the parameter mapping for the 'availableDate' property.
    --- Cause: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver
    Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver

    Carol Villeneuve wrote:
    Hi,
    We change the driver for the BEA WebLogic Type 4 JDBC MS SQL Server driver
    driver=weblogic.jdbc.sqlserver.SQLServerDriver
    url=jdbc:bea:sqlserver://db_name:port_number
    since we use this driver we got an error when the application try to update a field date type with a NULL value.
    Before, we use this driver and we didn't have this error
    driver=com.inet.tds.TdsDriver
    url=jdbc:inetdae:ammtl1sqls01:1961
    The stack is:
    Failed to update - id [updateItemBranch] - parameterObject [xxx.domain.store.Item@b0237c].
    Cause:com.ibatis.common.jdbc.exception.NestedSQLException:
    --- The error occurred in com/gildan/ecrm/persistence/sql/Item.xml.
    --- The error occurred while applying a parameter map.
    --- Check the updateItemBranch-InlineParameterMap.
    --- Check the parameter mapping for the 'availableDate' property.
    --- Cause: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver
    Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driverHi. You should do two things:
    1 - Contact BEA support for the very latest versions of the weblogic drivers.
    2 - show us the actual jdbc code being called, and the full original stacktrace
    of the SQLException.
    Joe

  • RE: Database (SQL-SERVER) access problem

    Have you used NT Control Panel/ ODBC to set up the ODBC data source name?
    You have to define the data source (database) SecTrade as well as the
    driver to be used (SQL Server). This can be done by selecting the Add
    button on the Data Sources screen in Control Panel/ ODBC.
    Hope this helps.
    Sanjay Murthi
    Indus Consultancy Services, Inc.
    From: Administrator
    Sent: Wednesday, August 13, 1997 6:49 PM
    To: "'[email protected]'"
    Cc: murthis; thyagarajm; thyagarm; vasasm; chandraa
    Subject: Database (SQL-SERVER) access problems
    MCI Mail date/time: Mon Aug 11, 1997 10:28 pm EST
    Source date/time: Mon, 11 Aug 1997 19:25:34 +0530
    Hi Forte-Users,
    We have a setup a Sql-Server database on a NT server. In the Forte
    EConsole,
    we have
    setup a ODBC-type Resource for this server, named SERVER2_ODBC. This NT
    server
    is configured as a Client Node in the active Forte environment. Note
    that
    Server2 is not
    the Forte server, but has Forte installed. There is another NT server
    which
    acts as the
    Forte server. NODEMGR and Sql-Server are running on SERVER2.
    In our application, we have a DBSession SO with the database source
    as SERVER2_ODBC, Userid=ForteInstructor. When running the application,
    Forte
    throws an exception, the gist of it being as follows:
    USER ERROR: (This error was converted)
    Failed to connect to database: SecTrade, username: ForteInstructor.
    [Microsoft][ODBC Driver Manager] Data source name not found and no
    default
    driver specified
    We have tried
    1) Installing ODBC drivers on the NT server (Server2)
    2) Accessing local databases from Forte clients which works fine
    3) Accessing the Sql-Server database through Isqlw (Sql-Server Client
    s/w) -
    It works.
    Could someone suggest what we should try to get rid of this problem?
    Thanks for any help,
    Kishore Puvvada

    Rajsarawat wrote:
    Dear sir/mam,
    I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).You have to turn on network (external to your computer) access.
    Under programs->sql server look for "surface"

  • Help - JDBC MS SQL Server and Cursors Error

    Hello,
    Please help. I am using weblogic 8.1 and MS SQL Server 2000. Using JDBC. I have am calling a stored procedure which outputs a CURSOR. I haveing problems specifying the right java.sql.Type for this. I tried java.sql.Type.OTHER but it fails. The code is as follows
    Connection conn = null;
    CallableStatement stmt = null;
    String sqlProc = "{ call GetDocumentDetails(?,?) }";
    try {
    conn = this.getConnection();               
    stmt = conn.prepareCall(sqlProc);
    stmt.setInt(1, docId);
    stmt.registerOutParameter(2,Types.OTHER);
    stmt.execute();
    ResultSet rs = (ResultSet) stmt.getObject(2);
    while(rs.next()) {
    The exception that I get is
    java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver.
         at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
    PLEASE HELP.
    Thanks in advance
    GM

    hi llturro,
    Thanks for answering my question. I have tried out what you suggested, but I still can't fix my problem. The following are the messages that display when I try to run my servlet. It seems that the DataSource, Connection and Statement are ok, however when it comes to the ResultSet the error message appear. What's wrong with my ResultSet coding ?
    ResultSet rs = stat.executeQuery("SELECT ISBN FROM BOOKSINFO WHERE ISBN='"+primarykey+"'");
    setEntityContext Method
    Find by primary key
    DataSource OK
    Connection OK
    Primary Key = 013-00-675721-9
    Statement OK
    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
    java.lang.NullPointerException
    java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
    java.lang.NullPointerException
    java.lang.NullPointerException
    <<no stack trace available>>

  • Java and MS SQL Server 2000 problem, please help

    please help me. I am using java and MS SQL Server 2000, and I'm trying to access and verify the login. I'm getting the following error message: [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index
    Can any please help in this regard.
    String userNumber = (String)userNumField.getValue();
    char[] userPasswordArray = userPasswordField.getPassword();
    String userPassword = new String(userPasswordArray);
         try {
                Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
                java.sql.Connection connection = java.sql.DriverManager.getConnection("jdbc:odbc:Dikolobe_Data");
                java.sql.PreparedStatement statement = connection.prepareStatement(
                        "SELECT USER_NUMBER, USER_PASSWORD, USER_CLASS, USER_STATUS " +
                        "FROM SYS_USER " +
                        "WHERE (USER_NUMBER = ? AND USER_PASSWORD = ?);");
                statement.setString(1, userNumber);
                statement.setString(2, userPassword);
                java.sql.ResultSet result = statement.executeQuery();
                if(result.next()) {
                    String userStatus = result.getString(4);
                    if(userStatus.equals("logged on")) {
                        String loginErrorMessage = "User with number: " + userNumber + " is already logged on.";
                        javax.swing.JOptionPane loginErrorPane = getNarrowOptionPane(72);
                        loginErrorPane.setMessage(loginErrorMessage);
                        loginErrorPane.setMessageType(javax.swing.JOptionPane.ERROR_MESSAGE);
                        javax.swing.JDialog loginErrorDialog = loginErrorPane.createDialog(null, "Login Error");
                        loginErrorDialog.setVisible(true);
                    else {
                        String userClassification = result.getString(3);
                        if(userClassification.equals("Administrator")) {
                            AdminHomePage newAdminHomePage = new AdminHomePage();
                            newAdminHomePage.setVisible(true);
                        else if(userClassification.equals("Educator")) {
                            EduHomePage newEduHomePage = new EduHomePage();
                            newEduHomePage.setVisible(true);
                        statement = connection.prepareStatement(
                                "UPDATE SYS_USER SET USER_STATUS = ? " +
                                "WHERE USER_NUMBER = ?");
                        statement.setString(1, "logged on");
                        statement.setString(2, userNumber);
                        statement.executeUpdate();
                        dispose();
                }

    Doesn't the following link give you enough information?
    http://www.google.com/search?q=invalid+descriptor+index
    Anyway .. This error means that the given ResultSet column index which you're trying to retrieve the value from is out of the range.

  • SQL Server excuteBatch() problem....

    Hi All,
    I am trying to Bulk insert using addBatch() and excuteBatch()
    which works fine.
    The problem I am facing is, when I am inserting 50 queries in excuteBatch(), even
    one of them fails, ( due to some foriegn key violation ) whole process stops.
    Can we able to ignore all the failed ones, and proceed till the end in excuteBatch()?
    I am using MS JDBC Driver for SQL Server and WL server 6.1 sp3.
    any help will be really helpful..
    thanks,
    Arun

    Arun wrote:
    Hi All,
    I am trying to Bulk insert using addBatch() and excuteBatch()
    which works fine.
    The problem I am facing is, when I am inserting 50 queries in excuteBatch(), even
    one of them fails, ( due to some foriegn key violation ) whole process stops.
    Can we able to ignore all the failed ones, and proceed till the end in excuteBatch()?
    I am using MS JDBC Driver for SQL Server and WL server 6.1 sp3.
    any help will be really helpful..
    thanks,
    ArunHi. Duplicate the problem in a standalone program, without weblogic code.
    It sounds like a driver bug, and you should post this to the ms jdbc newsgroup.
    Joe Weinstein

  • SQL Server driver problem

    I am trying to connect to SQL Server 2000. I have JDK1.3.1_02. When I compile my applet I get the error that class sqlserver from the statement "Class.forName(com.microsoft.jdbc.sqlserver.SQLServerDriver);" not found. I have included the path in my classpath as "d:\JDBC\lib\msbase.jar;d:\JDBC\lib\msutil.jar;d:\JDBC\lib\mssqlserver.jar" where JDBC is the root directory for the driver.
    Even the statement "import com.microsoft.*;" returns an error that package com.microsoft.* does not exist. What can be the problem?
    Any suggestions/help appreciated!

    You should be getting a different compiler error. Class.forName() requires a String argument, so your code should look like this:Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");Note the quotes around the class name. Also, your "import" statement is irrelevant in any case because that class is not in the com.microsoft package, it is in the com.microsoft.jdbc.sqlserver package.

  • SQL Server 2000 problem with MII Version 12.1.8 Build(24) Reconnecting

    Hi,
    I have a problem using XMII Version 12.1.8 Build(24) with com.microsoft.sqlserver.jdbc.SQLServerDriver JDBC driver with SQL 2000.
    The problem we have is the machine where the SQL server is installed on reboot as per schedule once a week. When the server comes back online, XMII  seems to get problem to reconnect correctly. Sometimes it reconnects perfectly, sometimes not.
    When it fails, the only way to fix the problem is to uncheck the 'Enabled' checkbox, then save the data server, then check the 'Enabled' checkbox, then save again.
    When the reconnect issue happens, uploading messages to SAP fail 100% of time, but downloading Control Recipes  from SAP works 50% of time. For example, some PO's can be processed correctly, some others not, causing data losses due to poor data buffering(buffering doesn't cover connection time out). The failed PO's are marked as 'Sent' into CO53 SAP transaction but in fact, are lost in a hole causing data losses.
    See the error we get atfer the server reboot:
    Unable to get a connection from the pool
    [EXCEPTION]
    com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
    Cannot create a connection to the database
    [EXCEPTION]
    com.sap.xmii.Illuminator.system.CommunicationException: Cannot create a connection to the database... [see details]
    Error processing transaction com.sap.xmii.bls.engine.TransactionInstance@cee764f
    [EXCEPTION]
    com.sap.xmii.scheduler.CronException: PMU ERR VAN - Cannot Qry MSIDs.... [see details]
    Unable to get a connection from the pool
    [EXCEPTION]
    com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
    Unable to get a connection from the pool
    [EXCEPTION]
    com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
    The only way we have thought to workaround this problem is to develop our own buffering method into XMII workbench puting all data received from SAP or SQL insert query into an Oracle temp database. We should probably be able to fix this by this way, but it reprensents many costs and efforts, so we try to avoid this for sure.
    Please, if you can provide us a patches or hints about how to fix this, it could be very appreciated because loosing data is very anoying.
    Thanks a lot!
    Edited by: mrmans on May 19, 2011 5:48 PM
    Edited by: Michael Appleby on May 19, 2011 6:10 PM

    The validation query is in place and the system works very well 99% of the time.
    When the SQL server machine reboot each sunday morning, during the time the machine is rebooting, the data server lose the connection which is normal, but when the machine comes back alive(less then 10 minutes), the data server seems to stay in an 'in-between' state showing the connection status 'Running' but showing also error messages posted in the orginial post in Netweaver logs. So at first look the data server is up and running and reconnected to SQL server after the reboot, but in fact, following these errors after the SQL server machine has rebooted, some data are processed correctly from SAP (Control Recipes) and some not.
    The problems looks like very similar to threadID 1596329.
    Here is the data server configuration for all our 5 data servers:
    Connector IDBC
    ConnectorID  
    ConnectorType SQL
    DatePrefix '
    DateSuffix '
    DaysRetention 7
    Description VANASR70 INTERFACE with MS-SQL JDBC 3.0
    Enabled T
    InitCommand  
    InternalDateFormat yyyy-MM-dd HH:mm:ss
    JDBCDriver com.microsoft.sqlserver.jdbc.SQLServerDriver
    MaxRetryCount 50
    Name PROF_INT_VAN
    PoolMax 150
    PoolSize 100
    RetryInterval 60000
    ServerPackage com.sap.xmii.Illuminator.connectors.IDBC
    ServerURL jdbc:sqlserver://VANASR70:1433;databaseName=INTERFACE
    Timeout 30
    UseCount 256
    UserName mii_user
    ValidationQuery SELECT GETDATE()
    WaitTime 60

  • MS SQL Server 2000 Problem to Connect

    Hi There
    I have a problem with MS SQL Server 2000 with Service Pack 3 and JDBC from Microsoft
    My tools are:
    - Windows 2003 Server Standart Edition
    - MS SQLServer 2000 with ServicePack 3
    - JDBC from Microsoft with ServicePack 3
    I want to connect in the database using JDBC.
    At first time, I follow the example to chance the authentication of SQL
    Server
    http://www.banmanpro.com/support/sql2k.asp
    Now, when I will try out to connect in the SQL Server, I receive this error
    message
    java.sql.SQLException: [Micro$oft][SQLServer 2000 Driver for
    JDBC][SQLServer]Login failed for user 'Administrador'.
    I'm trying to connect in SQL Server using my Windows Account, in other
    words, I'm using the ADMIN account of Windows and which was registered in
    the SQL Server.
    In then DriverManager.getConnection line from Java, the Username and
    Password is same the operation system, but I receive the error below.
    Maybe Can you help me please?

    You can't log in using Windows credentials using the MS driver (yes, I know that sounds kind of funny). Use jTDS for that, if you really need it (or if you encounter any other problems with the MS driver). Otherwise log in using SQL Server credentials (try with user sa and blank password if not sure).
    Alin.

  • JDBC - MS SQL Server 2000 Driver

    Do you need to have J2EE to run the MS downloaded SQL Server 2000 JDBC Driver? Currently have the J2SE installed with JDK 1.31_01 installed and keep getting errors where doesn't recognize a number of class objects. -- Thanks

    Do you need to have J2EE to run the MS downloaded SQL
    Server 2000 JDBC Driver? Currently have the J2SE
    installed with JDK 1.31_01 installed and keep getting
    errors where doesn't recognize a number of class
    objects. -- ThanksI did not have any problems on windows 2000 with SQL 7, J2SE 1.4 Beta 3. BUT You will have to re-jar the files since there is a corrupted jar file in their driver. This corruption is not fatal, but causes exceptions to be loggued.
    Did you load the driver with Class.forName ?

  • Jdbc -ms sql server

    I have ms sql server instaled on my comp, and i'm using a system account(and for authentification i have windows only chosen), but cannot connect to it using JDBC. My code is:
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = DriverManager.getConnection("jdbc:microsoft:sqlserver:local:1433", uName, pass);
    Initially I used as server name, the server name from the SQL Service manager, but it doens't work with that or "local" either. Also I used as an username and password my windows account but no matter what I fill in there I always get the error:
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL.
         at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
         at java.sql.DriverManager.getConnection(DriverManager.java:512)
         at java.sql.DriverManager.getConnection(DriverManager.java:171)
         at DBConnection.<init>(DBConnection.java:21)
         at DBConnectionTester.main(DBConnectionTester.jav
    a:4)
    I'm using blue j for compiling and running my programs, and sometimes i get an error from blue j too saying "Internal Blue J error: unexpected exception in remote VM java.lang.NullPointerException"
    So if anyone knows how to solve my problem, please help!

    me1357, change the authentication mode to mixedand
    while you're at it get a better driver.The better driver would be... jTds (???)Yes. The MS driver is buggy and slow. I recommend the http://jtds.sourceforge.net/ one based on usage. The MS developers who work on the MS driver have been talking to the Jtds developers to figure out how they (the MS developers) should better implement their driver (the MS one). That about sums it up.
    Although I am glad they realize when they are in over their heads and need some help.
    And now for the always popular disclaimer.
    I am not associated in any way with Jtds other than as a user of the driver I did donate money to the project (which I believe will pay for certification one day but Alin can keep it for all I care) because I am grateful that somebody took the time to write a solid driver.

  • JDBC MS-SQL Server at Oracle

    Hi,
    I'm developing Java procedures in Oracle 8.1.7. I've already loaded the
    Sybase JDBC driver successfully with loadjava and the Oracle procedures that
    access Sybase are working correctly.
    I've tried doing the same with Microsoft SQL Server 2000 JDBC, but it's not
    working. The jar files were placed on the classpath and the problem remains.
    Has anyone loaded the files msbase.jar, msutil.jar and mssqlserver.jar
    successfully in Oracle 8.1.7 with the loadjava command? Any ideas will be
    appreciated.
    Thanks in advance.
    Regards,
    Vanderlei Fonseca

    The only way this will work is if the vendor driver is a type-4 (100% java, no native methods). There is no external 'classpath' that the server uses for Java procedures. Everything has to be loaded with loadjava. I do not know if the SQL Server JDBC drivers are type-1, 2, 3 or 4. You need to check that with MS.

Maybe you are looking for