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!
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!
Anyone if SQL server has any built-in mechanism for handling Daylight savings?
Mostly for figuring out time passed between two datetime values....
Thanks in advance.
I have the database on a GMT server and a logdate that is in GMT too. How do I convert this into CST (GMT -6) , during daylight savings (GMT-5) when passing it back to the webpage.
I can use DATEADD(hh,-6,LogDate) but how do I know if the daylight savings period has started to do DATEADD(hh,-5,LogDate). I also want to solve this at the database level without altering the front-end.
Thanks.
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.
Joe
I have jobs scheduled on SQL Server 2005 and SQL Server 2008.
It's my understanding that if there are jobs scheduled to run between 2:00 - 3:00 AM this Sunday when Daylight Savings time moves the time from 2:00 AM to 3:00 AM, these jobs will run at 3:00 AM along with any scheduled jobs to run at 3:00 AM.
Is this correct?
This must've been convered before, but I can seem to find a solution to it. Daylight Savings Time is about to end in my area, at which time the clocks will go backwards from 1:59am to 1:00am.
I have scheduled jobs that run every minute, and I'm expecting that when the clock rolls back, they will stop running for the gained hour until the clock catches back up.
So, I need an automated way to correct this.
I was looking at the msdb..sysjobschedules table, at the next_run_time column. But it doesn't make much sense. That value will periodically update, but it is always a good bit behind the next run time reported in EM. And manually updating it seems to have no effect.
Is there a way to get a job to run or to recalculate the next run time via tsql script?
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?
I wanted to know how we can handle Time Zones and Daylight Savings Time in SQL Server 2000 as well as 2005.
Any pointers would be helpful.
Pranav
Hello all,
Hope all of us know that DST Patch update will be on 4th November,07.
Here my query is how to retrieve the DST patch updated date in sqlserver 2000?
any queries on this?
Would any one help me on this?
Thanks in advance,
Please advice me, now we are using service pack1, what is the latest service pack i can upgrade and has all the issues been recitified.
Thanks
Sort of new to MSSQL and I have a problem with my maintenance script not deleting files on 2 out of 3 servers so I am trying to determine what patch level I am at.
'Server A' works as expected:
Microsoft SQL Server 2005 - 9.00.2050.00 (Intel X86)
Feb 13 2007 23:02:48
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
These two servers don't:
Server B.
Microsoft SQL Server 2005 - 9.00.2050.00 (Intel X86)
Feb 13 2007 23:02:48
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Server C.
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
So I can see where I should patch server B to SP2 but why does Server C report as 9.00.1399 SP2?
Hi,I need to move a database from an instance running SQL Server 2000 SP3to another running SQL Server 2000 SP2. Can I just use backup/restoreor detach/reattach and let SQL server take care of any downgrading (ifany).Many thanksGiovanni
View 4 Replies View RelatedAfter applying the DST (daylight savings time) fix by METHOD-2 in the following KB article:
http://support.microsoft.com/default.aspx/kb/914387
We are receiving the following error for all reports we currently serve:
aspnet_wp!webserver!3c88!03/12/2007-08:44:53:: e ERROR: Internal error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: date
at System.Web.HttpCachePolicy.UtcSetLastModified(DateTime utcDate)
at System.Web.HttpCachePolicy.SetLastModified(DateTime date)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.ReturnResponseHeaders(HttpClientRequest sessionManager, RSStream result, HttpResponse resp)
at Microsoft.ReportingServices.WebServer.ResponseHeaderData.ReturnResponseHeaders()
at Microsoft.ReportingServices.WebServer.HttpResponseStream.InternalFlush(Boolean finalFlush)
at Microsoft.ReportingServices.WebServer.HttpResponseStream.Close()
at Microsoft.ReportingServices.WebServer.HttpResponseStreamFactory.CloseAllOpenStreams()
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport()
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(ItemType itemType)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem()
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent()
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
Reporting Services Version: Microsoft SQL Server Reporting Services Version 8.00.1042.00
SQL Server Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
We are using the work around specified in the following post to fix this issue:
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/3f2b4854dc79e5e8/1b8261f4cf149078?lnk=st&q=Reporting+Services+dst+error&rnum=2&hl=en#1b8261f4cf149078
Any Help would be greatly appreciated!
Thanks,
ML
We have scheduled jobs, which run every 2 minutes. If the job runs at 1:59am, the next run time is set to 2:01 am. If at 2:00am, the clock is rolled back to 1:00, my scheduled run time is still 2:01am. In this situalion, my 2 minute job will not run until 1 hour and 1 minute later, at 2:01am.
Any suggestions for reseting the next run times on the jobs to the next interval after the clock roles back to 1:00am.
-Matt
Hi,
How to prepare SQL Server 2005 and SQL Server 2000 for changes to daylight saving time in 2007?
I thought I would post this just in case you are not aware of the change of the Daylight Saving Time start and end dates in 2007. This is really an OS problem, not a SQL Server problem, but it could have a big impact on your applicaitons if you are not prepared. The first change is less that 2 months away, so it's not a bad time to give it some thought.
Here are some articles about preparing systems for the 2007 daylight savings time changes that you might find of interest.
Preparing for daylight saving time changes in 2007:
“Starting in the spring of 2007, daylight saving time (DST) start and end dates for the United States will transition to comply with the Energy Policy Act of 2005. DST dates in the United States will start three weeks earlier (2:00 A.M. on the second Sunday in March) and will end one week later (2:00 A.M. on the first Sunday in November).
Microsoft will be producing an update for Microsoft products affected by the new United States daylight saving time transition dates. These updates will be released through a combination of channels including Microsoft Customer Support Services (CSS), hotfixes incorporated in Knowledge Base articles, Windows Update, Microsoft Update, Windows Server Update Services (WSUS), and the Microsoft Download Center.�
http://www.microsoft.com/windows/timezone/dst2007.mspx
How to configure daylight saving time for the United States in 2007:
http://support.microsoft.com/?kbid=914387
Daylight Saving Time in Canada:
The article in the link below indicates that all Canadian provinces except for Nunavut have decided to follow the US daylight savings changes in 2007. The article contains links to news articles with official announcements of the changes.
http://en.wikipedia.org/wiki/Time_in_Canada
CODO ERGO SUM
Hi,
I have this simple SQL query which SELECTs the fields according to the criteria in WHERE clause. SELECT callingPartyNumber, originalCalledPartyNumber, finalCalledPartyNumber,
dateadd(ss, (dateTimeConnect + (60 * 60 * -5))+3600 , '01-01-1970 00:00:00') AS dateTimeConnect,
dateadd(ss, (dateTimeDisconnect + (60 * 60 * -5))+3600, '01-01-1970 00:00:00') AS dateTimeDisconnect,
CONVERT(char(8), DATEADD(second, duration, '0:00:00'), 108) AS duration
FROM Calls
WHERE
(callingPartyNumber = ISNULL(@callingPartyNumber, callingPartyNumber)) AND
(originalCalledPartyNumber = ISNULL(@originalCalledPartyNumber, originalCalledPartyNumber)) AND
(finalCalledPartyNumber = ISNULL(@finalCalledPartyNumber, finalCalledPartyNumber)) AND
(duration >= @theDuration) AND
((datetimeConnect - 14400) >= ISNULL(convert(bigint,
datediff(ss, '01-01-1970 00:00:00', @dateTimeConnect)), datetimeConnect)) AND
((dateTimeDisconnect - 14400) <= ISNULL(convert(bigint,
datediff(ss, '01-01-1970 00:00:00', @dateTimeDisconnect)), dateTimeDisconnect))
If you notice, in the SELECT, I add 3600 (1 hour) to adjust the time according to the current DayLight saving setting. Similarly, while comparing in WHERE clause, I subtract 14400 seconds (4 hours) to adjust the comparison according to EST (-5 GMT, but doing -4 GMT since daylight saving) and daylight saving.
Also, dateTimeConnect and dataTimeDisconnect fields save time in UTC seconds.
Now this application may be used by clients in different timezones. The application may be hosted on their server which would mean a different time zone. What would be the best way to make this time zone and daylight adjustment more dynamic instead of hardcoding the values.
Last weekend many of our severs had a failed job "collection_set_3_upload". The error that occured is: "Violation of PRIMARY KEY constraint 'PK_ active_ sessions_ and_requests'. Cannot insert duplicate key in object 'snapshots.active_sessions_and_requests'. The duplicate key value is (2824333, 2015-10-25 02:54:49.7630000 +02:00, 1)."Last weekend we happened to go from summer time to winter time. i.e. the clock passed 02:00 - 3:00 two times during this night.
I.e. there is a bug in the Data Collector component that collects data for the Management Data Warehouse: it uses local time instead of UTC. I've created a Connect item to report it to Microsoft.URL...how do you get your process running again? the job will no longer run because it will every 5 minutes keep on trying to upload the conflicting data for the 2nd 2:00 - 3:00 period. I've only found one solution: get rid of all data collected but not yet uploaded.
You do this by stopping the Collection set (in SSMS go to Object Explorer -> <the server you want to fix> -> Management -> Data Collection -> System Data Collection Sets. Right click "Query Statistics" and select "Stop Data Collection Set").Then you delete the cached results from the sql server machine's harddisk. These cached results are in files located in a Temp folder on the sql machine itself, inside the AppData folder for the service account SQL Server Agent is running under. Usually it will be something like: c:Users<sql agent service account>AppDataLocalTemp.
Inside this folder delete all files that have 'QueryActivity' in their name. You'll loose all data collected since the start of wintertime, but at least your data collection process will work again.After this you can start the Collection set again by right clicking it and select "Start Data Collection Set". Every 5 minutes the data will be summarised and uploaded into your management data warehouse.
Posting Data Etiquette - Jeff Moden
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw
I plan to apply the new security patch on my SQL 7.0 sp3 servers and get my SQL 2000 servers up to SP2 (which apparently already includes this)
But I was reading the Mitigating Factors in the announcement of this vulnerability and one reads as below:
"The effect of exploiting the first vulnerability would depend on how the SQL Server service was configured. SQL Server can be configured to run in a security context of the administrator’s choosing. (By default, it runs as a domain user). If best practices are followed, and the service is configured to run with the least privileges necessary, it would limit the worst-case damage an attacker could achieve. "
So my question is: What is the best practice for the SQL Server service and Agent service? Also are there resources for Best Practices?
Thanks!!
I am trying to apply this patch to a Developers Edition of SQL 2000. According to the instructions, I am to replace ssnetlib.pdb, located int the binndll folder. well, this file does not exist in this or any other folder on the server. I have installed SP2 and all previous patches. Anyone have any idea why this is and how to resolve it?
Thanks,
Mitchel
Hello, everyone:
Are ther any basic information about patch on SQL Server? How to develop patch, and run it? Thanks a lot
ZYT
Hi,
I have discovered something wrong with my SSIS package and I thought it best to post a new thread since the problem is not what I thought it was initially.
With relation to my post of 'directory variable problem' I have now discovered by opening my project this morning that apparently my project had gone corrupt, according to the dev environment since the message reads:
"There were errors while the package was being loaded.The package might be corrupted.See the Error List for details."
The Error List:
"Error 13 Error loading MyTestSSISPackage.dtsx: The connection "(local).MyTestDB.sa" is not found. This error is thrown by Connections collection when the specific connection element is not found."
This is a buggy ADO.net connection that I deleted yesterday since, even though it connects successfully, doesn't want to work! It keeps on telling me log in failed for user <MyTestUser> even after I test it and it connects fine with the username and password during the UDL screen of the connection.. It's like it forgets the bloody password.
I created another connection, this time an OLE connection and it seems to work fine.
*EDITED*
I stand corrected..no bloody connection manager is working now. They all fail stating that they cannot connect to the db due to some or another 'unsupported' value in the connection string...the connectionstring was set up by the environment's udl????? how is this possible. I am beginning to get annoyed with SSIS
Now finally my question...WHY is it that every time I change something its like the dev environment doesn't cascade the change throughout the project or package? The problem I have been having with my variables not getting picked up with the correct values which I gave them during design time is probably also related to this. How or where can I remove the reference to this old ADO.Net connection since I cannot find it anywhere in the <package>.dtsx file?
Anyone ever experienced this?
Regards
Mike
following is my sql:
select a.dcode, b.district from table1 a, table2 b
where
a.id = b.id
and return following result:
dcode district
123 south
321 north
456 east
789 west
123
789
so for those records that district are null, how can i fill them up as i know they have the same dcode as the other records?
According to SP1 documentation patching the Active node in a cluster will automatically apply the SP1 patch to the Passive nodes. However, I found a MS document that says if you have management tools installed on the passive node, you must patch this node separately. Is this correct?
Also, since Integration Services is not cluster-aware and therefore must be installed separately to the passive node(s), does SP1 need to be applied directly to the passive node(s) to patch Integration Services or is it automatically patched when I patch the Active node?
Thanks, Dave
I got 4 sql2k5 servers with service patch version as following:
Microsoft SQL Server 2005 - 9.00.2221.00 (Intel X86) Feb 9 2007 17:30:38
Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows
NT 5.2 (Build 3790: Service Pack 2)
Microsoft SQL Server 2005 - 9.00.2153.00 (Intel X86) May 8 2006 22:41:28
Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT
5.2 (Build 3790: Service Pack 2)
Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86) Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT
5.2 (Build 3790: Service Pack 2)
Can anyone please advise me what is the easiest way to upgrade them to the
most updated patch version? i.e. update path.
Meanwhile, what is the best practice to apply patches? Do you go to
microsoft website and check it out daily and apply it or other tricks?
Please advise. Thanks.
Hi,
I have problem in install SQL Server 6.5 service patch 5a. I download the .exe
from Microsoft and try to install it, it give error:
"setup initalizarion could not be successfully completed.
isql.exe can not be executed.
see error from relevant.OUT file. "
I thought the setup file need to run name pipes prototal instead of TCP/IP, so I change, but still give me the error. I install SS service patch 5a in other mechines before. Never has any problem. This time two of my server run into this problem, any help will be appreciated.
Eugene Shi
On the re-boot required for critical patch KB824105 MS SQL Server failed torecgnize the log on for the account it is registered under, and all otheraccounts when manually cahnged.It seems to have completely lost all ability to recognize and logon.SQL is totally hooped - no ODBC at all at the service doesn't start. At allbecause of no recognition of any accounts.Any suggestions? I've been trying for a while.
View 1 Replies View Related<!--[if !supportLists]--><!--[endif]-->
I posted this question before, and got a response about Windows Update. However, I work in a larger corp. and need to know if there are any other answers to this? We use a patch client that rolls out patches and service packs after we have tested them in our environment. What can we do to stay as up to date as possible for security patches?
How are security patches for SQL Server Express made available (e.g., as separate distributions or bundled into other Microsoft patch distribution mechanisms)? Are there specific procedures that I need to put in place to ensure that it gets patched on end user machines?
-Kyle
Hey!
Has anybody here had any issues with the MS03-031 security patch and SQL 2000 on Windows 2003?
We recently installed this patch on one of our test SQL 2000 machines, and the performance of queries running on this machine have gone up (gotten worse) by at least 10X.
We use indexed views and all queries are run with WITH(NOEXPAND) to force the indexed view to be used.
Anyway, after the patch was installed, the queries on the indexed view will ONLY use the clustered index, and not any of the other indexes, causing a Clustered Index Scan.
I removed the patch (well, re-installed SQL) patched it up to SP3a, and performance is back to normal.
Anybody experience anything similar?
Paul
Having an issue updating SQL Server 2012 RTM Standard  to CU3.I'm getting the following error from the Detail log on each try: "Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2061893565)"I've tried rebooting the server, ensuring the user running the installer is a local admin account, ran the repair wizard on the SQL install...Nothing seems to work.I have two identical servers, the first has gone smoothly, this is bugging me...
Server: Dell R720XD, Dual E5-2643 CPU, 64Gb RAM, Windows Server 2008 R2 Enterprise x64, SQL Server 2012 RTM CU2 x64 Installed.
Final result: The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
 Exit code (Decimal):      -2061893565
 Start time:           2012-09-17 16:25:32
 End time:            2012-09-17 16:28:41
 Requested action:        Patch
Instance MSSQLSERVER overall summary:
 Final result:          The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
 Exit code (Decimal):      -2061893565
 Start time:           2012-09-17 16:27:21
 End time:            2012-09-17 16:28:39
 Requested action:        Patch
[code]...
After applying security patch MS03-031 (Sql server ver 8.00.818) aquery that used to execute in under 2 seconds, now takes over 8Minutes to complete. Any ideas on what the heck might be going on?I have tested this extensively and can say for certain that installingthis hot fix is what has caused the performance problem. I just don'tknow why or how to fix it.Brian Oster
View 3 Replies View RelatedThis is related to an earlier post, but I found out that I was able to see SQL Server counters in Performance monitor before applying the patch, but the counters were not present afterwards....
do I need to edit the registry ?