db error: savings

Showing posts with label savings. Show all posts

Tuesday, March 27, 2012

Daylight Savings Time error SQL SERVER 2000

Hi all.
I used tzedit to update the daylight savings time setting on my windows 2000
server.. Now, when I run any of my reports, I get this error:
"An internal error occurred on the report server. See the error log for more
details. (rsInternalError) Get Online Help
Specified argument was out of the range of valid values. Parameter name:
date "
Does anyone have or heard of a solution?Maybe there's a patch for sql 2000, i fixed my win 2003 server and didn't
encounter this issue with my SQL 2005.
"jereviscious" <here@.there.com> wrote in message
news:eEmN81vaHHA.4396@.TK2MSFTNGP06.phx.gbl...
> Hi all.
> I used tzedit to update the daylight savings time setting on my windows
> 2000 server.. Now, when I run any of my reports, I get this error:
> "An internal error occurred on the report server. See the error log for
> more details. (rsInternalError) Get Online Help
> Specified argument was out of the range of valid values. Parameter name:
> date "
> Does anyone have or heard of a solution?
>|||Since Windows 2000 server isn't officially supported any more, microsoft
didn't release a patch. They did, however, issue this knowledge base
article, which I followed..
http://support.microsoft.com/kb/914387
and everything else appears to be working fine. All of my servers are
reporting the correct time and date. However, SQL SERVER is giving me this
problem, and I have no idea how to go about fixing it...
"Julien Bonnier" <julien@.m0851.com> wrote in message
news:OM3DXKwaHHA.3584@.TK2MSFTNGP02.phx.gbl...
> Maybe there's a patch for sql 2000, i fixed my win 2003 server and didn't
> encounter this issue with my SQL 2005.
>
> "jereviscious" <here@.there.com> wrote in message
> news:eEmN81vaHHA.4396@.TK2MSFTNGP06.phx.gbl...
>> Hi all.
>> I used tzedit to update the daylight savings time setting on my windows
>> 2000 server.. Now, when I run any of my reports, I get this error:
>> "An internal error occurred on the report server. See the error log for
>> more details. (rsInternalError) Get Online Help
>> Specified argument was out of the range of valid values. Parameter name:
>> date "
>> Does anyone have or heard of a solution?
>

Daylight Savings Time error SQL SERVER 2000

Hi all.

After DST change (US/Canada), when I run any of my reports, I get this error:

"An internal error occurred on the report server. See the error log for more
details. (rsInternalError) Get Online Help
Specified argument was out of the range of valid values. Parameter name:
date "

Does anyone have or heard of a solution?

Thank you!

What is your date format, MM/DD/YYYY or DD/MM/YYYY?|||

Try installing SQL Server 2005 (and restore the databases on it) and run the reports.

Shyam

|||mm/dd/yyyy|||

I cannot give up using SQL Server 2000 just because of this issue

|||

I do not think you need to give up on SQL 2000 for this.

Can you share the script where you pass in the parameters?

|||<Value>=Globals!ReportName &" between " & Parameters!startdate.Value & " & " & Parameters!enddate.Value</Value>
...
<ReportParameters>
<ReportParameter Name="startdate">
<DataType>DateTime</DataType>
<DefaultValue>
<Values>
<Value>=CDate(cstr(year(Now())) + "/" + "01" + "/" + "01" + " 00:00:01")</Value>
</Values>
</DefaultValue>
<Prompt>Start Date-Time (MM/DD/YYYY HH:MM:SS AM or PM)</Prompt>
</ReportParameter>
<ReportParameter Name="enddate">
<DataType>DateTime</DataType>
<DefaultValue>
<Values>
<Value>=CDate(cstr(year(Now())) + "/" + cstr(month(now())) + "/" + cstr(day(now())) + " 23:59:59")</Value>
</Values>
</DefaultValue>
<Prompt>End Date-Time (MM/DD/YYYY HH:MM:SS AM or PM)</Prompt>
</ReportParameter>
<ReportParameter Name="Team">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>%</Value>
</Values>
</DefaultValue>
<Prompt>Enter a Team with % as a wildcard character i.e. %Cust%</Prompt>
</ReportParameter>
</ReportParameters>|||

I do not see any problems in the script.

Please take a look at the server log and here's something for reference. If possible, please post what you can find from the log. HTH.

http://blogs.msdn.com/jgalla/archive/2006/12/05/diagnosing-rsinternalcatalogexception.aspx

|||

Problem was resolved after power outage ;) and server restart.

|||Reboot is always the "best" solution for all MS issues.

Daylight Savings Time changes coming in 2007

