dbTalk Databases Forums  

What are the effects of changing the system clock on SQL Server ?

microsoft.public.sqlserver.server microsoft.public.sqlserver.server


Discuss What are the effects of changing the system clock on SQL Server ? in the microsoft.public.sqlserver.server forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
DDLooks
 
Posts: n/a

Default What are the effects of changing the system clock on SQL Server ? - 12-30-2005 , 12:49 PM






Hello,

One of our Windows 2000 Servers is running SQL 2000 SP3. We need to advance
the system date on the machine to perform some application testing. After
testing is complete, we would fall back to the current date/time. How would
this affect SQL Server operation and database recoverability ?

Any help would be greatly appreciated.

Thank You.

Reply With Quote
  #2  
Old   
Dejan Sarka
 
Posts: n/a

Default Re: What are the effects of changing the system clock on SQL Server ? - 12-30-2005 , 01:37 PM






Quote:
One of our Windows 2000 Servers is running SQL 2000 SP3. We need to
advance
the system date on the machine to perform some application testing. After
testing is complete, we would fall back to the current date/time. How
would
this affect SQL Server operation and database recoverability ?

If you think of the Transaction Log, then don't worry. The sequence is
maintained by a Log Sequence Number, not by datetime.
But maybe some of your apps use datetime data (maybe with GETDATE function)
for some purpose, and they might have some problems.

--
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com




Reply With Quote
  #3  
Old   
DDLooks
 
Posts: n/a

Default Re: What are the effects of changing the system clock on SQL Serve - 12-30-2005 , 02:27 PM



Thank you very much for the clarification.

"Dejan Sarka" wrote:

Quote:
One of our Windows 2000 Servers is running SQL 2000 SP3. We need to
advance
the system date on the machine to perform some application testing. After
testing is complete, we would fall back to the current date/time. How
would
this affect SQL Server operation and database recoverability ?


If you think of the Transaction Log, then don't worry. The sequence is
maintained by a Log Sequence Number, not by datetime.
But maybe some of your apps use datetime data (maybe with GETDATE function)
for some purpose, and they might have some problems.

--
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com




Reply With Quote
  #4  
Old   
Tibor Karaszi
 
Posts: n/a

Default Re: What are the effects of changing the system clock on SQL Serve - 12-31-2005 , 01:19 AM



But you will mess up your RESTORE-ability. If you do transaction log backup and expect to restore to
a certain point in time (STOPAT parameter to the RESTORE command), you will have a "dead spot" in
the transaction log when you go backwards in time on the machine.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/


"DDLooks" <DDLooks (AT) discussions (DOT) microsoft.com> wrote

Quote:
Thank you very much for the clarification.

"Dejan Sarka" wrote:

One of our Windows 2000 Servers is running SQL 2000 SP3. We need to
advance
the system date on the machine to perform some application testing. After
testing is complete, we would fall back to the current date/time. How
would
this affect SQL Server operation and database recoverability ?


If you think of the Transaction Log, then don't worry. The sequence is
maintained by a Log Sequence Number, not by datetime.
But maybe some of your apps use datetime data (maybe with GETDATE function)
for some purpose, and they might have some problems.

--
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com





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 - 2013, Jelsoft Enterprises Ltd.