In our extraction queries we sometimes compare string variables after upper casing them. We should be passing the unmodified string variable to the database and then using the database to UPPER both its data value and the string variable before the compare instead of java's toUpper() on the client side. This would avoid differences in the return value of upper when language and collation differences occur.
@ivan: pls specify the queries you have fixed so that QA knows the appropriate scope of testing.
@ivan: Is this just for SQL Server 2012 or for all versions of SQL Server ? Where all do I need to verify this ?
a.) Execute Edit in the Server Tree Node only ?
b.) Execute Edit by executing in the Query Analyzer ?
@ivan: Is this just for SQL Server 2012 or for all versions of SQL Server ? Where all do I need to verify this ?
a.) Execute Edit in the Server Tree Node only ?
b.) Execute Edit by executing in the Query Analyzer ?
should be fixed now. we use a .toUpper() at start of all extractions that will need to be discontinued as this causes issues. This issue will need to be looked a broader level and not just a fix for this specific situation.
should be fixed now. we use a .toUpper() at start of all extractions that will need to be discontinued as this causes issues. This issue will need to be looked a broader level and not just a fix for this specific situation.
Issue #12522 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build 15.0.7-6 |
No time estimate |
1 issue link |
relates to #12517
Issue #12517execute edit throws failed to locate table error for SQL Server |
@ivan: pls specify the queries you have fixed so that QA knows the appropriate scope of testing.