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 |
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
 Posted - 2004-12-10 : 21:38:36
|
| Hi,I'm creating a tracking component for a website and need some help designing it. Here is my issue:There will be many affiliates who send traffic, and upon sending each unique it is logged to the appropriate database table. The affiliates send users to a certain URL that contains their affilID however they are also going to have the option of adding a "keyword", this is for tracking purposesThese rows are really going to add up over time. Instead of storing 100,000's of rows with a varchar field should I break out this table and create a Keyword table? When a user sends a keyword that isnt recognized it will insert it and find the identity value for it? Seems like a bit of a headache to program but seems like the better alternative.Hope this is clearthanks for any suggestionsmike123 |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-12-11 : 00:11:30
|
| Hmmm ... we do the "make an entry in the keyword table" thing. We wind up with lots and LOTS of keyword entries. And when we delete old, stale, logging rows we have to work out if a keyword is still used, or can be purged.Unless your keywords are long, and very frequently reoccuring, its a bit of an even-stevens call IMO.Mr Codd and Mr Normalisation may disagree!Kristen |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-12-11 : 04:52:49
|
| Up to you - with the normalised design you also have the problem of two messages with the same new keyword turning up at the same time.Are you always going to limit it to a single keyword?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2004-12-14 : 01:17:22
|
quote:
Originally posted by nr
Up to you - with the normalised design you also have the problem of two messages with the same new keyword turning up at the same time.Are you always going to limit it to a single keyword?
My keywords are going to be frequently recurring, however probably not unreasonably long - 10-20 chars average I am guessing. I will be limiting it to a single keyword yes.I am not sure I understand this problem you are presenting with the two messages with the same new keyword turning up at the same time.Thanks a bunch!mike123 |
|
|
|
|
|
|
Database Design Help