How not to hard-code collation in stored procedure
-
Is there a better way than to hard-code the collation in your stored procedure? Any help would be greatly appreciated.
-
How about set it at the column level. Then again it might be the problem.
What is the problem exactly?
-
Actually if you are hard-coding the collation on your stored procedure you must be doing something *very* interesting. What is it? I have only come accross such things in MS stored procedures but that is a different thing because they have to support multiple collations, are you too?
* Noel -
I think you are forgetting about case sensitive seaches... but that's the only time I ever used that!!
-
True you will use it on case sensitive serches but the question is
How *not* to ..
... Mine is why would you not ?I have use it also to conver code pages and to represent database defaults in comparisons but I am really eager to know what others are doing as well
* Noel -
Still waiting to see what the original poster needs... looks like we're the ones in hurry here
. -
My guess is that he is doing cross database queries and he wants his stored procedure to automatically detect this and dynamically determine the collating sequence to make the sql work.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply