What we do, is to create two tables for each multilingual object. E.g. the first table contains only language-neutral data (primary key, etc.) and the second table contains one record per language, containing the localized data plus the ISO code of the language. In some cases we add a DefaultLanguage field, so that we can … Read more
Assuming you don’t store things like the ‘+’, ‘()’, ‘-‘, spaces and what-have-yous (and why would you, they are presentational concerns which would vary based on local customs and the network distributions anyways), the ITU-T recommendation E.164 for the international telephone network (which most national networks are connected via) specifies that the entire number (including … Read more
String comparison is slower than int comparison. However, this does not matter if you simply retrieve a user from the database using the e-mail address. It does matter if you have complex queries with multiple joins. If you store information about users in multiple tables, the foreign keys to the users table will be the … Read more
Some more answers to your questions: 1) You’re pretty much on target for someone who is approaching a problem like this for the first time. I think the pointers from others on this question thus far pretty much cover it. Good job! 2 & 3) The performance hit you will take will largely be dependent … Read more
Tools –> Options –> Designers node –> Uncheck “ Prevent saving changes that require table recreation “.
What do you think about having a related translation table for each translatable table? CREATE TABLE T_PRODUCT (pr_id int, PRICE NUMBER(18, 2)) CREATE TABLE T_PRODUCT_tr (pr_id INT FK, languagecode varchar, pr_name text, pr_descr text) This way if you have multiple translatable column it would only require a single join to get it + since you … Read more
Reasons to use Foreign Keys: you won’t get Orphaned Rows you can get nice “on delete cascade” behavior, automatically cleaning up tables knowing about the relationships between tables in the database helps the Optimizer plan your queries for most efficient execution, since it is able to get better estimates on join cardinality. FKs give a … Read more
In one-to-one relation one end must be principal and second end must be dependent. Principal end is the one which will be inserted first and which can exist without the dependent one. Dependent end is the one which must be inserted after the principal because it has foreign key to the principal. In case of … Read more
When you create a database in Microsoft SQL Server you can have multiple file groups, where storage is created in multiple places, directories or disks. Each file group can be named. The PRIMARY file group is the default one, which is always created, and so the SQL you’ve given creates your table ON the PRIMARY … Read more
There’s a caveat with the general 39 character IPv6 structure. For IPv4 mapped IPv6 addresses, the string can be longer (than 39 characters). An example to show this: IPv6 (39 characters) : ABCD:ABCD:ABCD:ABCD:ABCD:ABCD:ABCD:ABCD IPv4-mapped IPv6 (45 characters) : ABCD:ABCD:ABCD:ABCD:ABCD:ABCD:192.168.158.190 Note: the last 32-bits (that correspond to IPv4 address) can need up to 15 characters (as … Read more