Well, in this case it seems that the whole schema will be just two tables
CREATE TABLE dbo.Users (
Id int not null identity(1,1) primary key,
Code varchar(...),
FirstAttribute ...,
SecondAttribute ...,
...
)go
CREATE INDEX idx_Users_Code ON dbo.Users(Code)
go
CREATE TABLE dbo.Links (
UserId1 int not null,
UserId2 int not null,
Weight ...,
CONSTRAINT pk_Links PRIMARY KEY CLUSTERED (UserId1, UserId2)
)go
and that's about it.
Object store is most likely an overcomplication in this case.
Jenda
Enoch was right!
Enjoy the last years of Rome.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.