Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
mailtonoorul
Starting Member
3 Posts |
Posted - 2014-05-26 : 09:32:03
|
1) In a database design until which normal form it is practically possible? Until 2nd normal form is it advisable?2) Is it advisable to use IDENTITY [(seed, increment)] to generate the sequence number in a table for concurrent user in Microsoft SQL Server 2012?3)Is it advisable to use SCOPE_IDENTITY () to get the latest identity number during concurrent user in Microsoft SQL Server 2012? 4)Kindly help us select the best solution from the following for creating reference in Microsoft SQL Server 2012Primary key column, integer data type with IDENTITY [ (seed , increment) ] to generate a sequence of number Or Code Column / Composite primary key column with varchar data type Noorul Ameen |
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2014-05-26 : 15:11:23
|
1. depends on many factors none of which you have provided.2. yes3. yes4. Advantages and disadvantages to both practices. Identity for PKs and referential integrity is efficient and uses less space. However with that you should also use a unique constraint to prevent logical duplicates (usually referred to as an alternate key). Composite keys act to both enforce uniqueness as well as referential integrity. However JOINs are more awkward there will likely be some tables that simply have no logical key.Be One with the OptimizerTG |
|
|
mailtonoorul
Starting Member
3 Posts |
Posted - 2014-05-27 : 04:24:12
|
whether it is mandatory that table should be in 3rd normal form?whether it can be in 2nd normal formNoorul Ameen |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-05-27 : 13:47:02
|
Nothing is mandatory. "Just depends"Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|