SQL clustering.

Hi experts.
Does sap support clustering SQL but not SAP, meaning can I cluster my sql 2008 r2 but install SAP in a distributed mode and not HA mode?

Hi
Just read the Installation guide and just go thru the links
http://www.microsoft.com/sqlserver/2008/en/us/sap-technical.aspx
Installation
Regards
S

Similar Messages

DNS name for sql clustering instance name

Hi all,
sql 2005 or sql 2008 clustering on windows 2008 R2
We create sql 2005 or sql 2008 clustering. The sql clustering
instance name (DNS name) was created manaully or created automatically in DNS.
is it issue if sql instance name was created manaully in DNS?
Thank you.

Hi,
For the manual create the CNO usually cause may issue, you'd better don't use that method.
The related article:
Windows 2008/ Windows 2008 R2 CNO Recovery
http://blogs.technet.com/b/hugofe/archive/2010/03/11/windows-2008-windows-2008-r2-cno-recovery.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SQL Clustering on C Series server with QLE8152-CNA cards

Is there any documentation on best practices when installing Windows on a c series server
with QLE8152-CNA cards for SQL clustering? Since it will be a bare metal install of Windows, this card will only present a maximum of 2 nics (FI A and FI B) to the Windows OS and because SQL clustering requires multiple nics (heartbeat, regular network), I wanted to know whethere there are guidelines on how to do this or whether it is even supported. I intend on using the failover feature in UCS Manager 1.4 when creating a service profile for these c series server which means I'll end up with 1 NIC presented to the Windows server. Thanks.

Hi Keny,
I tried to powercycle both servers (c260M2 and C460M2) but still no discovered server and also no logg.
I checked
Rack Server Discovery Policy == immediate
Rack management Connecton Policy == Auto Achnowledged
Chassis/Fex Doscovery Policy == 2 Link and Port-Channel (As I installed 2232PP I moved to Port Channel)
I am running UCSM Version 2.1(1e)
FI 6248 Version 5.0(3)N2(2.11e)
2232PP run on same as FI
I also have a connected 5108 with IOM 2104 running on 2.1(1e) Version.
CIMC Version of C260M2 and C460M2 will be checked tomorrow when my kolleague is in the datacenter.
Server Connection is not really the same like in http://www.cisco.com/en/US/docs/unified_computing/ucs/c-series_integration/ucsm2.1/b_UCSM2-1_C-Integration_chapter_011.html
Because I still have no VIC Card but the connections are the same.
C260 GE LOM1 <-> FEX2 Port 11
C260 GE LOM2 <-> FEX3 Port 11
C260 10 GE LOM1 (PCIE Slot4) <-> FEX2 Port 12
C260 10 GE LOM2 (PCIE Slot4) <-> FEX3 Port 12
GE LOM ist position 13 and 10 GE LOM is position 11 in the techspech of c260
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C260/install/overview.html#wp1243740
C460 GE LOM1 <-> FEX2 Port 10
C460 GE LOM2 <-> FEX3 Port 10
C460 10 GE LOM1 <-> FEX2 Port 9
C460 10 GE LOM2 <-> FEX3 Port 9
GE LOM ist postion 8 and 10 GE LOM ist position 7
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C460/install/overview.html#wp1243740
With C260 I also tried a reboot with disconnected 10 GE Ports, but also no discoverd Server until now.
Regards Alois

SSIS installed on 64 bit SQL Clustered Node.

I'm not looking to run SSIS as a clustered service. Initially I just want to install it on node1 of the cluster, eventually I will install on the second node.
So I install the SSIS component via add/remove programs and point to the 64 bit installation of sql server.
Following that, I installed SQL 2005 SP2.
Everything seemed to run though perfectly.
Next, I installed an SSIS package from 32 bit machine via a manifest file using file system method.. great no errors.
Now I go to create a job and I get:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
===
Suddenly, for reasons unknow, now when I attempt to create a new step, I can get into the menu, but if I attempt to select a package I get:
I'm not looking to run SSIS as a clustered service. Initially I just want to install it on node1 of the cluster, eventually I will install on the second node.
So I install the SSIS component via add/remove programs and point to the 64 bit installation of sql server.
Following that, I installed SQL 2005 SP2.
Everything seemed to run though perfectly.
Next, I installed an SSIS package from 32 bit machine via a manifest file using file system method.. great no errors.
Now I go to create a job and I get:
TITLE: Microsoft SQL Server Management Studio
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
ADDITIONAL INFORMATION:
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
If I attempt to explore SSIS pakages from management studio I get:
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
I'm wondering if this is because the package I deployed is 32 bit vs 64 bit? Or maybe I needed hot fixes in addion to SP2 after install the SSIS component after the original install?
Or maybe this was caused by registering of 32 bit DTS.dll files at some point trying to fix the original problem?
Thanks for any help or information.
TITLE: Microsoft SQL Server Management Studio
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
ADDITIONAL INFORMATION:
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
If I attempt to explore SSIS pakages from management studio I get:
TITLE: Microsoft SQL Server Management Studio

