Is this possible? SQL Server 2000 Write times

No timezone discrepancy, they did it in our labs here at our institution. I
didn't think so, but had to ask. What logs would i search and what would I
look for?

Shawn Ferguson wrote:
> I created an online application for one of our educational programs.
> The data is inserted via website entry -> client side validation ->
> stored procedure -> database. Given a table stucture as follows, if 100
> or even 1000 people applied at the exact same time using an online
> application, what is the maximum time interval that could separate each
> record. How long would SQL Server 2000 generally take to insert each
> record into the database. The problem is that each year, only the top
> 100 students are admitted in the program, but there is one student who
> says they applied at 9:00 am and their record insert time shows 9:59am.
> There are records before it and after it that shows times like 9:58,
> 9:58, 9:59: 10:00, 10:00, etc. Could it really take SQL Server 59
> minutes to actually write the record if 1000 people hit the database at
> the same time? Please help, they want to get counsil involved.
>
> ApplicantID int primary key identity
> SSN varchar(11)
> FirstName varchar(30)
> LastName varchar(50)indexed
> Address varchar (50)
> City varchar (50)
> State char (2)
> Zip varchar (11)
> Phone varchar (20)
> Email varchar (50)
> dateEntered smalldatetime
I would not expect that sort of delay. 9:00am/9:59am, could there be a
time zone discrepancy? Can you use your website logs to determine when
the user made their submission?Shawn Ferguson wrote:
> No timezone discrepancy, they did it in our labs here at our
> institution. I didn't think so, but had to ask. What logs would i
> search and what would I look for?
>
That would be a question for your web server folks. Your web server
should maintain logs of the visits to the web site.|||> No timezone discrepancy, they did it in our labs here at our institution.
That doesn't mean that some computer along the way doesn't have an incorrect
timezone and/or system time specified!

Is this a new SQL BUG

For the last two days, I have been checking my SQL Server error logs and this is what I find common on all the SQL Servers, with Audit Login options ON: Login failed for 'A', Login failed for 'B', Login Failed for 'C'..all the way to the last login.
For each login defined in the SQL Server, I'm finding that the error message is getting generated 18 times. My guess is that someone is trying to run some kind of code.

Any experience?Make sure you don't have any easily guessable accounts, and DEFINITELY, - change your SA password. This is not a bug (unless you don't have the latest security patch from M$, in which case it is and has been fixed). Whatch out, someone is after your server.