ORACLE APEX 21.2: How to export Classic Report with Japanese characters - export

I want to export my CR which contains Japanese characters (the type of the column that contains the Japanese word is NVARCHAR2)
Here are the characteristics of my DB:

Related

Remove emoji or smiley characters in SQL Server ntext column?

I have a mobile chat conversation text area which is stored in ntext data type in SQL Server 2008. I am doing some process character by character. I need to do something I do not know to pass these kind of emoji characters. Should I eliminate them or collate to different collation or encode to different char-set. My table's collation type is Latin1_General_CI_AS. I need something like this:
IF(SUBSTRING(#chat_Conversation, #i, 1) = 'Emoji')
CONTINUE;
As a first guess I'd suggest to place an N in front of your literal
Compare the results:
SELECT '๐Ÿ˜Š'
,N'๐Ÿ˜Š';
The result
ExtASCII Unicode
?? ๐Ÿ˜Š
Without the N the literal is read as extended ASCII, unknown characters are returned as question marks. With N you are dealing with UNICODE (to be exact: UCS-2)...
UPDATE
As pointed out in comments: Do not use NTEXT!
NTEXT, TEXT and IMAGE are deprecated for centuries! These types will not be supported in future versions!
Convert all your work (columns, variables...) to
NTEXT -> NVARCHAR(MAX) (covering UCS-2 characters)
TEXT -> VARCHAR(MAX) (covering extended ASCII, depending on COLLATION and code page)
IMAGE -> VARBINARY(MAX) (covering BLOBs)
Hint
If you are dealing with special characters like foreign alphabets or emojis you should always use the N with literals and with types...

Detecting split character in string

Recently I had a Problem with Splitting a HTML string into separate columns in Access 2010 and store date in SQL server 2008R2 table. This works more or less because the number of lines varies.
To avoid storing the HTML-tags I have a easier solution, I use a text field in Access which is Formated as Standard while the other text-field is formated as rich-text to contain the Format.
Inserting the same content, which is copied from a HTML mail in the Standard text field maintains the LINE FEED !
How can I "detect" which character is it to replace it by another character for further use??
Example:
<div><font face=Arial size=3 color=black>Customer Name</font></div>
<div><font face=Arial size=3 color=black>Customer Address</font></div>
<div><font face=Arial size=3 color=black>12345 City</font></div>
is the copied Content from html mail and inserted into the rich-text field.
If I copy this Content to a Standard text field it Looks like this:
Customer Name
Customer Address
12345 City
In the Server table the Content of the field Looks like this
Customer Name Customer Address 12345 City
But to maintain the line feed in the Access field there must be any character, but which??
Thanks!
Michael
In the SQL-Server table, multiple rows are shown as one row. If you set the ControlSource property of the Access TextBox to that column, it will be shown with multiple lines.
If you still want to know the characters: It's a combination of the ASCII control characters CR and LF (chr(13) & chr(10) or vbCrLf or vbNewLine). In SQL-Server syntax it's CHAR(13)+CHAR(10).

How to search japanese name using a stored procedure in SQL Server

I am writing a stored procedure for searching the Japanese name from the table which contains Japanese unicode strings. I have declared input parameter as nvarchar
But the application is sending me search string in 'search_string' format NOT in N'search string' format. How do I perform searching?

Manual import into SQL Server 2000 of tab delimited text file does not format international characters

I have searched for this specific solution and while I have found similar queries, I have not found one that solves my issue. I am manually importing a tab-delimited text file of data that contains international characters in some fields.
This is one such character: Exhibit Hall Cโ€“D
it's either an em dash or en dash in between the C & D. It copies and pastes fine, but when the data is taken into SQL Server 2000, it ends up looking like this:
Exhibit Hall Cรขโ‚ฌโ€œD
The field is nvarchar and like I said, I am doing the import manually through Enterprise Manager. Any ideas on how to solve this?
The problem is that the encoding between the import file and SQL Server is mismatched. The following approach worked for me in SQL Server 2000 importing into a database with the default encoding (SQL_Latin1_General_CP1_CI_AS):
Open the .csv/.tsv file with the free text editor Notepad++, and ensure that special characters appear normal to start with (if not, try Encoding|Encode in...)
Select Encoding|Convert to UCS-2 Little Endian
Save as a new .csv/.tsv file
In SQL Server Enterprise Manager, in the DTS Import/Export Wizard, choose the new file as the data source (source type: Text File)
If not automatically detected, choose File type: Unicode (in preview on this page, the unicode characters will still look like black blocks)
On the next page, Specify Column Delimiter, choose the correct delimiter. Once chosen, Unicode characters should appear correctly in the Preview pane
Complete import wizard
I would try using the bcputility ( http://technet.microsoft.com/en-us/library/ms162802(v=sql.90).aspx ) with the -w parameter.
You may also want to check the text encoding of the input file.

Export Data from Tables without Carriage Return/Enter

I am trying to export data from MS SQL table, one column stores data from text area and lot of them have Carriage keys and commas in them, this is messing up the csv file. How can I export data without CR and is it possible to export it in colon separated instead of comma ?
In general it depends on how smart is your "receiver" of CSV.
It is normal to export column containing Carriage return e.g. html code fragments stored in database.
Solutions to export such columns are:
Wrap column contents in delimiters (usually quotas but you can choose your own).
Replace CR by special unique character sequence and then replace this sequence to CR on the other side of export.
All of this can be done using "Export Data" task in SSMS.
For method 1 you can use "Text qualifier option" option, for method 2 you should write a query to replace CR sequence.
Please look at documentation:http://msdn.microsoft.com/en-us/library/ms140052%28v=sql.100%29.aspx

Resources