StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1207068
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-30T14:42:49.023
FavoriteCount
0
LastActivityDate
2009-08-03T08:25:02.620
LastEditDate
2009-08-03T08:25:02.620
LastEditorUserId
123070
OwnerUserId
123070
ParentId
1200420
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Your question is not clear enough. Do you 1) want to make a separate copy of your database for your Russian customers? 2) want to support Russian in the same DB that already supports English and Latvian ? So here is my answers for both 1) In SQL Management Studio right click the database, select Tasks -> Generate scripts -> Script all objects in selected database = true, Finish. script all database objects. then in any text editor open this script and perform replace of strings 'Latvian_CI_AS' to 'Cyrillic_General_CI_AS' NOTE: database collation can be changed with ALTER DATABASE but it will not change collations of all existing columns if they have non-default collations. <hr> 2) If you would like to have full Unicode support in your database (so Latvian, English and Russian words can be stored in the same column), you need to convert all VARCHAR , CHAR and TEXT fields to NVARCHAR, NCHAR, NTEXT In this case I will also recommend you to create database script, replace VARCHAR to NVARCHAR , CHAR to NCHAR, TEXT to NTEXT Then with the help of Tasks/Import data... wizard you will transfer data from old database to new one (if you need this data). Another possibility, if you have a few tables, just go to SQL Management Studio and change types to Unicode types manually. One could say it is also possible to do with alter table t alter column name nvarchar(size) script but if you have any constraint or defaults attached to this column, you will get an error ALTER TABLE ALTER COLUMN name failed because one or more objects access this column. and you will need to drop/create constraints in your script and this could be a nightmare... As CMS developer you will have to copy the database in any case, because when you convert everything in DB to unicode, I bet that in some places ASP/PHP code may stop working as expected. So having old and new copies will allow you to debug and fix problems one by one.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConvert web-based CMS to support utf-8
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBogdan_Ch
UserOwnerUserId
1. USBogdan_Ch
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.