December 18, 2002 at 9:07 am
Recently, I notice several of our Production SQL7 w/ SP4 on NT4 has a 'LastBatch' timestamp of '1/1/1900' but the 'LoginTime' timestamp is current. Is this a Y2K bug? Has anyone seen or know what this is all about? thanx...
December 18, 2002 at 10:09 am
Don't have any of those.
My NT4 (SP6), SQL 7, SP3 box doesn't do this.
Steve Jones
December 18, 2002 at 10:13 am
I do believe all it means is the connection was made but no type of query or SQL Sommand has been run yet. Once one occurrs you should see an update. If not then you could have an install issue.
December 18, 2002 at 10:43 am
Antares686,'s statement is correct. The system table containing this information has to have some date value to populate, so uses the default of 1/1/1900. Once a batch is run, the date gets updated and you'll quit seeing it that way.
December 18, 2002 at 12:40 pm
What do mean by having an install issue? And if this is just a system default, is there anywhere I can fix it or just ignore and move on? I check the SysProcesses table from the master db but not very helping.
December 18, 2002 at 1:28 pm
The date value is held in the sysprocesses table, in the last_batch column. The times I've seen the situation you describe, was after a fresh install, or apply of a service patch, and once the thread performs an action, it's updated and the 1/1/1900 is replaced with the time of the batch. Restarting the server should update it, I believe, but couldn't swear to it. I've never worried about it after finding out what it was that first time.
Don't rule out what Antares said about the Install problem, though. If it doesn't update once a batch is run on the process, he is right. Again.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply