October 8, 2003 at 10:08 am
I am using SQL Server 2000 (sp3) on window 2000. From the testing, it shows that if I changed the PC clock backward to before Y2K (e.g. Jan 1, 1999, 3 p.m.), and then slowly changing it forward again(e.g. Aug 25, 2002, 9 a.m., Dec 31, 2002, 11PM, and so on.), SQL Server will take more and more CPU usage. (Based on the same amount of activity on Database I/O)
Does anyone seems this before?
If you open task manager and look at the CPU usage History window, before the time change, you will see a constant stream of small peak at 20% cpu usage. After the time change, the CPU usage become a constant stream of small peak at >80%.
And the sqlservr.exe is the heaviest process running.
by Ben.
October 10, 2003 at 9:40 am
O.k. how about an easier question.
Does anyone change system time on their SQL server? (Adjust time for whatever reason...)
And does anyone detect any strange problem after that?
I know this is strange enough to say that this might be related to sql SP problem. And I couldn't deny that this is possible too.. 8-( That's why I want to narrow down the cause...
Some SPs using default value on column by converting date to string
[convert(varchar(23),getdate(),121)] but we never store date directly in our table.
I didn't have a chance to use profiler since I wasn't there when it happened. And I failed to recreate the similar problem even with the same steps the tester does...
All in all, it points to SQL server probelm rather than my database and SPs problem... (If that is the case, I am doom....)
Any help would be appreciated.
by Ben.
October 10, 2003 at 10:44 am
I have had to resync the time periodically and noticed that with SQL 7 there seemed to be a lag with SQLs time vs Windows new time (3 to 20 sec before synced). 2000 seems to be shorter if any. As for what you have seen I have not tested.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply