dbTalk Databases Forums  

SQL 2005 Error Log times appear to be in future

comp.databases.ms-sqlserver comp.databases.ms-sqlserver


Discuss SQL 2005 Error Log times appear to be in future in the comp.databases.ms-sqlserver forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mark D Powell
 
Posts: n/a

Default SQL 2005 Error Log times appear to be in future - 12-23-2010 , 08:24 AM






If I query the database select getdate I get 2010-12-23 09:08:17.330
but I have entries in the Error log like (User name and server name
edited)

Quote:
Date 12/23/2010 9:24:25 AM
Log SQL Server (Current - 12/23/2010 9:24:00 AM)

Source Logon

Message
Login failed for user 'xxx'. [CLIENT: <local machine>]
<<


How is this possible? What could be wrong?

Server Edition SP Version Resrc_Ver Resrc_Last_Updt_Tm
Svr_Dflt_Collation
XXXXXXXX Standard Edition SP3 9.00.4035.00 9.00.4035 NULL
SQL_Latin1_General_CP1_CI_AS


-- Mark D Powell --

Reply With Quote
  #2  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: SQL 2005 Error Log times appear to be in future - 12-23-2010 , 04:26 PM






Mark D Powell (Mark.Powell2 (AT) hp (DOT) com) writes:
Quote:
If I query the database select getdate I get 2010-12-23 09:08:17.330
but I have entries in the Error log like (User name and server name
edited)


Date 12/23/2010 9:24:25 AM
Log SQL Server (Current - 12/23/2010 9:24:00 AM)

Source Logon

Message
Login failed for user 'xxx'. [CLIENT: <local machine>]

That seems like something you have culled from Object Explorer. Am I
right?

I don't want to belittle you or anything, but did you double-check that
the query window and Object Explorer are connected to the same server?



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

Reply With Quote
  #3  
Old   
Mark D Powell
 
Posts: n/a

Default Re: SQL 2005 Error Log times appear to be in future - 12-30-2010 , 01:21 PM



On Dec 23, 5:26*pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:
Quote:
Mark D Powell (Mark.Powe... (AT) hp (DOT) com) writes:

If I query the database select getdate I get 2010-12-23 09:08:17.330
but I have entries in the Error log like *(User name and server name
edited)

Date * * * * *12/23/2010 9:24:25 AM
Log * * * * *SQL Server (Current - 12/23/2010 9:24:00 AM)

Source * * * * *Logon

Message
Login failed for user 'xxx'. [CLIENT: <local machine>]


That seems like something you have culled from Object Explorer. Am I
right?

I don't want to belittle you or anything, but did you double-check that
the query window and Object Explorer are connected to the same server?

--
Erland Sommarskog, SQL Server MVP, esq... (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
Yes, I am certain that the posted information is for the same SQL
Server since the messages were copied from the current SQL Server
Error Log accessed via SQL Server Management Studio running on the
database server. No other instances are configured to the tool. I
just copied and pasted from the bottom of the log display, that is, I
double clicked a log entry and copiled from the bottom portion of the
window that SSMS opens.

I have never seen this before. This is a small database where the
same table rows are updated constantly. Say about 20M of data with up
to 400M of change data (transaction log) per hour.

I have another 20 or so SQL Server installations running and I have
never seen this issue on any of them. This installation is running
under VM but then agains so are several of my other systems.

I have been told both systems are fully patched (VM and Windows).

Any ideas as to how/why the error log is showing errors in the future?

HTH -- Mark D Powell --

Reply With Quote
  #4  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: SQL 2005 Error Log times appear to be in future - 12-30-2010 , 02:56 PM



Mark D Powell (Mark.Powell2 (AT) hp (DOT) com) writes:
Quote:
Yes, I am certain that the posted information is for the same SQL
Server since the messages were copied from the current SQL Server
Error Log accessed via SQL Server Management Studio running on the
database server. No other instances are configured to the tool. I
just copied and pasted from the bottom of the log display, that is, I
double clicked a log entry and copiled from the bottom portion of the
window that SSMS opens.
Well, you confirmed my assumption from where you got the message.

Next time you see this, run xp_readerrorlog from the query window,
and see if you can see the same error message.

Quote:
I have another 20 or so SQL Server installations running and I have
never seen this issue on any of them. This installation is running
under VM but then agains so are several of my other systems.
One possibility is that the clock had drifted, and just had been
corrected. I don't know common this is with server-class VMs, but I
remember I had severe problems with the time get very fast or slow in
my VMs a couple of years back. I think the problem is related to
power-saving features in the CPU and/or BIOS.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

Reply With Quote
  #5  
Old   
HeadHunter iSpace
 
Posts: n/a

Default Re: SQL 2005 Error Log times appear to be in future - 01-09-2011 , 02:07 AM



Database Developer: This is a Permanent position in Santa Barbara, CA

The client is OK with telecommuting to some extent.

General Summary:

Responsibilities include:
Working with Data Warehouse Architect and application designers to
identify the business requirements and/or redesign databases as needed
for high scalability applications.
OLTP database design, development, performance tuning and
troubleshooting

Qualifications:

Required:
5+ years OLTP experience
Strong experience in designing OLTP databases for high traffic
applications
OLTP database performance tuning and troubleshooting skills for
Microsoft SQL Server 2005/2008 environment
Solid understanding of relational databases
Microsoft SQL Server 2005/2008 experience
Ability to communicate effectively with both business and technical
users.
Excellent written and oral communication skills.
Ability to work independently with minimal direction.
Superior organizational skills.
Minimum 5+ years of experience in a data architect role

Desirable:
Microsoft .Net Technologies
Familiarity with ETL Concepts
Experience with SSIS (SQL Server Integration Services), and SSRS (SQL
Server Reporting Services)
Bachelors Degree – Engineering, Computer Science or related field




Please email me a copy of your resume in word.doc format and feel free
to contact me on 310 448 2887 / roni.thomas (AT) ispace (DOT) com


Looking forward to hearing from you.


Thanks & Regards,
Roni Thomas
Professional Staff Recruiter
iSpace Inc
Learn: www.ispace.com | Direct: 310 448 2887 | Fax: 310 563 3801
Address: 2141 Rosecrans Ave, El Segundo, California 90245

Reply With Quote
  #6  
Old   
Mark D Powell
 
Posts: n/a

Default Re: SQL 2005 Error Log times appear to be in future - 01-20-2011 , 10:40 AM



On Dec 30 2010, 3:56*pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se>
wrote:
Quote:
Mark D Powell (Mark.Powe... (AT) hp (DOT) com) writes:

Yes, I am certain that the posted information is for the same SQL
Server since the messages were copied from the current SQL Server
Error Log accessed via SQL Server Management Studio running on the
database server. *No other instances are configured to the tool. *I
just copied and pasted from the bottom of the log display, that is, I
double clicked a log entry and copiled from the bottom portion of the
window that SSMS opens.

Well, you confirmed my assumption from where you got the message.

Next time you see this, run xp_readerrorlog from the query window,
and see if you can see the same error message.

I have another 20 or so SQL Server installations running and I have
never seen this issue on any of them. *This installation is running
under VM but then agains so are several of my other systems.

One possibility is that the clock had drifted, and just had been
corrected. I don't know common this is with server-class VMs, but I
remember I had severe problems with the time get very fast or slow in
my VMs a couple of years back. I think the problem is related to
power-saving features in the CPU and/or BIOS.

--
Erland Sommarskog, SQL Server MVP, esq... (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
Followup. I found out we saw the same future date issue in some
application logs that run on another server from database machine but
which communicates through a an application server running under VM.

We migrated the database to a new physical server and have not seen a
repeat of the problem.

HTH -- Mark D Powell --

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.