Just a note here... while this is an issue, the same error can come up if there are multiple instances and the msdb has moved to a location such that more than one instance tries to share an msdb. If this is the case for example, Instance1 points to
C:\program files\microsoft sql server\mssql\data\msdbdata.mdf and instance2 also points there, you will get this error. Check with:
Select name, physical_name as location, state_desc from sys.master_files where name='N'msdb';
If they both point to the same location (mine did), stop both instances, make a copy of the msdbdata.mdf and msdblog.ldg, restart one of the instances (say instance2) and repoint the copy you just made... say c:\program files\microsoft sql server\mssql.instance2\data
as follows:
alter database msdb modify file(name-msdbdata,filename='c:\program files\microsoft sql server\mssql.instance2\data\msdbdata.mdf
do the same for the log. Restart Instance2 and Start Instance1 and it should resolve the problem.
R, J

SQL Server 2012 - 3 SQL clustered instances - one default/ two named instances - how assign/should assign static ports for named instances

We have two physical servers hosting 3 SQL 2012 clustered instances, one default instance and two named instances.
The default instance is using port 1433 and the two named instances are using dynamic port assignment.
There is discussion about assigning static port numbers to the two named clustered SQL instances.
What is considered best-practice? For clustered named instances to have dynamic or static ports?
Are there any pitfalls to assigning a static port to a named instance that is a cluster?
Any help is greatly appreciated

Hi RobinMCBC,
In SQL server the default instance has a listener which listens on the fixed port which is TCP port 1433. And for the named instance the port on which the SQL server listens is random and is dynamically selected when the named instance of the SQL server
starts.
For Standalone instance of the SQL server we can change the dynamic port of the named instance to the static port by using SQL server configuration manager as other post, however, in case of the cluster, when we change the port no. of the named instance
to the static port using the method described above, the port no. again changes back to the dynamic port after you restart the services. I recommend you changing the Dynamic port of the SQL Server to static port
on all the nodes , disabling and enabling the checkpointing to the quorum.
For more information, you can review the following article about how to change the dynamic port of the SQL Server named instance to an static port in a SQL Server 2005 cluster.
http://blogs.msdn.com/b/sqlserverfaq/archive/2008/06/02/how-to-change-the-dynamic-port-of-the-sql-server-named-instance-to-an-static-port-in-a-sql-server-2005-cluster.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

BizTalk and SQL Clustering

Hi,
I have following questions in clustering:
1. When we say BizTalk cluster. Does that mean that all the server nodes that participate will use the same SQL server cluster, SSO cluster?
2. In case of SQL Server cluster, one is active and one is passive. Will both the servers be replica of each other? I mean to ask will they have same data and configuration? If not then how will it work in a failover scenario because the passive
instance will not the all the information of Active instance?
3. Does a Single node of SQL Cluster includes MsgBox and ManagementDB or are they on different Server?
4. What is the ideal setup of Sql DB? Eg: a different for MsgBox, Management DB, SSO etc?
5. Also, as per my understanding, for high availabilty we should have a BizTalk cluster, Sql cluster and SSO cluster? Is that correct?
Thanks.

Cluster or Not, all BizTalk Servers are configured in the same group and use the Master SSO instance. Only in the case of a cluster the associated DB's are clustered. Does not really change anything w.r.t configuration of the BizTalk Group.
I would refer you to the following links
http://msdn.microsoft.com/en-us/library/aa373130(v=vs.85).aspx and
http://technet.microsoft.com/en-us/library/cc757731(v=ws.10).aspx to get a better understanding of clusters. Clusters in Microsoft are a shared resource so to answer your question, the passive node will (in case of failover) get access to the resources
which were with the active instance and thus no further configu sync is required. Its is the same information from the drives, master DB, services, registry which fails over onto the passive node.
How you utilize the two (or more) nodes of the cluster depends on the load you expect to handle. You may choose to split databases across the TWO nodes [called Active/Active in Microsoft parlance]. This way BOTH the nodes have to be licensed. Each BizTalk
Database has different needs w.r.t frequency of reads/writes, size, etc. The BizTalk Performance Optimization Guide @http://msdn.microsoft.com/en-us/library/ee377064.aspx in addition to best
Practices for Maintaining BizTalk Database @http://msdn.microsoft.com/en-us/library/gg634566.aspx should provide you with guidance on how to split the BizTalk Databases across multiple cluster
nodes.
I would like to provide you ONE configuration fits all BUT that is not possible. The setup of the SQL is highly dependant on the load you expect to address through BizTalk, the HA/DR consideration pertaining to availability/licensing, etc. In short it is
a topic for an infrastructure architect.
BizTalk Cluster is again a subject of requirement. There is no BizTalk Cluster per-se, BizTalk Services (BTSNTSvc.exe) can be clustered so implying that specific host instance can be clustered. As a rule one should only look at clustering those Receive
Protocols which need to be configured for availability. Examples would be FILE, FTP, even DB locations. IIS/Web Services provide HA + scalability through NLB. If you have a SQL Cluster then it is recomended to also cluster SSO on the same set of servers primarily
because it does not require additonal BizTalk Licensing.
Regards.

SQL clustered instance outgoing traffic

Hi,
I have an interesting issue I'm trying to solve. Hopefully I'm missing something really simple. Here's a description of our environment, and the issue I'm having.
2 node SQL 2008 R2 SP2 clustered named instance. There are a total of 4 instance names on the cluster.
Node 1 IP is 192.168.1.121
Node 2 IP is 192.168.1.122
Named instance IPs are 192.168.1.123 to 192.168.1.126
Now here's my dilemma. When I connect to a linked server from one of the 4 named instances, instead of the remote server seeing the named instance IP (eg, 192.168.1.126), it's seeing the IP of the node that is hosting that instance (eg, 192.168.1.121). This
is causing us an issue, as the remote SQL server is behind a firewall, and we expected it to use the instance IP and not the host IP. I have already tried to force the IP in the Server Configuration Manager for the instance name, but this has not
helped.
The server logs for the instance show it listening only on the instance IP (eg. 192.168.1.126 <ipv4> 1433).
All communications to the named instances use the correct IP, and not the node IP. Any help would be greatly appreciated.
Regards,
Hugh McDaid

Hello Hugh,
You need to add an entry to your DNS server that resolves to the virtual IP used by each cluster role, and also add it as a resource for the corresponding role. Make sure the network interface used by SQL server outbound connections has its DNS server set
up correctly.
If that doesn't work, add the DNS name to your hosts file, pointing to the IP address.
"I have already tried to force the IP in the Server Configuration Manager for the instance name, but this has not helped."
So, you've set up an ALIAS for your sql server native client, right? Please note that there are two native clients installed in your servers, one for 32bit applications and the other for 64bits. Make sure the alias is set for BOTH clients. SSMS uses the
32bit aliases, and remember that they only apply locally. If you wanna work with them, tou need to configure the same aliases in each host that needs to connect to the instance.
Is this problem only happening between clustered instances?

SQL Clustered Servers

I’ve installed server 2012 R2 with the Failover Cluster Role and have configured two network interfaces. On the heartbeat NICs for each server I see a “Microsoft Failover Cluster Virtual
Adapter Performance Filter” which is not enabled for the NIC. Should I enable this for the heartbeat NICs for the servers in my cluster?
any and all thoughts would be greatly appreciated.
Leonard Hoffman

Questions about VMware requirements should be directed to VMware. VMware handles things differently from how Microsoft does, so you should ask them about their recommendations.
The issue is with guest cluster traffic potentially getting sent to the host cluster using the same NIC. This is a Hyper-V interaction. So from a Microsoft technology standpoint, if you are not using Hyper-V, it's a good idea to enable it, as
stated earlier. Again, check with VMware.
. : | : . : | : . tim

Can SQL server 2014 instance be introduced into SQL server 2012 clustering

Hello, everyone,
We have SQL server clustering set up in place (it is actually windows clustering), I am wondering if it is possible to introduce SQL server 2014 instance
into this clustering. Please share us your thoughts and experiences.
Thanks

if you are talking about SQL clustering -(FAILOVER CLUSTERED INSTANCES) , yes, you can do that.
you have windows cluster with nodea,nodeb....and you can install two different instances of failover clustered sql - sql 2012 and sql 2014.
Hope it Helps!!

SQL 2014 FCI+AG on Clustered Shared Volumes design

Hello,
I was assigned the task to design a new SQL 2014 environment for my company. Our current environment consists of two clusters of 4 nodes each (8 nodes total for the two clusters) in two datacenters (let's say LA & NY).
Each datacenter is both primary & DR for different applications. Each cluster is active/active and has 9 SQL instances - 1 DEV/2 UAT/4 PROD/2 DR.
We are using Windows Server 2008 R2 SP1 + SQL 2008 R2 SP2 FCIs for HA + DBM for DR, storage is symmetric, LUNs are coming from NetApp SAN filers.
Due to the consolidated nature of the current SQL clusters (some hold 100+ DBs for different applications), the new platform - Windows 2012 R2 and that one WSFC cluster will be used, I decided to go with a new build instead of upgrade.
My plan for the migration to SQL 2014 is as follows:
1. Evict two nodes from each cluster, the 9 SQLs in each datacenter will run on two nodes and I will have two nodes more per site to build the new environment.
Average CPU utilization for each node is 10-20%, total max memory of all SQL Servers per site is 256GB RAM, each node has 2 CPUs x 8 cores each with 256GB RAM. SQLs will still run on two nodes with reasonable performance.
Since the same number of cores is used and we pay SA, there will be no increase in licensing costs for the time of migration to SQL 2014 and to obsolete the SQL 2008 R2 environment.
2. The new cluster will consists of 4 nodes with Windows 2012 R2 (2 in NY and 2 in LA) and will have Node+FileShare majority quorum model with Cluster Managed voting enabled.
3. New SQL 2014 FCIs will be built (9 per site) and will use Clustered Shared Volumes + AlwaysON Availability Groups. Once the new environment is built, databases will be migrated by backup/restore.
Since we will have AlwaysON FCIs+AlwaysON AGs I'm aware that automatic failover cannot be used and the complications with addition of data files on primary databases, that's fine (file paths will be different of primary and DR SQL instances).
My question is - is this a supported configuration from Microsoft - AlwaysON AGs running on CSVs in a multi-site cluster?
I am aware that CSVs are something new for the SQL world, so what are the things I should take into consideration when building this solution? Are there any pitfalls to be wary of?
Any suggestions will be much appreciated.
Thank you in advance,

First, consider building a separate Hyper-V cluster in each data center, and running SQL Server in VMs.
In your proposed configuration if you loose connectivity between your data centers, half of your nodes will loose quorum and go offline. It's simpler to maintain quorum seperately in each data center when trying to run active-active.
Hyper-V adds a bunch of useful stuff, like live migration, storage migration, and basic HA and DR without guest clustering. And the implementation of Hyper-V on CSV is a very common pattern.
You can then present shared hard disks to your SQL VMs to create a FCI on a guest cluster. See
Deploy a Guest Cluster Using a Shared Virtual Hard Disk
Or you can simply use stand-alone instances on the guests, and use AlwaysOn AGs for rolling upgrades and DR.
That said, you proposed configuration is supported. It's a variant of the solution outlined here
AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using Failover Cluster Instances and Availability Groups
The cluster would have asymmetric storage, with the nodes in each data center sharing LUNs (whether on CSVs or not), but the LUNs in a data center would not be visible to the nodes in the other datacenter. You can and should use the same path names
on the primary and DR instances, as outlined in the whitepaper. This is important because otherwise file and filegroup operations will suspend the AlwaysOn data movement.
David
David http://blogs.msdn.com/b/dbrowne/

Unable to start SQL server agent service

hi,
We have 2 Node SQL Cluster that was working fine. Then We migrated the Linux DNS to Windows DNS successfully.Now restarted the SQL Server after it when we try to start the SQL Server Agent service its says the below msg while machine name and cluster
entries are in windows dns and resolving the IP to name and name to IP
Error msg: The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service." error message.
But whenever we set the Linux DNS Server ip in SQL Servers then it successfully starts the service. Now i want to know why its happening and what are the requirements or DNS entries/SPN which we missing when we migrated the linux DNS to windows
dns
Sagar

I was experiencing this issue or one just like it on one of our SQL clusters (SQL Server 2008 R2, two node).
The fix for us was the database Security Login for: NT SERVICE\SQLAgent$<instancename> was missing. The actual service account assigned to the SQL Agent service was a valid domain account and we had the credentials correct in the service
configuration, so no changes were needed there.
Using SQL Server Management Studio we manually added this BUILT IN account ( NT SERVICE\SQLAgent$<instancename> ) to the instance, and then assigned it user role = sysadmin (to go along with the default role = public).
Once this was done, we tried to restart the clustered SQL Agent service and it started and remained started.
Hope this helps someone, we spent over a day pouring over the installation trying to find the cause.
This worked for me, thanks:-)

SQL 2012 install fails with 'Object reference not set to an instance of an object" On windows 8.1 Hyper-V

Hi All,
Could you please help me here? On my Laptop which is running on windows 8.1 Operation system, I enabled the Hyper-V client feature and setup the Windows Fail-over Clustering using Windows 2012 Standard Edition. So, there are three machines which are running
on the Hyper-V. Below are the machine details;
1st machine - Working as Domain controller and its name is "ACONDomainGroup" and allocated to
1GB RAM to use.
2nd machine - Working as Node1 and its name is "AconNODE1W2K12STD"
and allocated to 2.5GB RAM to use.
3rd machine - Working as Node1 and its name is "AconNODE1W2K12STD"
and allocated to 1.5GB RAM to use.
and the windows virtual cluster name is "AconWinCLTR". While I am doing the SQL Cluster Installation, I am getting below mentioned error. all systems have 4.5 .net installed. May you please guide me where and what i am missing to complete sql clustering.....
Update Source: MU
User Input Settings:
ACTION: InstallFailoverCluster
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
ENU: true
ERRORREPORTING: false
FAILOVERCLUSTERDISKS: <empty>
FAILOVERCLUSTERGROUP:
FAILOVERCLUSTERIPADDRESSES: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FEATURES:
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL
Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft
SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network
Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
PID: *****
QUIET: false
QUIETSIMPLE: false
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup
Bootstrap\Log\20140420_052344\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup
Bootstrap\Log\20140420_052344\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.NullReferenceException
Message:
Object reference not set to an instance of an object.
HResult : 0x80004003
Data:
HelpLink.EvtType = 0x9AF1AE5E@0x44A889F9
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.ShouldRuleRun(Rule
rule)
at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.IsRuleSkipped(Rule
rule)
at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.LoadRule(String
ruleId, List`1 ruleProperties, XmlSchema ruleSchema, XmlElementParserFactory elementParser)
at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.LoadRules(IEnumerable`1
ruleIds)
at Microsoft.SqlServer.Configuration.InstallWizard.RunRuleProgressController.Initialize()

Dharmendra, the log details are incomplete are not sufficient enough for I guess anyone to help. Besides, from the details above, I can see that the Failover Cluster Disks are not selected:-
FAILOVERCLUSTERDISKS: <empty>
FAILOVERCLUSTERGROUP:
FAILOVERCLUSTERIPADDRESSES: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana

Getting Back to SQL DBA

Hello, I worked with SQL 7 and SQL 2000 many years ago (I also worked some with Oracle). About 14 years ago I got involved with AIX and then SAN administration. I've been
completely disconnected with SQL Server and Microsoft technologies during that time. I'm now considering getting back into the DBA environment as it seems like there are just more opportunities.
I'm looking for the best way to get retrained. I'm guessing there are SQL DBA certifications similar to the old MCSE. Which certifications should I be looking at? Where is the best place to get the required training (maybe in class room, or web based or even
a great book or set of books)? Should I start my focus on SQL2008 or 2012 or 2014?
Since I have been working more with mainframes and UNIX servers I want to create a simple Windows Server environment at home. Any suggestions? Can I just buy some cheap server and then install Windows server (I don't even know what version) along with SQL.
Is there a way for me to get affordable window server and SQL CDs to install my little lab environment? Does it make sense to get 2 servers so that I can get familiar with Windows/SQL clustering.
Any of your thoughts or suggestions would be extremely helpful.

Welcome back to SQL Server Land! :-)
There are more than one question here! So, I start with the SQL Server certifications.
Please first download this poster: Microsoft IT Academy Certification roadmap poster
Then take a look at this link: Certification
then, please see this one: Microsoft SQL Server certifications
About the version to focus, the latest version is SQL Server 2014, but you can start with 2012 or 2014 both are close.
About the affordable SQL Server, you can choose between two follow options:
1. SQL Server Evaluation (180 days)
2. SQL Server Developer Edition
About creating virtual labs, you can use this link to start:
Experience mission-critical capabilities in a virtual environment
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog

Sharepoint 2013 + SQL Cluster

Hi,
I am working on configuring a Sharepoint 2013 farm, which is using a clustered SQL Server. When I come to configuring SQL aliases, do I use an alias pointing at either SQL Server or the "parent"?
Thanks

Hello ,
You can refer below article for same .
http://blogs.msdn.com/b/sambetts/archive/2013/04/24/sharepoint-2013-and-sql-server-alwayson-high-availability-sharepoint.aspx
http://blogs.technet.com/b/saantil/archive/2012/04/25/sharepoint-and-sql-clustering.aspx
Best Regards Kuldeep Verma
Please remember to click "Mark As Answer" if a post solves your problem or "Vote As Helpful" if it was useful.

Change the IP Addresss of Servers that are members of a Windows Failover Cluster and SQL cluster

Hi all,
I have 3-nodes Windows Server 2012 R2 Cluster, on top of it I have two clustered named SQL 2012 instances installed. We need to change the IPs and subnet for the three physical servers incorporated in the Windows cluster. What will be the impact on
the Windows and SQL clusters? What extra configuration is needed in both Windows and SQL clusters to make sure the service will not fail after changing the IPs?

A similar question was answered
here.
The impact is that your Windows and SQL Server failover clustered instances will be offline during configuration so you need to schedule downtime. Plus, your client applications will not be able to find the new IP addresses immediately, depending on your
DNS TTL value. Work with your network/systems engineers to find out what this value is or validate the existing TTL values on your clustered resources by checking the HostRecordTTL property value. A workaround here is to set the HostRecordTTL property values
of your SQL Server network name to a very low value, say 1 minute, and then change it back to the current one once all of the applications can connect back to them.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL clustering.

Similar Messages

Maybe you are looking for