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?
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
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?
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?
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?
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.
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.
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.
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
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
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?
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!!!
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.
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?
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
When I run sp1 on the active node of a 64-bit cluster the setup just hangs when it gets to the Database services part. It does not return any errors as mentioned by others in this forum. I also do not have SqlSupport.msi in the add/remove programs (one suggestion on this forum was to uninstall it reinstall). I have let it run for up to 12 hours with no result.
There is no SQL9_Hotfix_KB913090_sqlrun_sql.msp.log file only SQL9_Hotfix_KB913090.log
this is the content
05/09/2006 12:41:12.274 ================================================================================ 05/09/2006 12:41:12.274 Hotfix package launched 05/09/2006 12:41:15.634 Product discovery successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 SP Level check successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 Product language check successfully completed during the install process for DEV01 05/09/2006 12:41:15.634 Product version check successfully completed during the install process for DEV01 05/09/2006 12:41:15.681 Product discovery successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 SP Level check successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 Product language check successfully completed during the install process for DEV02 05/09/2006 12:41:15.681 Product version check successfully completed during the install process for DEV02 05/09/2006 12:41:15.743 Product discovery successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 SP Level check successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 Product language check successfully completed during the install process for DEV03 05/09/2006 12:41:15.743 Product version check successfully completed during the install process for DEV03 05/09/2006 12:41:15.790 Product discovery successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 SP Level check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Product language check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Product version check successfully completed during the install process for DEV04 05/09/2006 12:41:15.790 Command-line instance name check completed during the install process 05/09/2006 12:41:15.868 Baseline build check completed during the install process 05/09/2006 12:44:25.795 Attempting to install instance: DEV02 05/09/2006 12:44:25.795 Enumerating passive cluster nodes 05/09/2006 12:44:25.873 Patching available passive node: TTCSQL62A 05/09/2006 12:44:25.873 Waiting for first successfully completed passive node 05/09/2006 12:44:25.873 Attempting to patch running passive node: TTCSQL62A
we want to have an activepassive and active passive cluster.
node a install sql instance 1 failover over to node b
node b install sql instance 2 failover to node a
do I have to setup 2 cluster ? ie. quorum, msdtc etc..
or just one cluster(quorum, ip and name), one msdtc group( as per MS msdtc doc) and 2 san disks (one for node a and one for node b.
is this correct? I have looked and looked for a step by step on setting this up, no where can I find what i need. I downloaded the failover cluster doc from microsoft, book online etc..
I want to create an activepassive on both nodes. (onenode will be the active node for on sql install while the other is passive.
I want to repeat this fo rthe second node, the second node being active and node 1 passive.
I logged into node 1 and I installed sql 2005 in failover cluster into sqlinstance 1., everyhting was fine, failover etc.
Now I logged into node 2 and ran sql 2005 setup to create a failover cluster.
I chose to install into sql instance 2.
Database unable to install with error "failed to set registry settings for server network libraries. acition is setdefaults.error 11001, no such host is known.
If I am not setting this up correclty please let me know
thanks
everything was fine. I logged onto node 2, was going to
I'm having trouble finding the recommended process for doing a full Disaster Recovery on a two node active/passive sql 2005 cluster. I've been able to locate the procedure for rebuilding a failed node on the msdn site but no procedure for recovering the entire system. Any assistance or points in the right direction are appreciated.
I have just recently inherited a sql server 2005 cluster (2 nodes) we have a situation coming up where i need to power down the whole cluster for several hours as a result of some power mains work.
I just need to confirm with someone the correct way to power down the whole cluster and power it back up once the power is restored the company. I appreciate this may not be the best place to have posted this but i am desperate and couldn't find another location.
Anyone know before I invest in the hardware if it is possible to have Two Clusters on the same hardware both in Active/Passive Clustering where Cluster1 and Cluster2 both use the Default SQL Server 2005 Instance (No Named Instances)?
This would be a Virtual Cluster with Two separate 2 node Clusters on the Same Hardware sharing the same OS and SQL.
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
I have YET to have a 100% CLEAN install of SQL 2005 in a clustered environment. SQL 2005 Std. was not so bad, I think I finally managed a 99% clean install (no script errors on patches) on the third try.
SQL 2005 EE keeps erroring off on 2153 patch install. The error logs are no help at all; they simply stop logging activity at about the point that the error occurs.
Process: Install OS Patch OS to SP1 Cluster OS on SAN Configure Cluster Groups (DBC01, DBC02, DBC03) with cluster disks Configure MSDTC (network access, configure cluster resources)
Start SQL Installation Install RTM Binaries on Node 1 for Default Instance Install Workstation and non-cluster components on remaining nodes Install RTM Binaries on Node 2 for Named Instance
Reboot all nodes
Install SP1 for all instances from node 1
Install SP1 for all local services/applications for all other nodes
While attempting to install the 2153 SQL patch/hotfix, the process will either: Hang while waiting for the first passive node for the default instance; or Crash immediately with no error messages in the logs.
This is no nearly detailed enough, I know. I'm missing error messages and more. It's snowing outside and I have to get home. I just think that the installation for this product in a clustered environment is very unstraightforward at best, and at worst is a real liability to an organization since it's practically impossible to get it clean the first time through.
I am trying to remove Analysis Server from a cluster. I have done the research and according to MS you can't use the regular add/remove programs dialog to remove a component. You have to use the setup.exe from the command line. This article (http://support.microsoft.com/kb/910230) explains at the very bottom to run this command "Start /wait <DiskDrive>setup.exe /qb REMOVE=Analysis_Server INSTANCENAME=<InstanceName>". Well I do that and I get the installer up and running but when it gets to that system configuration check screen, where it runs a bunch of checks on the nodes, it just closes before it does any checks and nothing further happens. I can't find any error in the event log or find any log files on disk related to why its just closing.
Just to investigate further, I wondered what executable was running when you ran the installer though the add/remove programs dialog, so I looked in the registry. Well along with the SQL Server 2005 entry, which runs the setup bootstrap program in your default install folder, I noticed an entry that was idenified only by its GUID. Looking at the sub keys I noticed the DisplayName was Microsoft SQL Server 2005 Analysis Services. The UninstallString key was set to "MsiExec.exe /I{52B0D62A-860D-4136-9A8A-9FD877E8EE89}" so I ran that. The installer seems to work, but it doesnt run any configuration checks. I get to the screen with the big button to change components with no errors. Then it acutally shows Analysis Services installed (the disk icon is not xed out), I can then click and select entire feature will be unavailable. I haven't proceeded on this step because I am worried about the cluster.
I am assuming that this uninstaller will only remove analysis services from the node its running on. This is fine, cause I can just run this same procedure on all the nodes... and then i would assume I would have to manually clean up the cluster resource. But I have not tested this, and unfortuanlly I don't have a development cluster to try this on.
Does anyone have experience with removing Analysis Services from a failover cluster environment?
