InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 14:52:59 GMT20http://www.sqlservercentral.com/Forums/Topic1399809-391-1.aspxI like your suggestion. Thank you very much.Wed, 26 Dec 2012 11:53:23 GMTTommyFhttp://www.sqlservercentral.com/Forums/Topic1399809-391-1.aspxLet'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 historyYou 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.Mon, 24 Dec 2012 09:36:47 GMTScottPletcherhttp://www.sqlservercentral.com/Forums/Topic1399809-391-1.aspxHi,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.Sun, 23 Dec 2012 23:20:13 GMTTommyF