Re: Login Tracking Table

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Nikos Yannacopoulos (nyannacoREMOVETHISBIT_at_in.gr)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 12:24:38 +0300

Robin,

If you are planning to upsize to SQL server, I assume this is going to be a
rather large database, right? With this in mind, the storage size increase
by using one flat users table, even if some users' details are not
populated, will be next to nothing proportionally.
Example: 100 user with no details x 6 null fields x 40 characters per field
= 24KB (actually just under 23.5).
In my opinion, this would never justify the increased design complexity.

HTH,
Nikos

"Robin Lawrie" <robin.lawrie@dsl.pipex.com> wrote in message
news:u6WFrXcpEHA.3252@TK2MSFTNGP14.phx.gbl...
> I am designing an Access database that will eventually be moved to a SQL
> server and be web-enabled.
>
> I would like to be able to track login times for users who exist in a
users
> table and have created a login tracking table for this purpose.
>
> My question concerns the relationships of these and other tables based on
> the userid field.
>
> The primary key for the users table is called userid. This is then linked
to
> a field in the login tracking table.
>
> The userid primary key is also currently linked to a user details table
with
> a 1-to-1 relationship (I split this up since some users will need their
> details stored and other's won't and didn't want to store blank info in
the
> users table - is this good or bad?)
>
> Is it a bad idea to have several tables linked by just the one ID, in this
> case the userid linked to the login tracking and user details table?
>
> Thanks,
>
> Robin.
>
>

Relevant Pages

  • Re: Login Tracking Table
    ... If you are planning to upsize to SQL server, I assume this is going to be a ... > I am designing an Access database that will eventually be moved to a SQL ... > table and have created a login tracking table for this purpose. ... > The primary key for the users table is called userid. ...
    (microsoft.public.access.gettingstarted)
  • Re: Database Auditing and connection strings
    ... We have a need to be able to perform auditing on the database side ... As part of the requirement we must know the userid ... 1) Using a standard ID and password in SQL Server but providing ... This might at least give us an idea as to why connection pooling ...
    (microsoft.public.dotnet.framework.adonet)
  • Hard Code Native Error code in program?
    ... On sql server 2000 ... When I try to establish a connection to the database ... if the UserID does not exist or if the UserID does exist ... NativeError - 18456 The UserID does not exist ...
    (microsoft.public.sqlserver.connect)
  • Re: High Throughput Database
    ... I think 3 tables will provide the same performance as one set per user as long as UserID is the the high-order column of each index. ... I was considering even making a new database per user. ... Perhaps go a different route and learn about load balancing, and how the sql server pooling will work. ...
    (microsoft.public.sqlserver.programming)
  • Re: WSE 3.0 Running under default ASPNet user
    ... UsernameTokenManager which needs to access a remote database. ... The web service needs to access a database on a remote server, ... use the UserID and Password held in the IIS config; ... this would be using the NetworkService account on Server 2003. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)