ousoonerjoe
Programmer
Simple question... I think.
I have a table that all the VARCHAR fields got converted to "SQL_EBCDIC037_CP1_CS_AS" whereas the rest of the system is using "SQL_Latin1_General_CP1_CI_AS" which is the system default. Don't ask how it happened, this is an inherited system. Five years later, we're still finding oddities as we clean this thing up. I suspect it's a leftover setting in TFS and will attack that next.
My question is this, are there any known issues switching the collation on the fly? Any potential conflicts?
Thank you.
SoonerJoe
--------------------------------------------------
“Crash programs fail because they are based on the theory that, with nine women pregnant, you can get a baby a month.” --Wernher von Braun
--------------------------------------------------
I have a table that all the VARCHAR fields got converted to "SQL_EBCDIC037_CP1_CS_AS" whereas the rest of the system is using "SQL_Latin1_General_CP1_CI_AS" which is the system default. Don't ask how it happened, this is an inherited system. Five years later, we're still finding oddities as we clean this thing up. I suspect it's a leftover setting in TFS and will attack that next.
My question is this, are there any known issues switching the collation on the fly? Any potential conflicts?
Thank you.
SoonerJoe
--------------------------------------------------
“Crash programs fail because they are based on the theory that, with nine women pregnant, you can get a baby a month.” --Wernher von Braun
--------------------------------------------------