on 10-22-2014 10:34 AM
Hi all,
i just migrated an addon from SAP - SQL to SAP - HANA and before i migrated the Company's DB.
The problem occur when execute hana query that have in the "WHERE" varchar filed equal at input value ('M' <> 'm') i can insert "UPPER" to solve the problem
so i have to insert UPPER on all varchar field used in a join in a group by etc.
There is a solution to this big problem, my addon is very big and has hundred and hundred of queries.
some one know how help me?
Regards Alessandro.
First off: please don't ever start saving on exclamation marks.
They really cost nothing and are so super effective in attracting attention and underlining that you really have a serious and very important - if not life changing - request.
Now to your question:
Yes, MS SQL Server allows for case-agnostic WHERE conditions and other DBMS, like SAP HANA, don't.
It's a MSS specific feature, not a SQL Standard function, so that should have been part of your migration project.
Since you're already a step further here, I would propose to focus on an approach that allows to postpone large code changes.
You could, e.g.
1. update all column to a uniform case and
2. setup triggers (yes, there are situations where I consider them useful and appropriate) that ensure that the columns are never again filled with the wrong case.
That'll get you over the next weeks while you can refactor the db access code in your application.
Cheers,
Lars
p.s. next time WRITING EVERYTHING IN UPPER CASE LETTER (how nicely this fits to the topic of this thread) WILL GET YOU TO THE ANSWERS EVEN FASTER.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.