collationdb2encoding
Ok, first of all, I have really limited knowledge about databases.
Problem that I have is next: I inserted few rows with data that contains Dutch characters, such as names of different countries. Some countries have at the end of their names Dutch language special characters ë, or like Ukraine have two dots on i (Servië, Oekraïne, Tunesië, Somalië, etc…).
These characters in database looks like this: ë -> A≈ and ï -> AZ.
Of course I would like that these Dutch characters shows in database.
I've tested two tools that can provide info about transactions including when, who, using which computer and application
ApexSQL Audit creates auditing triggers for you, so if you're not up to coding and creating triggers for each of your tables, this is an option
It has 2 built in reports, and the good thing about it is that it saves all captured transactions into 2 tables, so you can run queries against them and extract any info you need
Unfortunately, it can't replay the transactions
Another one is ApexSQL Log. It reads transaction logs and trn backups, so the database has to be in Full recovery model. Besides the data transactions, it also tracks schema changes (create table, alter function, etc) and it can replay transactions
You won't get any specific answer to this question, because as you observed, it depends.
The answer depends on your company's tolerance for having one DB2 instance adversely impact the performance of another's. You may be able to control or limit this impact if your AIX admins are willing to learn and set up WLM policies at the operating system level (not DB2 WLM).
This is really a question of capacity management. Understanding the workloads in your environment is key here, and being able to identify (or predict) when you'll run into limits will influence your decisions about how many instance(s) to put on a single server.
Best Answer
Well, the trick is that a database can only specify which "locale" it is used for at creation time. When you create a database you either specify what you want by specifying the codeset, territory and collation (example
CREATE DATABASE MYDB AUTOMATIC STORAGE YES ON '/data' DBPATH ON '/dbdir' USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM), or you let DB2 guess based on some system settings.You can check what yours is set to by running
db2 get db cfg for <db name>. In the case of what was used above you would see the following:Note, that you cannot change these settings after a database is created. One option would be to export the data from your database (using
db2export), drop and rebuild the database the with language settings you want, and then re-import the data (usingdb2import).Another option would be to see if there is a way to represent your character strings as pure "bit" data and store the bit sequence rather than the "string" or declare a field as
VARCHAR FOR BIT DATAand store your strings as bit sequences (though I'm not 100% positive on that one...).Also check out the links below as they have more information on the language thing and how to deal with multi-code-page results. Note that some of this information requires DB2 to be at least at version 9.5 or higher.
as well as check out the whole Multicultural support parent/sibling links related to that list link (the Character conversion between different code pages).