Is there a database to store posts in any national language?

[mobai520]

Is there a database to store posts in any national language or who sent a tutorial, thank you very much

[Nιgнтмαяε]

Why do you keep making the same post over and over with different topic names?

No one is going to help you convert the **** to Chinese.

[mobai520]

Originally Posted by Nιgнтмαяε

Why do you keep making the same post over and over with different topic names?

No one is going to help you convert the **** to Chinese.

Sorry. No, I just want someone to have a tutorial, or have the same post.

[KingKeesie]

*LAUGHING*

[ディオニュソス]

Delete all databases - > recreate them using a Chinese collation -> change your applications codepages to a Chinese one.
Thats most likely all you have to do

[xTwiLightx]

Originally Posted by ディオニュソス

Delete all databases - > recreate them using a Chinese collation -> change your applications codepages to a Chinese one.
Thats most likely all you have to do

He wants to support multiple languages, so only changing the collation won't do the trick.

Like I've stated multiple times in some of OP's threads, using Unicode columns and variables in stored procedures, he achieves what he wants (or at least the database part of it is done - speaking about the c++ code: I don't know what changes have to be made):



As you can see, the 'non_unicode' column can't handle the korean characters, but every other column can (regardless of the collaction in case of nvarchar columns). Also, the N' prefix is indispensable when using unicode.

When SQL Server 2019 is released, char columns/variables with collations using the '_UTF8' suffix will also support unicode characters. But I'd always go the nvarchar way.

[ディオニュソス]

Originally Posted by xTwiLightx

He wants to support multiple languages, so only changing the collation won't do the trick.

Like I've stated multiple times in some of OP's threads, using Unicode columns and variables in stored procedures, he achieves what he wants (or at least the database part of it is done - speaking about the c++ code: I don't know what changes have to be made):



As you can see, the 'non_unicode' column can't handle the korean characters, but every other column can (regardless of the collaction in case of nvarchar columns). Also, the N' prefix is indispensable when using unicode.

When SQL Server 2019 is released, char columns/variables with collations using the '_UTF8' suffix will also support unicode characters. But I'd always go the nvarchar way.

I very much doubt that's what he wants, all he wants is store chinese characters, he just has his speech upped to 100 so nobody understands him unless they have reached the same level of eloquence.

[mobai520]

Originally Posted by ディオニュソス

Delete all databases - > recreate them using a Chinese collation -> change your applications codepages to a Chinese one.
Thats most likely all you have to do

Thank you, but re-establish, I won't

Originally Posted by xTwiLightx

He wants to support multiple languages, so only changing the collation won't do the trick.

Like I've stated multiple times in some of OP's threads, using Unicode columns and variables in stored procedures, he achieves what he wants (or at least the database part of it is done - speaking about the c++ code: I don't know what changes have to be made):



As you can see, the 'non_unicode' column can't handle the korean characters, but every other column can (regardless of the collaction in case of nvarchar columns). Also, the N' prefix is indispensable when using unicode.

When SQL Server 2019 is released, char columns/variables with collations using the '_UTF8' suffix will also support unicode characters. But I'd always go the nvarchar way.

Yes, my problem is this.

Originally Posted by ディオニュソス

I very much doubt that's what he wants, all he wants is store chinese characters, he just has his speech upped to 100 so nobody understands him unless they have reached the same level of eloquence.

Yes, I want this.

Originally Posted by xTwiLightx

He wants to support multiple languages, so only changing the collation won't do the trick.

Like I've stated multiple times in some of OP's threads, using Unicode columns and variables in stored procedures, he achieves what he wants (or at least the database part of it is done - speaking about the c++ code: I don't know what changes have to be made):



As you can see, the 'non_unicode' column can't handle the korean characters, but every other column can (regardless of the collaction in case of nvarchar columns). Also, the N' prefix is indispensable when using unicode.

When SQL Server 2019 is released, char columns/variables with collations using the '_UTF8' suffix will also support unicode characters. But I'd always go the nvarchar way.

This is the name I created in Chinese, click on it and click here.

[xTwiLightx]

Originally Posted by ディオニュソス

I very much doubt that's what he wants, all he wants is store chinese characters, he just has his speech upped to 100 so nobody understands him unless they have reached the same level of eloquence.

The thread title even says "ANY national lanuage"

Originally Posted by mobai520

This is the name I created in Chinese, click on it and click here.

If you just want chinese, go on and set the collation to a chinese one on database or server level and re-create the databases.

To see what collations are available on your server, execute the following query:

select * from sys.fn_helpcollations()
where [name] like 'Chinese%'

For me, the results look like that:


See what fits your requirements, the collation is mainly for the sort order of characters. But that could be different for a complex language like chinese.

Set your codepage everywhere to the one used for chinese
- see

[mobai520]

Originally Posted by xTwiLightx

The thread title even says "ANY national lanuage"


If you just want chinese, go on and set the collation to a chinese one on database or server level and re-create the databases.

To see what collations are available on your server, execute the following query:

select * from sys.fn_helpcollations()
where [name] like 'Chinese%'

For me, the results look like that:


See what fits your requirements, the collation is mainly for the sort order of characters. But that could be different for a complex language like chinese.

Set your codepage everywhere to the one used for chinese
- see

Thank you, the main thing is that I won't



Use this to use this

[xTwiLightx]

Originally Posted by mobai520

Thank you, the main thing is that I won't



Use this to use this

Our results don't have to be the same - you have to decide what collation you need. I am not into the chinese language, so you'll have to go trough that list and choose the one that fits your requirements.

After that, you can check this site which covers a few scenarios when changing the collation:

[mobai520]

Originally Posted by xTwiLightx

Our results don't have to be the same - you have to decide what collation you need. I am not into the chinese language, so you'll have to go trough that list and choose the one that fits your requirements.

After that, you can check this site which covers a few scenarios when changing the collation:

Thank you, I changed the database after the method is damaged, can not be used. This is a backup database, you can try to help me see it.




USE master;
GO

-- Set to single-user mode
ALTER DATABASE [CHARACTER_01_DBF]
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO

-- change collation
ALTER DATABASE [CHARACTER_01_DBF]
COLLATE Chinese_PRC_CI_AS;
GO

-- Set to multi-user mode
ALTER DATABASE [CHARACTER_01_DBF]
SET MULTI_USER WITH ROLLBACK IMMEDIATE;
GO

--Verify the collation setting.
SELECT name, collation_name
FROM sys.databases
WHERE name = N'm_szName';
GO

Message 5075, Level 16, State 1, Line 10
The object 'fn_item2row' depends on the database collation. If the object bound to the schema depends on a database collation, you cannot change the database collation. Please remove the dependency of the database collation and retry the operation.
Message 5072, Level 16, State 1, Line 10
ALTER DATABASE failed. The default collation for the database 'CHARACTER_01_DBF' cannot be set to Chinese_PRC_CI_AS.

(0 rows affected)

[xTwiLightx]

It seems you'll have to re-create the database and execute the scripts to create the tables and procedures after that.

[mobai520]

Originally Posted by xTwiLightx

It seems you'll have to re-create the database and execute the scripts to create the tables and procedures after that.

It should be re-established. Can you help me? Thank you.

[xTwiLightx]

Originally Posted by mobai520

It should be re-established. Can you help me? Thank you.

I can't. I already gave a handful of tips to get chinese language to work.