May 23, 2008 at 12:12 pm
Check the code to see if it added the COLLATE key word after the parameter definition. That would cause the problem.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 23, 2008 at 1:11 pm
The word COLLATE is no where in my procedure and I do not recall seeing it anywhere when building any recent tables or indexes.
Any way to reset the collate for parameters, back to the database_default?
May 23, 2008 at 1:24 pm
I'm not sure. I've never seen it go off without there being a collation value set either on the table or column or parameter. If you're getting collation errors on parameters that don't have collation settings... I'm not sure.
Are you on the latest service pack & all? Have you looked on the MS web site to see if there's a hot fix related to this issue?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 23, 2008 at 2:20 pm
I have punted. I have looked around and have given up. I recreated the procedure with a new name and dropped the old procedure. It is all working now. I will just chalk it up to TOAD, since it does not seem to be a database issue.
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply