How can i check the time the Database is using?

My SQL 2000 server seems to be logging data an hour early, the Windows 2003
time is correct though. What steps should I take to find out what is
happening. I'm in the UK and we have to change our clocks for day light,
but these are all set to automatically adjust clocks.
Should it be using the local server time?I had a discussion with an Microsoft Consultant about this, from what I
remember. He said SQL server doesn't have time-zone setting it grabs it's
information from the Server its running on. So maybe check the settings on
the server ..
Ref Link: http://support.microsoft.com/?kbid=928388
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Gonzo" wrote:

> My SQL 2000 server seems to be logging data an hour early, the Windows 200
3
> time is correct though. What steps should I take to find out what is
> happening. I'm in the UK and we have to change our clocks for day light,
> but these are all set to automatically adjust clocks.
> Should it be using the local server time?
>|||SQL Server gets it date and time from the server itself thru an internal
winapi call. So if the server is correct then so is SQL Server. If you are
supplying the datetimes via the client as a value in the insert statement
then the client may be an hour behid. Can you post the actual code that is
doing the inserts?
Andrew J. Kelly SQL MVP
"Gonzo" <no@.no123.com> wrote in message
news:CF181373-2F00-4EE0-9B7F-6EAC76C705BE@.microsoft.com...
> My SQL 2000 server seems to be logging data an hour early, the Windows
> 2003 time is correct though. What steps should I take to find out what is
> happening. I'm in the UK and we have to change our clocks for day light,
> but these are all set to automatically adjust clocks.
> Should it be using the local server time?sql

How can i check the time the Database is using?

My SQL 2000 server seems to be logging data an hour early, the Windows 2003
time is correct though. What steps should I take to find out what is
happening. I'm in the UK and we have to change our clocks for day light,
but these are all set to automatically adjust clocks.
Should it be using the local server time?I had a discussion with an Microsoft Consultant about this, from what I
remember. He said SQL server doesn't have time-zone setting it grabs it's
information from the Server its running on. So maybe check the settings on
the server ..
Ref Link: http://support.microsoft.com/?kbid=928388
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Gonzo" wrote:
> My SQL 2000 server seems to be logging data an hour early, the Windows 2003
> time is correct though. What steps should I take to find out what is
> happening. I'm in the UK and we have to change our clocks for day light,
> but these are all set to automatically adjust clocks.
> Should it be using the local server time?
>|||SQL Server gets it date and time from the server itself thru an internal
winapi call. So if the server is correct then so is SQL Server. If you are
supplying the datetimes via the client as a value in the insert statement
then the client may be an hour behid. Can you post the actual code that is
doing the inserts?
--
Andrew J. Kelly SQL MVP
"Gonzo" <no@.no123.com> wrote in message
news:CF181373-2F00-4EE0-9B7F-6EAC76C705BE@.microsoft.com...
> My SQL 2000 server seems to be logging data an hour early, the Windows
> 2003 time is correct though. What steps should I take to find out what is
> happening. I'm in the UK and we have to change our clocks for day light,
> but these are all set to automatically adjust clocks.
> Should it be using the local server time?

Hot Swapping Cluster Nodes

We are trying to deploy a two node Active / Passive cluster. But would like to test / ascertain the necessary steps to hot-swap one of the nodes should the need arise. The scenario being that the node is unavailable for longer than the time deemed accep
table to have a node down.
We would aim to bring a spare node into the cluster, install it wil binaries and allow it to replace the original failover node, whilst the original failover node was being fixed.
However, on initial testing SQL Server seems to have problems with this, and basically, for a node to be part of a cluster it must be present at the initial install.
Is there a way around this?
You can have the node ready to join the cluster but it must actually be in
the cluster before SQL can install to it. Once the node is in the cluster,
you can install SQL and any service packs/hotfixes without taking SQL
offline. BOL has the procedure to replace a failed node in a SQL cluster.
So, you can't do exactly what you want but you can get very close.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Beverley" <Bev.Brindle@.barclays.co.uk> wrote in message
news:B41DAA45-424E-4970-ABF9-16243D76CEDC@.microsoft.com...
> We are trying to deploy a two node Active / Passive cluster. But would
like to test / ascertain the necessary steps to hot-swap one of the nodes
should the need arise. The scenario being that the node is unavailable for
longer than the time deemed acceptable to have a node down.
> We would aim to bring a spare node into the cluster, install it wil
binaries and allow it to replace the original failover node, whilst the
original failover node was being fixed.
> However, on initial testing SQL Server seems to have problems with this,
and basically, for a node to be part of a cluster it must be present at the
initial install.
> Is there a way around this?
>
|||Thanks, we're going into a phase of strategic testing for the Cluster, and this is very useful.
Thanks alot.
Bev