Create 3 users tables

Hello,
In my web site I have 2 types of users: students and professors.
All users need to login but the personal information for each user type
has different fields.
So I create 3 tables: professors, students and authentication,
"professors" will have all the personal data from professors.
"students" will have all the personal data from students.
authentication will have the username and password from all users.
How can i link authentication table to both professors and students
tables so when the user logins i get the data from that user, either a
professor or student?
And is the right way to do this?
I am using SQL 2005 and Asp.Net 2.0
Thanks,
MiguelOn Wed, 21 Dec 2005 23:10:00 +0000, Miguel Dias Moura wrote:

>Hello,
>In my web site I have 2 types of users: students and professors.
>All users need to login but the personal information for each user type
>has different fields.
>So I create 3 tables: professors, students and authentication,
>"professors" will have all the personal data from professors.
>"students" will have all the personal data from students.
>authentication will have the username and password from all users.
>How can i link authentication table to both professors and students
>tables so when the user logins i get the data from that user, either a
>professor or student?
>And is the right way to do this?
>I am using SQL 2005 and Asp.Net 2.0
>Thanks,
>Miguel
Hi Miguel,
I would use one Persons table to hold information that applies to both
professors and students. Specific information then goes in the students
and the professors tables.
Login information could go in the Persons table, but is probably better
placed in a seperate table (for reasons of security, but also for
flexibility - maybe, someone will someday need two seperate accounts,
then you'll be ready for it).
The tables Persons, Students and Professors all have the same primary
key; this same column is also foreign key in the Students and Professors
table, in both cases referencing the Persons table.
The Logins table has userid as primary key (of course) and has also a
foreign key that referenced the Persons table.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)

CPU messages in log

Running x64 AMD procs and receive the following types of messages in our SQL
log
The time stamp counter of CPU on scheduler id 3 is not synchronized with
other CPUs.
I have seen a lot of postings about this, but have not been lucky to stop
it.
Do we know what the latest is on this and what the actual fix is if any ?
ThanksSee http://support.microsoft.com/kb/931279
Linchi
"Hassan" wrote:
> Running x64 AMD procs and receive the following types of messages in our SQL
> log
> The time stamp counter of CPU on scheduler id 3 is not synchronized with
> other CPUs.
> I have seen a lot of postings about this, but have not been lucky to stop
> it.
> Do we know what the latest is on this and what the actual fix is if any ?
> Thanks
>
>|||See the workaround section of this article:
http://support.microsoft.com/kb/931279
HTH,
Plamen Ratchev
http://www.SQLStudio.com|||we tried those and they still pop up.
Have you guys used those workarounds and made them disappear ?
Its not annoying so far, but was curious to know.
"Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
news:B633FD5B-849E-45AD-8F4A-6F1BADEC302A@.microsoft.com...
> See the workaround section of this article:
> http://support.microsoft.com/kb/931279
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com|||I have seen this happen only once on a development machine and disabling CPU
frequency variation in BIOS did the trick.
Plamen Ratchev
http://www.SQLStudio.com|||We never tried to make the messages go away since having the messages is a
minor annoyance. I probably won't try it unless the clock drift starts to
cause real problem for the SQL trace metrics.
Linchi
"Hassan" wrote:
> we tried those and they still pop up.
> Have you guys used those workarounds and made them disappear ?
> Its not annoying so far, but was curious to know.
> "Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
> news:B633FD5B-849E-45AD-8F4A-6F1BADEC302A@.microsoft.com...
> > See the workaround section of this article:
> > http://support.microsoft.com/kb/931279
> >
> > HTH,
> >
> > Plamen Ratchev
> > http://www.SQLStudio.com
>
>