![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 ? |
#3
| |||
| |||
|
|
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 |
#4
| |||
| |||
|
|
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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |