Fixing the Error
-
Comments posted to this topic are about the item Fixing the Error
-
The error message appears to be missing from your message. Can you tell me, precisely, what the error is please? That will make it much easier to fix the problem.
Sorry, muscle-memory. At least I know there's an error message. What I used to get was, "the report's not working."
On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
—Charles Babbage, Passages from the Life of a PhilosopherHow to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
-
Well that's weird. I see it in the editor.
Changing the formatting to get it to show up and awarding back points.
-
In this example, I guess it's reasonable to just convert the data type to nvarchar to fix the immediate encoding issue but is this really the best practice? If this error was introduced in a larger context where changing the data type may be non-trivial, I think the COLLATE clause is the more appropriate fix. Thoughts?
-
The COLLATE Clause is a great way to fix things where it makes sense that the collation differs between databases.
It really depends on what the situation is as to what the best fix might be. I rarely want to change data types if I can avoid it
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply