cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with update+select fixed queries in MII 12.0

Former Member
0 Kudos

Hi all,

We are in the process of migrating an MII 11.5 project to version 12.0.

A number of the queries are complex and consist of update or insert statements, followed by a select. All are executed against SQL Server 2005 databases using SQL Queries using the Fixed Query option. The "SET NOCOUNT ON" clause is included. In version 11.5, the queries executed the updates/inserts then returned the results from the last select, which could then be used elsewhere in the BLTs. Note that the TDS Driver was used for these Data Servers.

However, in v12.0 the Data Servers now use the JDBC driver issued by Microsoft (sqljdbc 1.2). This does not appear to cater for the sorts of queries that were being used before. Or, something more fundamental is happening at the MII level.

Is there a generic database driver (other than ODBC) that we can use, as in the previous version of MII?

Thanks,

Marc

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Why not continue to use the TDS driver? Also, there's an open source driver called jTDS you might want to investigate.

http://jtds.sourceforge.net/

Answers (3)

Answers (3)

jcgood25
Active Contributor
0 Kudos

The present JDBC driver on your 11.5 server could be copied from C:\ServletExec AS\se-xMII\webapps\default\Lighthammer\WEB-INF\lib\Una2000.jar (or equivalent location). Then you just upload and deploy and your 12.0 system should operate with the same driver.

Former Member
0 Kudos

Thanks Rick.

jTDS has solved the issue.

Regards,

Marc

Former Member
0 Kudos

Be mindful of memory usage on with the jTDS driver. I have had certain applications where a memory leak occured.

I have run into the same problems with the older Microsoft JDBC driver. Especially when you try to use table variables. The latest MSSQL JDBC (ver 2.0) seems to have solved a lot of problems. Unfortunately it only works for JDK 1.5 and above.

Former Member
0 Kudos

Hi Marc,

Is it possible you to check the error messages in logs and post them here?

Also check the SAP Note:990322

Go through below thread:

-Suresh