sql – Reality Me

You mean like getting the papers from the copier in order?

You know, I have probably exported and imported data from hundreds of databases at this point in my life. And never, I say never, have I ever had a collation problem. Collation has to deal with how a database handles issues of sort order, case sensitivity, and sensitivity to accents. It becomes important when your database is not US centric or is going to serve an International audience. Last night it got me.

I tried directly updating data on a server that is probably located in Amsterdam and ended up with:

Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation

Ugh.

You know when you are on a tight schedule, the stupidity that comes with MS SQL, ColdFusion and a Windows Server can make you go bald. There is no reason for something as simple as creating a datasource to be throwing dumb error messages!

Connection verification failed for data source: foo
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user ‘foouser’. Reason: The password of the account must be changed.
The root cause was that: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user ‘foouser’. Reason: The password of the account must be changed.

The password has been changed half a dozen times!

Update: Ah! Either 1) Know what your password policy is and make sure your password is compliant or 2) turn off “Enforce password policy” and “User must change password at next login” (which was my problem). For a datasource, you can probably remove the check from “Enforce password expiration” as well. Note that if you try to do all three of these at once that you will get errors. Remove “User must change password at next login” first then “Enforce password expiration” then “Enforce password policy”.

Tag: sql

Collation?

Stupid CF Configuration Errors and MS SQL

djuggler