I apologize ahead of time if this has been covered. I tried searching but found only the OS specific response to my question (http://www.microsoft.com/windows/timezone/dst2007.mspx).

With the coming changes to DST in 2007, is there -- or is there even a need to -- patch either SQL Server 2005 or 2000 to account for those changes?

Doug,

have you received any responses yet to this question? I too have the same question and have only found the page that you already linked too as well. Please let me know if you find out anything.

Thanks,

Chad (chad.smith@.lucasfilm.com)

|||

There has been a lot discussion in the SQL org about this. To date, we have determined SQL is pulling all dates from the OS so no updates from SQL are needed. If we eventually find a problem we'll definitely release an update.

Thanks,

Peter Saddow

|||What about releasing a "rebasing" utility like the one issued for Outlook and Exchange?|||How about date arithmetic? Wouldn't that be affected by this change?|||

Consider this:

You have a calculation that comes up with a date/time in the future with a result as UTC value. Let's assume that future date falls somewhere between 3/11, 2AM and 4/1 2AM. This UTC value must be wrong because you haven't applied any DST related patches yet. If you store this value for future use, it will be wrong.

You apply OS DST patch.

You do the same calculation as before. This time, UTC will not be different by just the amount of time that passed between two calculations. Extra hour will be added because that is what the patch corrects.

The first value is still wrong and something must be done about it. That's why Microsoft issued "rebasing" tool for Outlook and Exchange.

It's not enough to say: "you'll be fine as soon as you patch OS". This doesn't fix bad dates that are being calculated and stored today.

I'm still waiting for someone to explain to me why the above line of thinking doesn't apply to SQL Server (or any other Windows application).

All you MVPs out there?

|||The anwser to your question, is that SQL server itself is not responsible for the data being stored in it. So any application that is storing its data in SQL server will need to come out with an update to compensate for the change in Daylight Savings Time if the developer deems there to be an issue, where the dates and times that are stored in it would be affected.|||

By now SQL Server has been added to the list of Microsoft products affected by DST change. It will requre patching. That was the original issue that started this thread.

I don't know how SQL Server scheduler stores dates but some schedulers have been affected if they store dates as UTC (or GMT). For me, jury is still out on this.

|||

Here is some SQL script that I’ve come up with to calculate the daylight savings for -2006 and +2007.

http://2pttechnology.com/Web/forums/thread/19.aspx

|||I am a computer illiterazzi. I just want a simple, no hassle patch to fix my computer which is a Windows XP 2002 Service Pack. There are so many selections, I am terrified I will pick the wrong one and screw my expensive new computer. I don't use outlook to my knowledge. I can't find that the daylight savings patch has been downloaded automatically. There are a gadzillion downloads in my computer record. Please help. Thanks.sql

Daylight Savings Time changes coming in 2007

I apologize ahead of time if this has been covered. I tried searching but found only the OS specific response to my question (http://www.microsoft.com/windows/timezone/dst2007.mspx).

With the coming changes to DST in 2007, is there -- or is there even a need to -- patch either SQL Server 2005 or 2000 to account for those changes?

Doug,

have you received any responses yet to this question? I too have the same question and have only found the page that you already linked too as well. Please let me know if you find out anything.

Thanks,

Chad (chad.smith@.lucasfilm.com)

|||

Thanks,

Peter Saddow

|||What about releasing a "rebasing" utility like the one issued for Outlook and Exchange?|||How about date arithmetic? Wouldn't that be affected by this change?|||

Consider this:

You apply OS DST patch.

The first value is still wrong and something must be done about it. That's why Microsoft issued "rebasing" tool for Outlook and Exchange.

It's not enough to say: "you'll be fine as soon as you patch OS". This doesn't fix bad dates that are being calculated and stored today.

I'm still waiting for someone to explain to me why the above line of thinking doesn't apply to SQL Server (or any other Windows application).

All you MVPs out there?

By now SQL Server has been added to the list of Microsoft products affected by DST change. It will requre patching. That was the original issue that started this thread.

I don't know how SQL Server scheduler stores dates but some schedulers have been affected if they store dates as UTC (or GMT). For me, jury is still out on this.

|||

Here is some SQL script that I’ve come up with to calculate the daylight savings for -2006 and +2007.

http://2pttechnology.com/Web/forums/thread/19.aspx

Daylight Savings Time changes coming in 2007

I apologize ahead of time if this has been covered. I tried searching but found only the OS specific response to my question (http://www.microsoft.com/windows/timezone/dst2007.mspx).

With the coming changes to DST in 2007, is there -- or is there even a need to -- patch either SQL Server 2005 or 2000 to account for those changes?

Doug,

have you received any responses yet to this question? I too have the same question and have only found the page that you already linked too as well. Please let me know if you find out anything.

Thanks,

Chad (chad.smith@.lucasfilm.com)

|||

Thanks,

Peter Saddow

|||What about releasing a "rebasing" utility like the one issued for Outlook and Exchange?|||How about date arithmetic? Wouldn't that be affected by this change?|||

Consider this:

You apply OS DST patch.

The first value is still wrong and something must be done about it. That's why Microsoft issued "rebasing" tool for Outlook and Exchange.

It's not enough to say: "you'll be fine as soon as you patch OS". This doesn't fix bad dates that are being calculated and stored today.

I'm still waiting for someone to explain to me why the above line of thinking doesn't apply to SQL Server (or any other Windows application).

All you MVPs out there?

By now SQL Server has been added to the list of Microsoft products affected by DST change. It will requre patching. That was the original issue that started this thread.

I don't know how SQL Server scheduler stores dates but some schedulers have been affected if they store dates as UTC (or GMT). For me, jury is still out on this.

|||

Here is some SQL script that I’ve come up with to calculate the daylight savings for -2006 and +2007.

http://2pttechnology.com/Web/forums/thread/19.aspx

Sunday, March 25, 2012

Daylight Savings Time changes coming in 2007

I apologize ahead of time if this has been covered. I tried searching but found only the OS specific response to my question (http://www.microsoft.com/windows/timezone/dst2007.mspx).

With the coming changes to DST in 2007, is there -- or is there even a need to -- patch either SQL Server 2005 or 2000 to account for those changes?

Doug,

have you received any responses yet to this question? I too have the same question and have only found the page that you already linked too as well. Please let me know if you find out anything.

Thanks,

Chad (chad.smith@.lucasfilm.com)

|||

Thanks,

Peter Saddow

|||What about releasing a "rebasing" utility like the one issued for Outlook and Exchange?|||How about date arithmetic? Wouldn't that be affected by this change?|||

Consider this:

You apply OS DST patch.

The first value is still wrong and something must be done about it. That's why Microsoft issued "rebasing" tool for Outlook and Exchange.

It's not enough to say: "you'll be fine as soon as you patch OS". This doesn't fix bad dates that are being calculated and stored today.

I'm still waiting for someone to explain to me why the above line of thinking doesn't apply to SQL Server (or any other Windows application).

All you MVPs out there?

By now SQL Server has been added to the list of Microsoft products affected by DST change. It will requre patching. That was the original issue that started this thread.

I don't know how SQL Server scheduler stores dates but some schedulers have been affected if they store dates as UTC (or GMT). For me, jury is still out on this.

|||

Here is some SQL script that I’ve come up with to calculate the daylight savings for -2006 and +2007.

http://2pttechnology.com/Web/forums/thread/19.aspx

Daylight Savings Time changes coming in 2007

I apologize ahead of time if this has been covered. I tried searching but found only the OS specific response to my question (http://www.microsoft.com/windows/timezone/dst2007.mspx).

With the coming changes to DST in 2007, is there -- or is there even a need to -- patch either SQL Server 2005 or 2000 to account for those changes?

Doug,

have you received any responses yet to this question? I too have the same question and have only found the page that you already linked too as well. Please let me know if you find out anything.

Thanks,

Chad (chad.smith@.lucasfilm.com)

|||

Thanks,

Peter Saddow

|||What about releasing a "rebasing" utility like the one issued for Outlook and Exchange?|||How about date arithmetic? Wouldn't that be affected by this change?|||

Consider this:

You apply OS DST patch.

The first value is still wrong and something must be done about it. That's why Microsoft issued "rebasing" tool for Outlook and Exchange.

It's not enough to say: "you'll be fine as soon as you patch OS". This doesn't fix bad dates that are being calculated and stored today.

I'm still waiting for someone to explain to me why the above line of thinking doesn't apply to SQL Server (or any other Windows application).

All you MVPs out there?

By now SQL Server has been added to the list of Microsoft products affected by DST change. It will requre patching. That was the original issue that started this thread.

I don't know how SQL Server scheduler stores dates but some schedulers have been affected if they store dates as UTC (or GMT). For me, jury is still out on this.

|||

Here is some SQL script that I’ve come up with to calculate the daylight savings for -2006 and +2007.

http://2pttechnology.com/Web/forums/thread/19.aspx

Daylight Savings Time Change in 2007

Is there a patch available for SQL Server 2000 to address the 2007 change in
daylight savings time?
Thank you very much in advance for your help.
Thanks,
Sally
Sally wrote:
> Is there a patch available for SQL Server 2000 to address the 2007 change in
> daylight savings time?
> Thank you very much in advance for your help.
> Thanks,
> Sally
SQL Server takes the current date and time from the OS. For details
see:
http://www.microsoft.com/windows/timezone/dst2007.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
sql

Daylight Savings Time Change in 2007

Is there a patch available for SQL Server 2000 to address the 2007 change in
daylight savings time?
Thank you very much in advance for your help.
Thanks,
SallySally wrote:
> Is there a patch available for SQL Server 2000 to address the 2007 change
in
> daylight savings time?
> Thank you very much in advance for your help.
> Thanks,
> Sally
SQL Server takes the current date and time from the OS. For details
see:
http://www.microsoft.com/windows/timezone/dst2007.mspx
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

Daylight Savings Time Change

Can you tell me what kind of impact we are looking at from SQL server point
of view for the daylight savings time change that is happening soon.
SQL 7.0
SQL 2000
SQL 2005
Will there be a hot fix?
ThanksSQL Server takes its date and time from Windows. There is no hot fix
required for SQL Server, since the DST change is dealt with at the operating
system layer.
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:17E4EF33-1859-4897-89D0-658979BF7E8C@.microsoft.com...
> Can you tell me what kind of impact we are looking at from SQL server
> point
> of view for the daylight savings time change that is happening soon.
> SQL 7.0
> SQL 2000
> SQL 2005
> Will there be a hot fix?
> Thanks|||Take a look into this URL:-
http://www.microsoft.com/windows/timezone/dst2007.mspx
Thanks
Hari
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:17E4EF33-1859-4897-89D0-658979BF7E8C@.microsoft.com...
> Can you tell me what kind of impact we are looking at from SQL server
> point
> of view for the daylight savings time change that is happening soon.
> SQL 7.0
> SQL 2000
> SQL 2005
> Will there be a hot fix?
> Thanks|||"Aaron Bertrand [SQL Server MVP]" wrote:

> SQL Server takes its date and time from Windows. There is no hot fix
> required for SQL Server, since the DST change is dealt with at the operati
ng
> system layer.
Technically, not quite. SQL Server Notification Services 2.0 RTM and SP1,
and SQL Server Notification Services 2005 SP1 are affected. They store time
zone info in a table NSTimeZoneDstOffsets. A fix will be required.
Linchi

Daylight Savings Time Change

Can you tell me what kind of impact we are looking at from SQL server point
of view for the daylight savings time change that is happening soon.
SQL 7.0
SQL 2000
SQL 2005
Will there be a hot fix?
Thanks
SQL Server takes its date and time from Windows. There is no hot fix
required for SQL Server, since the DST change is dealt with at the operating
system layer.
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:17E4EF33-1859-4897-89D0-658979BF7E8C@.microsoft.com...
> Can you tell me what kind of impact we are looking at from SQL server
> point
> of view for the daylight savings time change that is happening soon.
> SQL 7.0
> SQL 2000
> SQL 2005
> Will there be a hot fix?
> Thanks
|||Take a look into this URL:-
http://www.microsoft.com/windows/timezone/dst2007.mspx
Thanks
Hari
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:17E4EF33-1859-4897-89D0-658979BF7E8C@.microsoft.com...
> Can you tell me what kind of impact we are looking at from SQL server
> point
> of view for the daylight savings time change that is happening soon.
> SQL 7.0
> SQL 2000
> SQL 2005
> Will there be a hot fix?
> Thanks
|||"Aaron Bertrand [SQL Server MVP]" wrote:

> SQL Server takes its date and time from Windows. There is no hot fix
> required for SQL Server, since the DST change is dealt with at the operating
> system layer.
Technically, not quite. SQL Server Notification Services 2.0 RTM and SP1,
and SQL Server Notification Services 2005 SP1 are affected. They store time
zone info in a table NSTimeZoneDstOffsets. A fix will be required.
Linchi

Daylight Savings Time Change

Can you tell me what kind of impact we are looking at from SQL server point
of view for the daylight savings time change that is happening soon.
SQL 7.0
SQL 2000
SQL 2005
Will there be a hot fix?
ThanksSQL Server takes its date and time from Windows. There is no hot fix
required for SQL Server, since the DST change is dealt with at the operating
system layer.
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:17E4EF33-1859-4897-89D0-658979BF7E8C@.microsoft.com...
> Can you tell me what kind of impact we are looking at from SQL server
> point
> of view for the daylight savings time change that is happening soon.
> SQL 7.0
> SQL 2000
> SQL 2005
> Will there be a hot fix?
> Thanks|||Take a look into this URL:-
http://www.microsoft.com/windows/timezone/dst2007.mspx
Thanks
Hari
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:17E4EF33-1859-4897-89D0-658979BF7E8C@.microsoft.com...
> Can you tell me what kind of impact we are looking at from SQL server
> point
> of view for the daylight savings time change that is happening soon.
> SQL 7.0
> SQL 2000
> SQL 2005
> Will there be a hot fix?
> Thanks|||"Aaron Bertrand [SQL Server MVP]" wrote:
> SQL Server takes its date and time from Windows. There is no hot fix
> required for SQL Server, since the DST change is dealt with at the operating
> system layer.
Technically, not quite. SQL Server Notification Services 2.0 RTM and SP1,
and SQL Server Notification Services 2005 SP1 are affected. They store time
zone info in a table NSTimeZoneDstOffsets. A fix will be required.
Linchi

daylight savings time

With the change in daylight savings time this year I was wondering if any patches needed to be applied to sql server. We are running sql server 2000.
Thanks.
Joethe date and time in sql server is determined by the machine clock which would mean it would be a windows patch.

they moved the date, did'nt they? Good question.|||Thanks for the reply, Sean.|||you guys should check out this article --

http://sqlblindman.googlepages.com/begindst

yes, that blindman

:)|||Nice but unnecessary. The mothership will provide the patches. Unless you are one of those guys that do not patch your servers…

http://www.microsoft.com/windows/timezone/dst2007.mspx

Some funny crap might happen this year because of this.

Here is the patch for XP SP2 and Server 2003.

http://support.microsoft.com/kb/928388/sql

Daylight savings time

Does anyone have a good daylight savings time function? I need to get it going today, and am thinking of being lazy and just putting the dates in a table for the next several years. Since I am only concerned with EST and BST, however, and both follow strict rules, I was hopeing to write a function that I can use dynamically.

Hate to reinvent the wheel though.

TIAI have one I can send you later today.

blindman|||You da (blind)man!|||if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[BeginDST]') and xtype in (N'FN', N'IF', N'TF'))
drop function [dbo].[BeginDST]
GO

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[EndDST]') and xtype in (N'FN', N'IF', N'TF'))
drop function [dbo].[EndDST]
GO

SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

create function BeginDST(@.TargetDate as datetime)
returns datetime
as
--function BeginDST
--blindman, 9/2003
--Returns the data Daylight Savings Time begins for the specified year.
begin
declare @.BeginDST datetime
set @.BeginDST = '4/1/' + cast(Year(@.TargetDate) as char(4))
while datename(weekday,@.BeginDST) <> 'Sunday'
set @.BeginDST = dateadd(day, +1, @.BeginDST)
Return @.BeginDST
end

GO

create function EndDST(@.TargetDate as datetime)
returns datetime
as
--function EndDST
--blindman, 9/2003
--Returns the data Daylight Savings Time ends for the specified year.
begin
declare @.EndDST datetime
set @.EndDST = '10/31/' + cast(Year(@.TargetDate) as char(4))
while datename(weekday,@.EndDST) <> 'Sunday'
set @.EndDST = dateadd(day, -1, @.EndDST)
Return @.EndDST
end

GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO|||Thanks dude. While I was waiting, however, I came up with this:

CREATE FUNCTION [TZCONVERT] (@.time_zone VARCHAR(5), @.in_date DATETIME)
RETURNS DATETIME AS
BEGIN

DECLARE @.out_date DATETIME,
@.daylight_start_date DATETIME,
@.daylight_end_date DATETIME

IF @.time_zone = 'EST'
BEGIN
SET @.daylight_start_date = DATEADD(hour, 3, DATEADD(d, (7-DATEPART(dw,'4/1/' + CAST(YEAR(@.in_date) AS VARCHAR(4)))+2)%7-1, '4/1/' + CAST(YEAR(@.in_date) AS VARCHAR(4))))
SET @.daylight_end_date = DATEADD(hour, 1, DATEADD(day, -1 * DATEPART(dw,'10/31/' + CAST(YEAR(@.in_date) AS VARCHAR(4))), '11/1/' + CAST(YEAR(@.in_date) AS VARCHAR(4))))

IF @.in_date BETWEEN @.daylight_start_date AND @.daylight_end_date
SET @.out_date = DATEADD(hour, -4, @.in_date)
ELSE
SET @.out_date = DATEADD(hour, -5, @.in_date)
END

IF @.time_zone = 'BST'
BEGIN
SET @.daylight_start_date = DATEADD(hour, 3, DATEADD(day, -1 * DATEPART(dw,'3/31/' + CAST(YEAR(@.in_date) AS VARCHAR(4))), '4/1/' + CAST(YEAR(@.in_date) AS VARCHAR(4))))
SET @.daylight_end_date = DATEADD(hour, 1, DATEADD(day, -1 * DATEPART(dw,'10/31/' + CAST(YEAR(@.in_date) AS VARCHAR(4))), '11/1/' + CAST(YEAR(@.in_date) AS VARCHAR(4))))

IF @.in_date BETWEEN @.daylight_start_date AND @.daylight_end_date
SET @.out_date = DATEADD(hour, 1, @.in_date)
ELSE
SET @.out_date = @.in_date
END

RETURN @.out_date

END|||I tried using modulo arthimetic at first too, but it became too confusing to try to account for the fact that the "dw" parameter for DATEPART returns different values on different systems depending on the value of the DATEFIRST setting.

As long as you never run your code on a system with a different setting you should be OK.

blindman

Daylight Savings Patch for 2000 Server

I was wondering if there is a simple patch for 2000 server. It seems that the only fix is to edit the registry and to use the time zone editor app. If there is a simple patch like there is for the 2003 servers i would appreciate it if anyone can show me where. I have about 80+ servers with 2000!!!

Much appreciated!

Look at this KBA http://support.microsoft.com/?kbid=928388 for more information.|||

This is the actual kba for windows 2000 server: http://support.microsoft.com/kb/914387

As you can see, there's really no quick patch to run.

|||I don't understand. SQL Server has absolutely no clue what the time is, time zone, or anything else. It gets all of its timing information from Windows. So, if you fix the time in Windows, you are done. You aren't finding a patch, simply because there isn't one since there isn't anything in SQL Server to fix.|||If you are based in the USA then as per the KBA you need to patch as per the recent time zone settings.|||Which is precisely the point. You patch WINDOWS. You do NOT patch SQL Server, because there is no SQL Server patch for this.|||Michael, the original poster was trying to patch windows .... Windows Server 2000, not SQL 2000. Yes, not all of us are using Server 2003 on all our hardware.

So, I guess is it a manual patch for my Server 2000 machines? Any body found a better way?

Thanks,

Vidal|||

Hi Guys

I think I found a better way!!!

Tech Republic had an article (HTTP://articles.techrepublic.com.com/5100-10877-61680.htlm) that has a tool called TZEdit where you set the new times zone setting without having to hack the registry.

I installed it last night and it works , I'm deploying it to the rest of my Windows 2000 Servers today, just read the "help file" and make sure you go to control panel and unselect and reselect your time zone to have your changes take effect

Hope that helps ,Mike

Daylight Savings Patch for 2000 Server

Much appreciated!

Look at this KBA http://support.microsoft.com/?kbid=928388 for more information.|||

This is the actual kba for windows 2000 server: http://support.microsoft.com/kb/914387

As you can see, there's really no quick patch to run.

So, I guess is it a manual patch for my Server 2000 machines? Any body found a better way?

Thanks,

Vidal|||

Hi Guys

I think I found a better way!!!

Tech Republic had an article (HTTP://articles.techrepublic.com.com/5100-10877-61680.htlm) that has a tool called TZEdit where you set the new times zone setting without having to hack the registry.

Hope that helps ,Mike

Daylight Savings Date Change

I have a Windows 2003 Standard server running MS SQL 2000 Server on it. I
read that if I have MS SQL Server Notification Services running on it I will
need to apply an update to it for the daylight savings time date change. Ho
w
do I tell if I have Notification Services running on this server. I don't
see it in Services. Is there anywhere else I need to look or is that it?
Thank you in advance.
--
Mike StevensYou would see it as a separately installed program in "Add/Remove Programs"
if you are on SQL Server
2000.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Stevens" <Stevens@.discussions.microsoft.com> wrote in message
news:D66848A1-E298-4A6E-AB6A-2085835741B0@.microsoft.com...
>I have a Windows 2003 Standard server running MS SQL 2000 Server on it. I
> read that if I have MS SQL Server Notification Services running on it I wi
ll
> need to apply an update to it for the daylight savings time date change.
How
> do I tell if I have Notification Services running on this server. I don't
> see it in Services. Is there anywhere else I need to look or is that it?
> Thank you in advance.
> --
> Mike Stevens|||In addition to the note from Tibor, you will have some databases like
NSMain* and NS*. The KB article that has the fix includes a section on
detecting if Notification Services is installed on SQL Server 2000:
http://support.microsoft.com/kb/931815
HTH,
Plamen Ratchev
http://www.SQLStudio.com|||That answered my question. Thank you for your help.
--
Mike Stevens
"Tibor Karaszi" wrote:

> You would see it as a separately installed program in "Add/Remove Programs
" if you are on SQL Server
> 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Stevens" <Stevens@.discussions.microsoft.com> wrote in message
> news:D66848A1-E298-4A6E-AB6A-2085835741B0@.microsoft.com...
>
>|||Thank you for your help. It doesn't look like I have it. One less thing to
do.
--
Mike Stevens
"Plamen Ratchev" wrote:

> In addition to the note from Tibor, you will have some databases like
> NSMain* and NS*. The KB article that has the fix includes a section on
> detecting if Notification Services is installed on SQL Server 2000:
> http://support.microsoft.com/kb/931815
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com
>
>|||Plamen,
Can you install SQL2005 Notification Services but not configure it? If
that's so then this is what we have done so we should not have to run the
script in the KB article.
Chris
"Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
news:OBOgOXuSHHA.5016@.TK2MSFTNGP05.phx.gbl...
> In addition to the note from Tibor, you will have some databases like
> NSMain* and NS*. The KB article that has the fix includes a section on
> detecting if Notification Services is installed on SQL Server 2000:
> http://support.microsoft.com/kb/931815
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com
>
>|||You are correct Chris. When you install Notification Services only the
binary files are installed. You have to worry about applying the fix only
when you configure and deploy instances of Notification Services, which host
notification applications. Also, note in the KB that new instances created
after SP2 will not need to be fixed, as they will have the correct
information.
Regards,
Plamen Ratchev
http://www.SQLStudio.com|||Thanks Plamen.
That's what I had hoped for.
Chris
"Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
news:%239ANydwSHHA.4260@.TK2MSFTNGP06.phx.gbl...
> You are correct Chris. When you install Notification Services only the
> binary files are installed. You have to worry about applying the fix only
> when you configure and deploy instances of Notification Services, which
> host notification applications. Also, note in the KB that new instances
> created after SP2 will not need to be fixed, as they will have the correct
> information.
> Regards,
> Plamen Ratchev
> http://www.SQLStudio.com
>

Daylight Savings Date Change

I have a Windows 2003 Standard server running MS SQL 2000 Server on it. I
read that if I have MS SQL Server Notification Services running on it I will
need to apply an update to it for the daylight savings time date change. How
do I tell if I have Notification Services running on this server. I don't
see it in Services. Is there anywhere else I need to look or is that it?
Thank you in advance.
Mike Stevens
In addition to the note from Tibor, you will have some databases like
NSMain* and NS*. The KB article that has the fix includes a section on
detecting if Notification Services is installed on SQL Server 2000:
http://support.microsoft.com/kb/931815
HTH,
Plamen Ratchev
http://www.SQLStudio.com
|||That answered my question. Thank you for your help.
Mike Stevens
"Tibor Karaszi" wrote:

> You would see it as a separately installed program in "Add/Remove Programs" if you are on SQL Server
> 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Stevens" <Stevens@.discussions.microsoft.com> wrote in message
> news:D66848A1-E298-4A6E-AB6A-2085835741B0@.microsoft.com...
>
>
|||Thank you for your help. It doesn't look like I have it. One less thing to
do.
Mike Stevens
"Plamen Ratchev" wrote:

> In addition to the note from Tibor, you will have some databases like
> NSMain* and NS*. The KB article that has the fix includes a section on
> detecting if Notification Services is installed on SQL Server 2000:
> http://support.microsoft.com/kb/931815
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com
>
>
|||Plamen,
Can you install SQL2005 Notification Services but not configure it? If
that's so then this is what we have done so we should not have to run the
script in the KB article.
Chris
"Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
news:OBOgOXuSHHA.5016@.TK2MSFTNGP05.phx.gbl...
> In addition to the note from Tibor, you will have some databases like
> NSMain* and NS*. The KB article that has the fix includes a section on
> detecting if Notification Services is installed on SQL Server 2000:
> http://support.microsoft.com/kb/931815
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com
>
>
|||You are correct Chris. When you install Notification Services only the
binary files are installed. You have to worry about applying the fix only
when you configure and deploy instances of Notification Services, which host
notification applications. Also, note in the KB that new instances created
after SP2 will not need to be fixed, as they will have the correct
information.
Regards,
Plamen Ratchev
http://www.SQLStudio.com
|||Thanks Plamen.
That's what I had hoped for.
Chris
"Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
news:%239ANydwSHHA.4260@.TK2MSFTNGP06.phx.gbl...
> You are correct Chris. When you install Notification Services only the
> binary files are installed. You have to worry about applying the fix only
> when you configure and deploy instances of Notification Services, which
> host notification applications. Also, note in the KB that new instances
> created after SP2 will not need to be fixed, as they will have the correct
> information.
> Regards,
> Plamen Ratchev
> http://www.SQLStudio.com
>
sql

Daylight Savings Date Change

I have a Windows 2003 Standard server running MS SQL 2000 Server on it. I
read that if I have MS SQL Server Notification Services running on it I will
need to apply an update to it for the daylight savings time date change. How
do I tell if I have Notification Services running on this server. I don't
see it in Services. Is there anywhere else I need to look or is that it?
Thank you in advance.
--
Mike StevensYou would see it as a separately installed program in "Add/Remove Programs" if you are on SQL Server
2000.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Stevens" <Stevens@.discussions.microsoft.com> wrote in message
news:D66848A1-E298-4A6E-AB6A-2085835741B0@.microsoft.com...
>I have a Windows 2003 Standard server running MS SQL 2000 Server on it. I
> read that if I have MS SQL Server Notification Services running on it I will
> need to apply an update to it for the daylight savings time date change. How
> do I tell if I have Notification Services running on this server. I don't
> see it in Services. Is there anywhere else I need to look or is that it?
> Thank you in advance.
> --
> Mike Stevens|||In addition to the note from Tibor, you will have some databases like
NSMain* and NS*. The KB article that has the fix includes a section on
detecting if Notification Services is installed on SQL Server 2000:
http://support.microsoft.com/kb/931815
HTH,
Plamen Ratchev
http://www.SQLStudio.com|||That answered my question. Thank you for your help.
--
Mike Stevens
"Tibor Karaszi" wrote:
> You would see it as a separately installed program in "Add/Remove Programs" if you are on SQL Server
> 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Stevens" <Stevens@.discussions.microsoft.com> wrote in message
> news:D66848A1-E298-4A6E-AB6A-2085835741B0@.microsoft.com...
> >I have a Windows 2003 Standard server running MS SQL 2000 Server on it. I
> > read that if I have MS SQL Server Notification Services running on it I will
> > need to apply an update to it for the daylight savings time date change. How
> > do I tell if I have Notification Services running on this server. I don't
> > see it in Services. Is there anywhere else I need to look or is that it?
> >
> > Thank you in advance.
> > --
> > Mike Stevens
>
>|||Thank you for your help. It doesn't look like I have it. One less thing to
do.
--
Mike Stevens
"Plamen Ratchev" wrote:
> In addition to the note from Tibor, you will have some databases like
> NSMain* and NS*. The KB article that has the fix includes a section on
> detecting if Notification Services is installed on SQL Server 2000:
> http://support.microsoft.com/kb/931815
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com
>
>|||Plamen,
Can you install SQL2005 Notification Services but not configure it? If
that's so then this is what we have done so we should not have to run the
script in the KB article.
Chris
"Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
news:OBOgOXuSHHA.5016@.TK2MSFTNGP05.phx.gbl...
> In addition to the note from Tibor, you will have some databases like
> NSMain* and NS*. The KB article that has the fix includes a section on
> detecting if Notification Services is installed on SQL Server 2000:
> http://support.microsoft.com/kb/931815
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com
>
>|||You are correct Chris. When you install Notification Services only the
binary files are installed. You have to worry about applying the fix only
when you configure and deploy instances of Notification Services, which host
notification applications. Also, note in the KB that new instances created
after SP2 will not need to be fixed, as they will have the correct
information.
Regards,
Plamen Ratchev
http://www.SQLStudio.com|||Thanks Plamen.
That's what I had hoped for.
Chris
"Plamen Ratchev" <Plamen@.SQLStudio.com> wrote in message
news:%239ANydwSHHA.4260@.TK2MSFTNGP06.phx.gbl...
> You are correct Chris. When you install Notification Services only the
> binary files are installed. You have to worry about applying the fix only
> when you configure and deploy instances of Notification Services, which
> host notification applications. Also, note in the KB that new instances
> created after SP2 will not need to be fixed, as they will have the correct
> information.
> Regards,
> Plamen Ratchev
> http://www.SQLStudio.com
>

Daylight Savings change

All,

I am curious if there is anything to worry about with the recently adopted change to the Daylight Savings settings and SQL Server? Are there any required patches, suggestions, etc?

Thank you

Take a look here http://www.microsoft.com/windows/timezone/dst2007.mspx

Denis the SQL Menace

http://sqlservercode.blogspot.com/

|||

The link above is right. In short you will need to update your operating system, which should happen automatically through Windows Update, but there is no need to patch SQL Server.

We were recently reviewing all components to check if there is potential area that needs updating, and we have not identified any.

Regards,

Maciek Sarnowicz

Tuesday, March 27, 2012

Daylight Savings Time error SQL SERVER 2000

Daylight Savings Time error SQL SERVER 2000

Daylight Savings Time changes coming in 2007

Daylight Savings Time changes coming in 2007

Daylight Savings Time changes coming in 2007

Sunday, March 25, 2012

Daylight Savings Time changes coming in 2007

Daylight Savings Time changes coming in 2007

Daylight Savings Time Change in 2007

Daylight Savings Time Change in 2007

Daylight Savings Time Change

Daylight Savings Time Change

Daylight Savings Time Change

daylight savings time

Daylight savings time

Daylight Savings Patch for 2000 Server

Daylight Savings Patch for 2000 Server

Daylight Savings Date Change

Daylight Savings Date Change

Daylight Savings Date Change

Daylight Savings change

db error

Blog Archive

About Me