SQL install on Cluster

Dear Team,
we got a error while installing sql on cluster
We just want to clarify that
"where do we install sql,on clustered shared drive or local drive?"
Our setup is like below.
Having two nodes clustered on one IP,
and two shared drives(Clustered drives) each in of the nodes.
Individual local drives for each node for OS installations
We started installation and while installing SQL it is giving following error
And the error message in detail is
================================================================================
[Error Message]
The shared directory (or command line option INSTALLSHAREDWOWDIR) value for a cluster installation cannot be a directory on a shared disk.
================================================================================
Can any one suggest is there is any work around solution for this.

Hello Envecon SUPPORT,
you must install SQL Server on local disk on both servers, event C:\ is correct in this context.
You should also read the relevant documentation because the standard installer is not recommended by SAP, unless you want to use advanced configuration. In your scenario, basic configuration is enough.
Best regards,
Valerio

Similar Messages

DSC, SQL Server 2012 Enterprise sp2 x64, SQL Server Failover Cluster Install not succeeding

Summary: DSC fails to fully install the SQL Server 2012 Failover Cluster, but the identical code snippet below run in powershell ise with administrator credentials works perfectly as does running the SQL server install interface.
In order to develop DSC configurations, I have set up a Windows Server 2012 R2 failover cluster in VMware Workstation v10 consisting of 3 nodes. All have the same Windows Server 2012 version and have been fully patched via Microsoft Updates.
The cluster properly fails over on command and the cluster validates. Powershell 4.0 is being used as installed in windows.
PDC
Node1
Node2
The DSC script builds up the parameters to setup.exe for SQL Server. Here is the cmd that gets built...
$cmd2 = "C:\SOFTWARE\SQL\Setup.exe /Q /ACTION=InstallFailoverCluster /INSTANCENAME=MSSQLSERVER /INSTANCEID=MSSQLSERVER /IACCEPTSQLSERVERLICENSETERMS /UpdateEnabled=false /IndicateProgress=false /FEATURES=SQLEngine,FullText,SSMS,ADV_SSMS,BIDS,IS,BC,CONN,BOL /SECURITYMODE=SQL /SAPWD=password#1 /SQLSVCACCOUNT=SAASLAB1\sql_services /SQLSVCPASSWORD=password#1 /SQLSYSADMINACCOUNTS=`"SAASLAB1\sql_admin`" `"SAASLAB1\sql_services`" `"SAASLAB1\cubara01`" /AGTSVCACCOUNT=SAASLAB1\sql_services /AGTSVCPASSWORD=password#1 /ISSVCACCOUNT=SAASLAB1\sql_services /ISSVCPASSWORD=password#1 /ISSVCSTARTUPTYPE=Automatic /FAILOVERCLUSTERDISKS=MountRoot /FAILOVERCLUSTERGROUP='SQL Server (MSSQLSERVER)' /FAILOVERCLUSTERNETWORKNAME=SQLClusterLab1 /FAILOVERCLUSTERIPADDRESSES=`"IPv4;192.168.100.15;LAN;255.255.255.0`" /INSTALLSQLDATADIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBDIR=M:\SAN\SQLData\MSSQLSERVER /SQLUSERDBLOGDIR=M:\SAN\SQLLogs\MSSQLSERVER /SQLTEMPDBDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLTEMPDBLOGDIR=M:\SAN\SQLTempDB\MSSQLSERVER /SQLBACKUPDIR=M:\SAN\Backups\MSSQLSERVER > C:\Logs\sqlInstall-log.txt "
Invoke-Expression $cmd2
When I run this specific command in Powershell ISE running as administrator, logged in as domain account that is in the Node1's administrators group and has domain administrative authority, it works perfectly fine and sets up the initial node properly.
When I use the EXACT SAME code above pasted into my custom DSC resource, as a test with a known successful install, run with the same user as above, it does NOT completely install the cluster properly. It still installs 17 applications
related to SQL Server and seems to properly configure everything except the cluster. The Failover Cluster Manager shows that the SQL Server Role will not come on line and the SQL Server Agent Role is not created.
The code is run on Node1 so the setup folder is local to Node1.
The ConfigurationFile.ini files for the two types of installs are identical.
Summary.txt does have issues..
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred during the setup process of the feature.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x86D8003A
Error description:             The cluster resource 'SQL Server' could not be brought online. Error: There was a failure to call cluster code from a provider. Exception message: Generic
failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation. .
It feels like this is a security issue with DSC or an issue with the setup in SQL Server, but please note I have granted administrators group and domain administrators authority. The nodes were built with the same login. Windows firewall
is completely disabled.
Please let me know if any more detail is required.

Hi Lydia,
Thanks for your interest and help.
I tried "Option 3 (recommended)" and that did not help.
The issue I encounter with the fail-over cluster only occurs when trying to install with DSC!
Using the SQL Server Install wizard, Command Prompt and even in Powershell by invoking the setup.exe all work perfectly.
So, to reiterate, this issue only occurs while running in the context of DSC.
I am using the same domain login with Domain Admin Security and locally the account has Administrators group credentials. The SQL Server Service account also has Administrators Group Credentials.

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.

How to install sp2 for sql server 2012 , where sql server 2012 instnce is installed in cluster mode

Hi Everyone,
I want to install sp2 for sql server 2012, My sql server 2012 instance is installed in cluster mode.
Please suggest the best practice to install sp2 , what are prerequisite and recommendation.
Please share installation guide for sp2 in cluster instance, if any one have.
Thanks All
Aditya

Did you searched a bit before posting question.
Please read
https://support.microsoft.com/kb/958734?wa=wsignin1.0
http://blogs.msdn.com/b/john_daskalakis/archive/2014/09/05/how-to-install-a-service-pack-at-a-sql-server-2012-failover-instance-best-practices.aspx
http://blogs.msdn.com/b/jason_howell/archive/2012/08/28/how-to-patch-sql-server-2012-setup-with-an-updated-setup-package-using-updatesource-to-get-a-smart-setup.aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SCCM 2012 - Migrating SQL components to cluster including Reporting Services

Current SCCM 2012 environment:
- CAS with database on remote SQL (non-cluster) server in a named instance - SQLSRV\CASINST
- SQL Reporting Services in also installed in the SQLSRV\CASINST instance
- The SCCM Reporting Services Point role is installed on the SQLSRV\CASINST instance
- Primary server with database on the same remote SQL (non-cluster) server in a different named instance - SQLSRV\PRIINST
Now I would like to move all of the database stuff to an existing SQL 2008 R2 cluster (SQLCLUSTER) and decommission the SQLSRV server. SQLCLUSTER already exists and the default instance is already in use (for other applications) for both database engine
services and reporting services.
From my understanding:
- SQL 2008 R2 Reporting Services cannot be clustered
- Best practise is to install Reporting Services Point on a remote site server rather than a CAS server
- SSRS can be installed on nodes in SQL cluster as standalone installs - with the caviat that they don't use instance names already in use
So I plan to:
- Move CAS database to new named instance on cluster eg SQLCLUSTER\CASINST
- Move primary database to new named instance on cluster eg SQLCLUSTER\PRIINST
- Install SQL Reporting Services on one of the cluster nodes (unclustered) using a named SSRS instance eg SQLCLUSTERNODE1\SCCMREPORTING
- This article points out some interesting results of not have a default instance - http://magalhaesv.wordpress.com/2012/05/24/system-center-configuration-manager-x-sql-server-reporting-services-x-wmi-english-version/
- Move Reporting Services Point from SQLSRV\CASINST to the cluster node eg SQLCLUSTERNODE1\SCCMREPORTING
I have read on some forums (eg
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/40ad0cb4-a464-4576-b824-957ed6e1b2e2) things like '' If you have an app like SCCM that requires a default instance of SSRS, you are out of luck if your cluster already has a default
instance of the database engine.", but I cannot find this anywhere in Microsoft documentation. From the MS documentation (http://technet.microsoft.com/en-us/library/7fd0d4f5-14e0-4ec7-b2e6-3b67487df555#BKMK_InstallReportingServicesPoint)
I understand that as long the current user has read access to WMI on the remote site server where SQL Reporting Services is installed, you should be able to use a named instance for SQL Reporting Services and successfully install the Reporting Services Point
on it.
So a 2 part question:
- Anybody see any obvious flaws in my high level plan?
- Anybody care to comment on the SCCM requiring a default instance of SSRS?
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

Yes, I know this is an old post, I’m trying to clean them up, Did you figure this out, if so how?
http://www.enhansoft.com/
Hi Garth,
Yes we moved the DBs and RS as outlined above. As expected, we needed to have a default instance of RS because otherwise the SCCM console doesn't see the Reporting Services instance when you try to deploy the Reporting Services site role.
So the above plan worked.
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

SQL Server Failover Cluster Questions

Dear All,
            I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.
1.  I am receiving MSDTC Warning. I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not. I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases
and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?
http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/
2. During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME". Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group
would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.
3. During the instance creation, one needs to provide "SQL Server Network Name". As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this
for all instances that I create or this is only required once in the cluster:
4. During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features. As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through
it, so which features should be selected? so that there is less workload on the server.
5. All the instances use TempDB for databases that are present inside it. What would be the best practice with respect to TempDB. One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What
should be the ideal size of the TempDB LUN?
6. Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?
Thanks in advance.

Hello,
1.You can run the Microsoft Distributed Transaction Coordinator service (MSDTC) as a clustered resource on a failover cluster server for increased reliability, based on the failover capabilities of the clustered servers. You can
refer to the MSDTC section of the following blog about determine whether the Microsoft Distributed Transaction Coordinator (MSDTC) cluster resource must be created.
Reference:http://msdn.microsoft.com/en-us/library/ms189910.aspx#MSDTC
2. The Cluster Resource Group is where SQL Server failover cluster resource will be placed. Each clustered SQL Server will belong to a Failover
Cluster Resource Group. For example, if you had configure a two node SQL Server Cluster, each clustered instance on the two node belong to a same Cluster Resource Group.
You can change the Cluster Resource Group name, but notes the following name is reserved and already used as Resource Group names: Available Storage, Cluster Group.
3. Each SQL Server cluster is assigned a virtual Network name and IP address, which client applications use to connect to the clustered SQL Server.
4. Not familiar with SCVMM, SCOM, Orchestrator, but you should install the Database Engine Services and SQL Server Management tools.If you want to use SQL Server Reporting Services, you can install Reporting Servers, but Report Server service cannot participate
in a failover cluster.
5. You can use isolated disk for user database and temp DB of each SQL Server Cluster
6. Yes. You should use Cluster Disks which add to Clustered Shared Volumes to host the data file and log of databases.
http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

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..

How to add a new instance to a 2 node SQL 2008 R2 Cluster under the same networkname

Hello All,
I'm fairly new to sql and have just deployed a new 2 node SQL 2008 R2 cluster.
During installation, I created a networkname SQLCLU and a named instance I01.
I now would like to add another Instance (I02) under the same networkname.
What is the proper procedure to do this?
I don't believe that I should do this using the action: "New SQL Server failover cluster" from the setup menu, but rather using the action "New Installation or add features to an existing installation"
With the second option, I'm however not sure how I should make this instance clustered..
Should I also execute the "New Installation or add features to an existing installation" action on the 2nd node in the cluster?
Many thanks for your advice!
Filip

You cannot use the same network name for 2 instances. You need to use a different network name for the second instance I02
A failover cluster instance contains:
A combination of one or more disks in a Microsoft Cluster Service (MSCS) cluster group, also known as a resource group. Each resource group can contain at most one instance of SQL Server.
A network name for the failover cluster instance.
One or more IP addresses assigned to the failover cluster instance.
One instance of SQL Server that includes SQL Server, SQL Server Agent, the Full-text Search (FTS) service, and Replication. You can install a failover cluster with SQL Server only, Analysis Services
only, or SQL Server and Analysis Services
http://msdn.microsoft.com/en-in/library/ms179410(v=sql.105).aspx

SQL PATCH IN CLUSTER ENVIRONMENT

Dear All,
One of my client is having SAP ECC6.0 , SQL 2005 , windows 2003 64 bit.
They are having SQL 2005 version 9.00.1399 and according to SAP it is no more supported so they want to upgrade it to 9.00.4035.
In DEV and QAS (non cluster environment) they are already having 9.00.4035 .
- Can you guys please guide me about how to apply SQL patch in Cluster environment.
- Shall I apply patch 9.00.4035 directly from 9.00.1399
- Any recommendations before and after applying patched
Kindly guide.
Regards,
Rmoihnitii

Hello my friend
Unfortunately this is not a zero down time solution since Database Services and Analysis Services checkboxes will not be available while patching SP3:
1. Launch SP3 package on the active node;
2. Select authentication mode for the instance you are going to update;
3. Enter credentials of the login you want to run service pack on behalf of;
4. Click all the way next to start installing;
Then you need to update the inactive node it is necessary to execute all the steps except steps 2 and 3. There can be some problems with updating database service in the cluster. Restart of each node of the cluster and restart of the cluster service usually resolves all the problems. After restart try to update database service one more time.
Regards,
Effan

Installing MSCS cluster installation

HI Guru,
I want to installing MSCS cluster installation on win 2003 ENT.with sql server 2005 .
Choosing High availability (ABAP)
Please Guide me prerequisite & partation on local & shared disk.
Its Urgent.
Personal mail ID is [email protected]
Regards
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

Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill Thacker

Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Sql server 2008R2 cluster (active-passive) prerequistites

Hi All,
Please any one can help me in exact prerequisites for installing sql server 2008R2 cluster server(two node).
Thanks in advance.
Maheshwar Reddy

Hi Please find the pre-requisites for SQL server cluster installation .
Before Installing SQL cluster we need to have a Windows Cluster with required shared storage space and DTC Service configured in Windows
Cluster.
Be ready with the plan of where the SQL to be installed and where the Database, Log, Temp DB and Backup are to be stored.
If you require SOP for this please share your mail id .i will send the same .

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.

Apply monthly Windows 2008 r2 updates within SQL Server 2008 cluster

Hello is applying Windows updates within 2 node SQL Server 2008 cluster (active-passive) as simple as download/install the windows update on the passive node, then failover, then apply on other node, and then fail back over ?...or are there other needed/recommended
steps ? Thanks in advance.

Thanks for your reply Shanky_621 much appreciated.
In your link provided http://support.microsoft.com/kb/174799 it looks like the steps order is slightly different from this link of
http://technet.microsoft.com/en-us/library/cc731291.aspx which mentions...
"...where the recommended sequence is to move all services and applications off of the node, pause the node, then apply software updates to the node."
...does it matter which is done first ('Pause' or 'move Services/Application') or can I simply go to the Passive node (say 'B' where there are no Services or Applications currently on it), 'Pause' it, apply the Windows updates, then 'Resume' it, &
reboot ?

Error while installing Oracle Cluster Ready Services Release 1 (10.1.0.2)

Hi all,
I am trying for RAC 10gR1 (10.1.0.2) using two machines with Windows 2000 Server. For this I need to install Oracle Cluster Ready Services Release 1 (10.1.0.2).
Machine details are as follows:-
Node 1:
Computer Name:     RAC1
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection 2: (Used for Public Interface)
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection: (Used for Private Interface between the two nodes)
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.10.10.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Node 2:
     Computer Name:     RAC2
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection 2: (Used for Public Interface)
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.181
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection: (Used for Private Interface between the two nodes)
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.10.10.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
I have made following entries in Hosts file of both the machines:-
192.168.1.65     RAC1
192.168.1.181     RAC2
10.10.10.11     RAC01-PRIV
10.10.10.12     RAC02-PRIV
192.168.1.201     RAC01-VIP
192.168.1.202     RAC02-VIP
I have completed all the pre-installation steps, i.e. configuring the disk for storage, and both the machine are communicating each other through there Private and Public interfaces. Now the problem appears when I am installing Oracle Cluster Ready Services, at the end of Installation following message appears and the auto configuration steps fails.
================================================================================================================
Output generated from configuration assistant "Oracle Cluster Ready Services Configuration Assistant":
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: rac1 rac01-priv rac1
node 2: rac2 rac02-priv rac2
Creating OCR keys for user 'administrator', privgrp ''..
Operation successful.
Now formatting voting device: \\.\votedsk
Successful in setting block0 for voting disk.
Format complete.
Step 1: checking status of CRS cluster
Step 2: configuring OCR repository
Step 3: configuring safe mode for CRS stack
Step 4: Starting up CRS stack on all nodes
RAC1 service OracleCSService in improper PENDING state, err(997)
RAC2 service OracleCSService in improper PENDING state, err(997)
Configuration assistant "Oracle Cluster Ready Services Configuration Assistant" failed
================================================================================================================
Output generated from configuration assistant "Oracle Notification Server Configuration Assistant":
Configuration assistant "Oracle Notification Server Configuration Assistant" failed
================================================================================================================
Output generated from configuration assistant "Oracle Private Interconnect Configuration Assistant":
PRIF-10: failed to initialize the cluster registry
Configuration assistant "Oracle Private Interconnect Configuration Assistant" failed
===============================================================
I would be highly obliged if any one tell me why it is happing like this and what could be the possible remedy.
Waiting for the respone.
With Regards
Dinesh
[email protected]

Hi user478171,
I have the same problem with two nodes in Windows 2003 with RAC 10g R2, but I don't have idea to solve.
Please advice me
Thanks advances
regards,
IvanR

SQL install on Cluster

Similar Messages

Maybe you are looking for