2013/8/31 Łukasz Walkowski
>
> 3. And this part is most interesting for me. Columns browser, eventsource,
> eventtype, devicetype, operatingsystem contain a small pool of strings -
> for example for devicetype this is set to Computer, Mobile, Tablet or
> Unknown. Browser is set to normalized brow
On Sat, Aug 31, 2013 at 10:06 AM, Łukasz Walkowski <
lukasz.walkow...@homplex.pl> wrote:
> > I think the main "pro" of this approach is that it doesn't use any
> > nonstandard SQL features, so you preserve your options to move to some
> > other database in the future. The main "con" is that you'd
Tom,
> If you're starting to be concerned about space, it's definitely time to
> get away from this choice. Depending on what locale you're using,
> comparing varchar values can be quite an expensive operation, too.
I don't like wasting space and processing power even if more work is required
t
=?utf-8?Q?=C5=81ukasz_Walkowski?= writes:
> 3. And this part is most interesting for me. Columns browser, eventsource,
> eventtype, devicetype, operatingsystem contain a small pool of strings - for
> example for devicetype this is set to Computer, Mobile, Tablet or Unknown.
> Browser is set to
bsreejithin wrote:
> What I posted is about a new setup that's going to come
> up..Discussions are on whether to setup DB cluster to handle 1000
> concurrent users.
I previously worked for Wisconsin Courts, where we had a single
server which handled about 3000 web users collectively generating
h
Hi,
This is my first post on this group so welcome everyone! Currently I'm working
on optimizing a quite simple database used to store events from one website.
Every event is a set of data describing user behaviour. The main table that
stores all events is built using schema:
Column
