Design suggestion

  • Hi,

    I have to keep in a login history table the user's operating system / operating system version / browser / browser version / device type (mobile/pc etc) / device.

    In case there are around a million entries a month and I have to keep two years of data,

    should I use dictionary tables or should I keep the full strings descriptions in the login history table?

    Thank you.

  • Let's assume you can get all that information.

    You have conflicting needs: you don't want to slow down the login process, but you also don't want to store full string descriptions for everything for the entire history

    You could consider a two-level system: the initial logging captures everything with full strings. Then another process periodically pulls that data into a permanent history table, assigning identifiers in place of strings as required. Then the initial log data is deleted.

    This allows you to have a minimal effect on logins but still save space and enhance analysis by assigning codes later.

    SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".

  • I like your suggestion. Thank you very much.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply