Howto take SQL Server 2005 Cluster AND Cluster Group Offline

I need to update firmware on the backend storage used by our Active/Passive SQL Server 2005 Cluster. The first step in the process states that all I/O to the disks should be stopped. Per that, I need to take the the SQL Server cluster offline AND the cluster group; however, I then need to use one of the servers that participates in the cluster to perform the upgrade on the storage array. Using the process (which doesn't account for having to use one of clustered servers to perform updates) outlined at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1550288&SiteID=1 as a basis, below is my best guess regarding what I will need to do:
Shutdown:
1. Backup all of your databases prior to the outage and ensure they are in a safe place (NOT on the disk drives in the cluster)
2. Take the SQL Server group OFFLINE. This will cleanly shutdown the SQL Server and it will remain offline when you power the machine back on.
3. Once SQL Server is offline, power off the node which does NOT have the cluster resource currently running on it
4. Save the node which is running the cluster group for last - make a note of this machine as it will be the first one you power back on. MY ADDITION: Before powering it down, set the cluster service to manual so that when you restart the server to perform the storage array maintenance, the cluster will not be running - and likewise not generating I/O against the disk array.
MY ADDITION: 5. Restart the server from step 4. Takes the cluster offline "cleanly" and brings the server back on line so that the storage array maintenance can be performed.
6. Update the firmware on the storage array. After that is complete, set the cluster service back to "Automatic".
Start up:
1. Restart the server. Per the previous steps, the server to be restarted will be the server that last hosted the cluster group and the one used to update the firmware on the storage array.
2. RDP into the node, open cluster administrator, and verify that the cluster came back online successfully and everything looks clean
3. Power on the second node.
4. Failover the cluster group across each node in the cluster and validate that everything looks OK
5. Bring your SQL Server groups back online
6. Validate that everything is operational
Is there a better way to do this or official documentation for the process?
Thanks.

FYI: I did use the process outlined above to briing the cluster offline, perform updates, and bring it back online. It worked as I had hoped. As a test, I had also done the same on a test [non-SQL] cluster prior to making the updates to our SQL cluster. Is it the best way to do it? Who knows. Did it work? Yes.

Similar Messages

How to install a DB Instance in a SQL Server 2005 cluster

Hi all,
I have an installation scenaro is install SCS/CI in machine A, and DB instance on a already exist cluster. This is based on Windows 2003 SR2 and SQL Server 2005 cluster. But now after i finish SCS, i don't know how to install the DB instance. Do i just need sign in the active node of the DB cluster and start the sapinst.exe. I am worry about any of my mis-action will broke the cluster.. Appreciate any tips or idea about it, thanks.
Peter

directly start sapinst.exe on the cluster node.

New SQL Server Failover Cluster Installation - No disk is available to select in section "Cluster Disk Slection"

Hello Everyone,
I am in a deep need for your help regarding the problem I am facing.
I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
No roles were created, 2 nodes are available and 1 network is there in the cluster.
If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
Thanks in advance for your support and looking forward for your valuable feedbacks.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Dear Ashwin,
I have granted the privileges mentioned in the link you provided as below:
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

SQL server plugin - cluster?

Ive previously installed a sql server plugin for 11g grid control. works great.
Is there a how-to or a suppoprt note on installing for 2008 SQL server cluster? cant seem to find. In the install guide on the download link for the plugin, the versions supported are listed a
Microsoft SQL Server 2005 Cluster: Active/Active and Active/Passive

SQL Server 2008 R2 is certified on EM 11g, and will also be certified once the EM 12 version of the plug-in is released. We are working on version 2012 and should be certified soon.
Refer to MOS certify for more details.

Sql server 2005, R/3 4.6c and compability mode

Hi
I doing upgrade from 4.6c --> ECC 6.0 on sql server 2005. And i get followin error
SCRIPT MSSINCHK
=================
Msg 468, Level 16, State 9, Server MEDIASP10, Line 55
Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and
"SQL_Latin1_General_CP850_BIN2" in the equal to operation.
Msg 468, Level 16, State 9, Server MEDIASP10, Line 66
Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and
"SQL_Latin1_General_CP850_BIN2" in the equal to operation.
Execution completed successfully
I have checked that collation order is correct.
I think that problem that somehow sql server's compability mode is recognized wrong (sql server 2000 insted sql server 2005).
Any colution on this ?
Br, Juha Niemi

Hi there,
I'm running into this same issue when trying to run PREPARE for the 4.6c to ERP/ECC 6.0 upgrade in phase INITPUT_PRE. I ran several of the queries mentioned in this thread and discovered that the database and instance are both BIN2, and 116230 columns are BIN2, but another 319398 columns are still BIN. Without reverting the database (eek, somehow) back to MSSQL2000 and rerunning instcoll.exe (again, I already did once) or building an alter table query for each one that is out of spec (which according to MSDN won't work on certain cols anyway), how can this be resolved?
for my SID database I have the following column types in count:
SQL_Latin1_General_CP850_BIN2     116230
Latin1_General_BIN     29
NULL     58467
Latin1_General_CI_AS_KS_WS     11
SQL_Latin1_General_CP850_BIN     319398
But the databases are all running BIN2 as such:
Server     SQL_Latin1_General_CP850_BIN2
Master     SQL_Latin1_General_CP850_BIN2
Model     SQL_Latin1_General_CP850_BIN2
TempDB     SQL_Latin1_General_CP850_BIN2
SID     SQL_Latin1_General_CP850_BIN2
The checkdb procedure came back with no errors:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'PD1'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
And the system appears to be functioning correctly, except that the Upgrade Assistant won't let me continue with the mismatched column collation types.
Suggestions? I noticed there was never a resolution posted.
Thanks,
--ben

MS SQL Server 2005 and JDBC

Hi friends
I am new in Java and for the first time I want to write a program to connect to my database on MS SQL Server 2005 to retreive data. I read the tutorial, but I couldn't find there any information about the proper driver name to connect to a SQL Server database ;(
Could you please let me know what I should write as DriverManager.getConnection(????) to make the connection?
Thank you in advance.

I really thank you for your patience and accompanying me. At last I found what the problem was! It was about MS SQL Server 2005 TCP/IP connection!!!! It's disable by default, so it didn't let my java program to login. I enabled it and restart all the SQL services again. But when I executed the program another error appeared: This driver doesn't let you to have integrated secuirty .So I had to bring the 'sa' user id and its password to login to MS SQL Server. And this time it worked!! You are right, I had to cheange the connection URL to bring the port in it.
I am writing a system for a small company in java, and I installed the MS SQL Server 2005 myself and I should manage all the problems myself! So I didn't have anyone to help me but you dear friends.
I really appreciate all your valuable advice.
Now the final code is:
import java.sql.*;
public class DBtest {
     public static void main(String[] args) {
          // Create a variable for the connection string.
          //String connectionUrl = "jdbc:sqlserver://localhost:1433;databaseName=Northwind;integratedSecurity=true;";
          String connectionUrl = "jdbc:sqlserver://localhost;databaseName=Northwind;integratedSecurity=true;";
          // Declare the JDBC objects.
          Connection con = null;
          Statement stmt = null;
          ResultSet rs = null;
             try {
                  // Establish the connection.
                      Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
                      con = DriverManager.getConnection(connectionUrl);
                      // Create and execute an SQL statement that returns some data.
                      String SQL = "SELECT city,country FROM customers";
                      stmt = con.createStatement();
                      rs = stmt.executeQuery(SQL);
                      // Iterate through the data in the result set and display it.
                      while (rs.next()) {
                           System.out.println(rs.getString(0) + " " + rs.getString(1));
          // Handle any errors that may have occurred.
          catch (Exception e) {
               e.printStackTrace();
          finally {
               if (rs != null) try { rs.close(); } catch(Exception e) {}
                   if (stmt != null) try { stmt.close(); } catch(Exception e) {}
                   if (con != null) try { con.close(); } catch(Exception e) {}
}

I can't link to an I series (IBM AS400) server from my sql server 2014 server (64 bit) -- but yes can link on sql server 2005 (32 bit)

I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big). I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64
bit). There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change? How can I get this I series server to link to my sql server 2014 server?
USE [master]
GO
/****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
GO
Rich P

Thank you for this reply. I went to the link and selected the option for DB2s and ran the install. Then I started up SSMS. I copied the same script as above, and it executed successfully. But when I try to run a query against
a table in a database on this linked sever -- I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 8
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Do I need to change the line containing -- @provider=N'MSDASQL', maybe?
this is the query I'm running:
select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
The same exact query runs fine on the sql server 2005 linked server. Is there something I need to configure?
Rich P

Sql server 2005 in server 2012 domain

Hello,
I am running sql server 2005, in a 2003 domain. I plan to possibly upgrade domain/servers to 2012, but am thinking it may create issues with sql 2005?
1. Can sql server version 2005 (32-bit) run ok in a 2012 server domain?
2. If not, will it run ok, if I leave 2003 servers (running mixed mode) until sql 2005 is upgraded?
Thank you
Robert

1. Can sql server version 2005 (32-bit) run ok in a 2012 server domain?
No & May be.
No if you are trying to have multiple version of SQL Server on server ,as per this
article
SQL Server 2005 (the release version and service packs) and earlier versions of SQL Server are not supported on Windows
Server 2012 R2, Windows Server 2012, Windows 8.1, or Windows 8. You will receive a warning in the Action Center if Windows 8.1 or Windows 8 detects an instance of SQL Server 2005.
May be, if you just want to have single instance of SQL Server 2005 on server 2012. Check this:
How to install SQL Server 2005 on Windows 8
2. If not, will it run ok, if I leave 2003 servers (running mixed mode) until sql 2005 is upgraded?
To be able to answer this question in a better way, may I know your SQL Server 2005 version and to which version you want to upgrade? Check for the
supported version and editor upgrade
before going for upgrade along with there hardware and software requirements.
Glad to help! Please remember to accept the answer if you found it helpful. It will be useful for future readers having same issue.

Moving from SQL server 2005 to SQL server 2008 ... for a MS/SQL newbie.

Hello,
I am in charge of moving an existing SAP NW BI (SPS20) from a MS SQL Server 2005 database on Windows Server 2003 (x864/64 bit) Platform to a MS SQL Server 2008 database/Windows Server 2008 Platform (x64/64 bit).
The SID of the SAP system will remain the same.
The thing is that I have always worrked so far on Oracle/Unix environements, windows/MSSQL is an entire new world for me,
so I am quite worried.
I have read many sap notes/installation guides/forum posts regarding this operation, I will describe here my understanding
of the techinical operations that I will need to perfrom.
Could you correct me if I am wrong, as well as give me your comments ?
1/ I will need to perform an SQL server database copy within a homogeneous system copy.
2/First ,I'll have to install on the target environnement the SQL server 2008 database. I'll have to install the SQL Server Database Software with SQL4SAP (no need to install the database server software manually, right ?). Afterwards, I'll install on the target environnent, SAP Netweaver 7.0 SR3 with a modified Instalaltion Master DVD.
3/ On the source environement, I'll perfrom a database backup of the SQL Server 2005 system and restore the database on the target environement. since I choose to perfrom a restore of the database , there is no need to follow all the steps described in sap note 151603 :determine the file structure of the source database, create the directory structure for the target database, etc ...
4/ Once the restoration is finished, I use SAPINST and finish the homogeneous copy : >additional sofware->system copy>target system->central system --> Based on AS Abap --central installation
Your comments are welcome.
Thank you for your attention
Best Regards.
Raoul

Hi Raoul,
you also need a modified Kernel DVD for the installation on SQL 2008 (see SAP Note 1152240).
And don't forget to install and patch the Visual Studio c++ Runtime (also described in that note).
I also would recommend to restore the backup and then install SAP NW 7.0 SR3 and use the restored SQL 2008 database.
So the basic steps are:
1. Perform backup and restore to SQL 2008
1.1 Install SQL 2008 with SQL4SAP
1.2 Backup old database
1.3. Restore backup on SQL 2008
2. Install VC runtime on Win 2008
3. Create modified Kernel DVD
4. Create modified Master DVD
5. Perform system copy target installaton with - additional sofware->system copy>target system--->central system --> Based on AS Abap --central installation and use the SQL 2008 database
You could also use SQL Server 2008 R2 which was release last month.
Please also check Note 1476928
Best,
Sebastian Dusch

MS SQL SERVER 2005 Trial Download

Hi,
I am planning to install ms sql server 2005 trailer edition in my system
i want SSIS SSAS SSRS every thing i want (Standard Edition or Enterprise Edition)
can you please send me currect link MS SQL SERVER installation
Thanks
siva

SQL Server 2005 SP3 Beta is published on the Microsoft web
Download SQL Server 2005 SP3
What's New in SQL Server 2005 SP3
and SQL Server 2005 SP2 is available at:
http://www.microsoft.com/Sqlserver/2005/en/us/
Dannol

SQL Server 2005 Migration Q's

Ok so I have a SQL Server 2005 database and have migrated it to Oracle 10g Rev 2..
All the text fields are right padded :( how do I stop the extra padding on the text fields is there a flag or something ?
thanks

What are the column types in SQL Server and in Oracle?
CHAR types are always padded to their full length with spaces whereas VARCHAR types only store what is actually there.

BPC 5.1 SP11 with SQL SERVER 2005 SP3

Hi all,
i have a BPC 5.1 SP11 single-server installation.
I know the DB Server prerequisite is Microsoft SQL Server 2005 SP2 and cumulative update package 8.
SQL Server 2005 SP3 is supported?
is there any document about compatibility?
have i install SP3 before or after BPC Installation?
thanks

HI Paolo,
SQL Server 2005 SP3 is supported with SAP BPC 5.1 SP3 or any other later version.
We already installed for few customers SP3 and this patch fix bugs into SSAS and also improve some performances regarding SSAS.
So the recommendation will be to apply this patch in your environment because it will bring just benefits.
If you have multiserver installation remmeber that you have to apply the patch in all servers not just into Database server.
Regards
Sorin Radulescu

MSCS cluster installation on win + sql server 2005

Dear Guru,
I want to installing MSCS cluster installation on win 2003 ENT.with sql server 2005 .
Choosing High availability (ABAP)
Please Guide me prerequisit & partation on local & shared disk.
Its Urgent.
Personal mail ID is [email protected]
Regards
Amol kulkarni
Message was edited by:
amol kulkarni

Hi,
You know what ?
Step by step installation is different in every company because each company has a different usage of SAP software.
It is precisly your job as a SAP sys admin, to study the problem, to solve it and to write the step by step documentation.
In my company, it took me one month and my documentation is 250 pages long.
You will not get someone else doing YOUR job instead of you.
The standard SAP documenation is perfectly enough to study your particular case...
Good luck !
Olivier

ERP ECC 6.0 Cluster Installation under MS SQL Server 2005

Hi,
anybody in the world did a ECC 6.0 Cluster installation under MS SQL Server 2005 database?
Can anyone please share some usefull documents to understand... This is new to me and doing it for first time.
Pls help
RGC

Hi,
I'm looking for a customized document for ECC installation (how to document) and not a SAP Standard one as i'm new to cluster. Please share if any.
How to configure the nodes in three tier architecture?
In which node the DB should be installed?
In which node the CI should be installed?
How to configure Central Point of Failure (CPOF)?
How the ECC 6.0 cluster works and how to distribute the resources (SAP) across nodes?
What are the resources that needed for failover from one node to another?
Expecting help.
rgds
RGC

SQL Server 2005 High Availability and Disaster Recovery options

Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how
do we test the failover is working?
Thanks in advance.........
Ione

DR : Disaster recovery is the best option for the business to minimize their data loss and downtime. The SQL server has a number of native options. But, everything is depends upon your recovery time objective RTO and recovery point objective RPO.
1. Data center disaster
Geo Clustering
2. Server(Host)/Drive (Except shared drive) disaster
Clustering
3. Database/Drive disaster
Database mirroring
Log shipping
Replication
Log shipping
Log shipping is the process of automating the full database backup and transaction log on a production server and then automatically restores them on to the secondary (standby) server.
Log shipping will work either Full or Bulk logged recovery model.
You can also configure log shipping in the single SQL instance.
The Stand by database can be either restoring or read only (standby).
The manual fail over is required to bring the database online.
Some data can be lost (15 minutes).
Peer-to-Peer Transactional Replication
Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application
to route traffic to the remaining servers. The remaining servers contain same copies of the data.
Clustering
Clustering is a combination of one or more servers it will automatically allow one physical server to take over the tasks of another physical server that has failed. Its not a real disaster recovery solution because if the shared drive unavailable we cannot
bring the database to online.
Clustering is best option it provides a minimum downtime (like 5 minutes) and data loss in case any data center (Geo) or server failure.
Clustering needs extra hardware/server and it’s more expensive.
Database mirroring
Database mirroring introduced in 2005 onwards. Database Mirroring maintain an exact copy of a database on a different server. It has automatic fail over option and mainly helps to increase the database availability too.
Database mirroring only works FULL recovery model.
This needs two instances.
Mirror database always in restoring state.
http://msdn.microsoft.com/en-us/library/ms151196%28v=sql.90%29.aspx
http://blogs.technet.com/b/wbaer/archive/2008/04/19/high-availability-and-disaster-recovery-with-microsoft-sql-server-2005-database-mirroring-and-microsoft-sql-server-2005-log-shipping-for-microsoft-sharepoint-products-and-technologies.aspx
http://www.slideshare.net/rajib_kundu/disaster-recovery-in-sql-server
HADR Considerations
Need to Understand the business motivations and regulatory requirements that are driving the customer's HA/DR requirements. Understand how your customer categorizes the workload from an HA/DR perspective. There is likely to be an alignment between the needs
and categorization.
Check for both the recovery time objective (RTO) and the recovery point objective (RPO) for different workload categories, for both a failure within a data center (local high availability) and a total data center failure (disaster recovery). While RPO and
RTO vary for different workloads because of business, cost, or technological considerations, customers may prefer a single technical solution for ease in operations. However, a single technical solution may require trade-offs that need to be discussed with
customers so that their expectations are set appropriately.
Check and understand if there is an organizational preference for a particular HA/DR technology. Customers may have a preference because of previous experiences, established operational procedures, or simply the desire for uniformity across databases from
different vendors. Understand the motives behind a preference: A customers' preference for HA/DR may not be because of the functions and features of the HA/DR technology. For example, a customer may decide to adopt a third-party solution for DR to maintain
a single operational procedure. For this reason, using HA/DR technology provided by a SAN vendor (such as EMC SRDF) is a popular approach.
To design and adopt an HA/DR solution it is also important to understand the implications of applying maintenance to both hardware and software (including Windows security patching). Database mirroring is often adopted to minimize the service disruption
to achieve this objective.
HADR Options :
Failover clustering for HA and database mirroring for DR.
Synchronous database mirroring for HA/DR and log shipping for additional DR.
Geo-cluster for HA/DR and log shipping for additional DR.
Failover clustering for HA and storage area network (SAN)-based replication for DR.
Peer-to-peer replication for HA and DR (and reporting).
Backup & Restore ( DR)
keep your server DB backups in network location ( DR)
Always keep your sql server 2005 upto date, in case if you are not getting any official support from MS then you have to take care of any critical issues and more..
Raju Rasagounder Sr MSSQL DBA

Howto take SQL Server 2005 Cluster AND Cluster Group Offline

Similar Messages

Maybe you are looking for