![]() ('SPECIAL CHARACTERS - APOSTROPHE','Zombie''s Land'), ('SPECIAL CHARACTERS - CARRAGE RETURN LINE FEED','Zombieland' + CHAR(13) + CHAR(10)), ('SPACE AT START AND END', N' Zombieland '), ,THE_TEXT NVARCHAR(60) COLLATE Latin1_General_CS_AS IF (SELECT OBJECT_id(N'TEST_DATA','U')) IS NOT NULL ![]() So the “EXAMPLE_TYPE” can be “SPACE AT END” and “THE_TEXT” has a piece of text with a space at the end (‘Zombieland ‘). The first column is a description of the key component we are looking at in the 2 nd column. The script below will create a table with 2 columns. What I do is run them against the data every morning and send out emails to those responsible so they can correct them before the issue starts to manifest. ![]() ![]() Over the years I have compiled a small library of queries that I hope you will find as useful as I have. The reality is that even if you have a great deal of control over the data, this stuff always sneaks in. These issues manifest as odd characters on a report, off center titles, screens not opening, orders failing to get created and the list goes on. In addition many times the errors associated with the problem have nothing to do with identifying the character, but are related to the issue it is causing. When working with multiple source systems wouldn't it be nice if everyone could agree on what characters were acceptable. Special characters are one of those necessary evils.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |