Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1943
| From | Erland Sommarskog <esquel@sommarskog.se> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: cluster or hash table advise needed |
| Date | 2015-09-29 22:15 +0200 |
| Organization | Erland Sommarskog |
| Message-ID | <XnsA524E262AB726Yazorman@127.0.0.1> (permalink) |
| References | <fa7449c7-daca-4a6d-81ba-603063464b4f@googlegroups.com> |
M.G. (michael@gurfinkel.us) writes: > We are designing a table with high insert / delete activity. The table > maintains sequence of actions per specific experiments. These are the > attributes: Important question: is the activity concurrent or not? That is, can data for multiple experiments be written simultaneously? > Expected number of records - around 10 million, expected number of > inserts (pure additions) around 5000 a day, number of change > (delete/insert) around 1000 OK, so that is not really high activity. :-) And then I would assume that there is no concurrent activity. I would say that you scrap the ACTIVITY_SEQUENCE column, as it seems to serve no purpose. Make (EXP_ID, ACT_SEQ, ACT_ID) a primary key, because a having a primary key based on data is a good thing. You may never look at indivitual data, but you don't want duplicates. And make this PK clustered, that seems to fit your use of the table very well. -- Erland Sommarskog, Stockholm, esquel@sommarskog.se
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Next in thread | Find similar
cluster or hash table advise needed "M.G." <michael@gurfinkel.us> - 2015-09-29 12:06 -0700
Re: cluster or hash table advise needed Erland Sommarskog <esquel@sommarskog.se> - 2015-09-29 22:15 +0200
Re: cluster or hash table advise needed "M.G." <michael@gurfinkel.us> - 2015-09-29 13:55 -0700
csiph-web