SQL 2012 Cluster Multi Instances !

Hello,
For SQL 2012 Cluster Multi Instances setup, Does the Storage Space should be different for each instance or can be the same?
Kindly help me in this.
Regards !

Hello,
The reason is that's what Microsoft decided to do. It's also that way because disks are a clustered resource and belong to a single resource group. Each SQL Server install will have its own resource group. If a disk could belong to more than one resource
group, and a group fails - then all of the instances with the same disk would fail. That's not what you'd want from an HA solution. Microsoft clustering is a shared nothing model to which this is part of.
Before installing:
http://technet.microsoft.com/en-us/library/ms189910.aspx
◦The base drive, the one with the drive letter, cannot be shared among failover cluster instances.
Creating a new SQL Server Cluster:
http://technet.microsoft.com/en-us/library/ms179530.aspx
-Sean
Sean Gallardy | Blog |
Twitter

Similar Messages

Adding existing SQL Server 2012 to a New SQL 2012 Cluster

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the cluster
without losing any functionality. All servers will be built with same drive letter.

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the
cluster without losing any functionality. All servers will be built with same drive letter.
No its not possible to convert standalone installation to cluster.Moreover first you need to configure Windows cluster then backup all SQL server databases logins jobs packages and install fresh instance of SQL Server in cluster aware mode
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Sql 2008 r2 cluster side by side with sql 2012 cluster on Windows 2008 R2

We have a SQL 2008R2 active/passive SQL cluster running on Windows 2008 R2 cluster.
I would like to add a SQL 2012 clustered instance to the same Winows 2008 R2 cluster.
Are there any issues involved having a SQL 2008 R2 clustered instance running side by side with a SQL 2012 instance in same Windows 2008 R2 cluster?
Are there any pitfalls/"gotchas" to watch for with SQL 2012 cluster install?
Thank you so much!

Hello,
Two instances, one SQL Server 2008 and the other SQL Server 2012, side-by-side, is fully supported.
I would like to recommend you to assign a different port (not port 1433) to the non-default instance
to avoid an IP address conflict between both instances.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Hyper-V guest SQL 2012 cluster live migration failure

I have two IBM HX5 nodes connected to IBM DS5300. Hyper-V 2012 cluster was built on blades. In HV cluster was made six virtual machines, connected to DS5300 via HV Virtual SAN. These VMs was formed a guest SQL Cluster. Databases' files are placed on
DS5300 storage and available through VM FibreChannel Adapters. IBM MPIO Module is installed on all hosts and VMs.
SQL Server instances work without problem. But! When I try to live migrate SQL VM to another HV node an SQL Instance fails. In SQL error log I see:
2013-06-19 10:39:44.07 spid1s      Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.07 spid1s      SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.07 spid1s      Write error during log flush.
2013-06-19 10:39:44.07 spid55      Error: 9001, Severity: 21, State: 4.
2013-06-19 10:39:44.07 spid55      The log for database 'Admin' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2013-06-19 10:39:44.07 spid55      Database Admin was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.33 spid36s     Starting up database 'Admin'.
2013-06-19 10:39:44.58 spid36s     349 transactions rolled forward in database 'Admin' (6:0). This is an informational message only. No user action is required.
2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail (failure): alignBuf 0x000000001A75D000, writeSize 0x400, filePos 0x156adc00
2013-06-19 10:39:44.58 spid36s     blankSize 0x3c0000, blkOffset 0x1056e, fileSeqNo 1313, totBytesWritten 0x0
2013-06-19 10:39:44.58 spid36s     fcb status 0x42, handle 0x0000000000000BC0, size 262144 pages
2013-06-19 10:39:44.58 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.58 spid36s     Error: 5159, Severity: 24, State: 13.
2013-06-19 10:39:44.58 spid36s     Operating system error 170(The requested resource is in use.) on file "v:\MSSQL\log\Admin\Log.ldf" during FixupLogTail.
2013-06-19 10:39:44.58 spid36s     Error: 3414, Severity: 21, State: 1.
2013-06-19 10:39:44.58 spid36s     An error occurred during recovery, preventing the database 'Admin' (6:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected,
contact Technical Support.
In windows system log I see a lot of warnings like this:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Microsoft-Windows-Ntfs" Guid="{3FF37A1C-A68D-4D6E-8C9B-F79E8B16C482}" />
<EventID>140</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000008</Keywords>
<TimeCreated
SystemTime="2013-06-19T06:39:44.314400200Z" />
<EventRecordID>25239</EventRecordID>
<Correlation
/>
<Execution
ProcessID="4620" ThreadID="4284" />
<Channel>System</Channel>
<Computer>sql-node-5.local.net</Computer>
<Security
UserID="S-1-5-21-796845957-515967899-725345543-17066" />
</System>
- <EventData>
<Data Name="VolumeId">\\?\Volume{752f0849-6201-48e9-8821-7db897a10305}</Data>
<Data Name="DeviceName">\Device\HarddiskVolume70</Data>
<Data Name="Error">0x80000011</Data>
</EventData>
</Event>
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{752f0849-6201-48e9-8821-7db897a10305}, DeviceName: \Device\HarddiskVolume70.
({Device Busy}
The device is currently busy.)
There aren't any error or warning in HV hosts.

Hello,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Fanny Liu
If you have any feedback on our support, please click
here.
Fanny Liu
TechNet Community Support

Time-out issue Always on SQL 2012 Cluster

Currently I'm working on a large deployment of a SharePoint 2013 environment (stretched farm over 2 DC's). We are using a SQL 2012 alwayson multisubnet cluster (each DC has 1 SQL node). During the installation of SharePoint we encountered several connection
time-out errors from the SQL environment. (Exception calling "Open" with "0" argument(s): "Connection Timeout Expired. The timeout period elapsed during the post-login
phase. The connection could have timed out while waiting for server to complete the login process and respond;)
Steps we follow for SharePoint installation are:
Steps to configure SharePoint 2013 on an AlwaysOn Availability group:
1>Create SharePoint databases (with the PowerShell script)
Configure a SQL alias for a consistent SQL instance name.
Create farm on SQL instance/replica 1 (one of the SQL nodes), creating all databases needed (service-apps & web-apps). -->
we are connected directly to 1 SQL node and not connecting to the cluster. Installation server is in same DC as the SQL node.
Stop SharePoint so databases remain static during migration to an AlwaysOn cluster.
2>Move database to AlwaysOn high-availability group.
Restore all the DBs onto SQL replica 2 (with NORECOVERY).
Create AlwaysOn availability group, or use existing
Join the replica 2 databases to availability group.
Create listener.
3>Migrate SharePoint onto AlwaysOn on cluster
Make all SharePoint DB MultiSubnetFailover aware with PowerShell Cmdlet
Reconfigure SQL alias for new listener
àat this point the SharePoint farm is connecting to the SQL cluster (listener of AlwaysOn availability group of the SQL Instance), but we never reached this point so far.
Restart SharePoint services with updated alias.
Event errors and SQL log errors that I found:
Date,Source,Severity,Message,Category,Event,User,Computer
09/18/2014 07:34:59,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPAG_CU8000001105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:59,MSSQL$SPAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:52,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPWMAG_CU8000002105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:52,MSSQL$SPWMAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:47,Service Control Manager,Information,The WMI Performance Adapter service entered the running state.,(0),7036,,CU8000000015
09/18/2014 07:32:41,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPSDAG_CU8000003105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:32:41,MSSQL$SPSDAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:31:09,PowerShell,Information,Engine state is changed from Available to Stopped. <nl/><nl/>Details: <nl/> NewEngineState=Stopped<nl/> PreviousEngineState=Available<nl/><nl/> SequenceNumber=61464<nl/><nl/> HostName=OpsMgr
PowerShell Host<nl/> HostVersion=7.0.5000.0<nl/> HostId=32012185-8d9a-41c2-be56-91929c02f1e8<nl/> EngineVersion=4.0<nl/> RunspaceId=af176e01-185d-4574-ab9b-0fd745178d29<nl/> PipelineId=<nl/> CommandName=<nl/> CommandType=<nl/> ScriptName=<nl/> CommandPath=<nl/> CommandLine=,(4),403,,CU8000000015
We are not allow to update/write in the DNS for the multisubnet cluster IP registration, so I think that explains the "failed registration
" error. But can this explains our time-out errors during the SharePoint installation? For the installation we are connection directly to 1 SQL node and not to the SQL
cluster.
Any help is appreciated!
Ronald Bruinsma - Independent SharePoint Consultant - iDocs.info - The Netherlands -- Please don't forget to propose this post as an answer or mark it as helpful if it did help you. Thanks.

Don't just change the connection timeout on your SharePoint farm. This will just hide the real issue. From your error message, it seems that the DNS record for the Availability Group listener name is not being written. Talk to your AD administrators to validate
if dynamic DNS registration is configured for the DNS servers. If it is, AD will create the DNS entry of the virtual computer object for the Availability Group listener name. The WSFC should also have Create Computer Objects permission in the AD Organizational
Unit where your Availability Group listener name will be created.
On a side note, make sure that you configure a separate SharePoint 2013 farm for your DR environment that will use the content databases joined in the Availability Group. For a stretched farm deployments, latency should be less than 1ms one way as
per this article. And while you can add your admin content and config databases on the Availability Group, asynchronous commit is
not supported.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL 2012 Cluster install - error msg

Hi
I am in the process of installing SQL server 2012 cluster, on the Instance configuration page where i gave "SQL Server Network Name" as "appsqlclsA" and the "Named Instance" as "Ins01". I am getting the below
error msg, i am not sure exactly what permissions i need.
"The SQL Server failover cluster network name "appsqlclsA" is not valid. The name must be a valid DNS and Wins name.
So what i understand is i do not have permission to create the virtual sql name account "appsqlclsA"" in the AD.
But i need help finding exactly what permission i need.
Thank you for your help

Take a look at this
TechNet article for assigning permissions in Active Directory to create the virtual computer object. Either you are granted the appropriate permissions or the virtual computer object be pre-staged prior to installation
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL 2012 HADR failover instance

Greetings all.
Currently here is the setup we have built out. All are Server 2012 R2 OS
2 node FCI shared storage SQL 2012 servers in production site. Failover works flawlessly between them. WSFC setup between them
1 node in DR, member of the WSFC with the 2 servers above but not FCI, seperate storage infrastructure but same disk drive letter setups
Availability Groups setup between the 2 that are fully synchronized
We are going to have a planned primary outage in the primary DC. Nerves are getting the better of me in regard to the setup. I know the data is there and it can be accessed. My question is that once i perform the failure of the two nodes
in the FCI how are my applications going to know how to reach the HADR server as it is on a seperate instance? Does SQL aliasing need to be setup in the configuration to make it work properly or am i being overly paranoid at this point?

The listener name is similar to a cluster client access point. When you create a listener name, it will create a virtual computer object in Active Directory and, with AD-integrated DNS, will create the corresponding DNS entries. Depending on how you configure
your cluster, the listener name should have 2 virtual IP addresses - one for the production network and another for the DR network - and will be written to the DNS. That being said, your listener name has to be unique so that the network traffic can be properly
routed to the instance running the Availability Group. You also need to configure the appropriate TTL value for the listener name or use the latest SQL Server client APIs to take advantage of the MultiSubnetFailover parameter in the application connection
string
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL 2012 Cluster- How to or Steps to Move Tempdb Files from Local drive to Shared volume

Hi..
I did Installation of SQL Server 2012 Cluster. During this setup I installed Tempdb Files on Local drive. Now I want to move this tempdb files from local drive to Shared Drive . When I am trying to move I am getting below error.
Does any one can help me or provide the steps to move this tempdb files from local drive to Shared Drive ?
Msg 5184, Level 16, State 1, Line 1
Cannot use file 'Z:\Tempdb\tempdb.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource
of the Sql Server does not have a dependency on it.
Thanks
Regards..
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Hi,
The error message may be thrown out when you attempt to create a database on another shared cluster drive when the SQL Server resource is not dependent on that disk.
Check if you are in the scenario which mentioned in the following article:
How to create databases or change disk file locations on a shared cluster drive on which SQL Server was not originally installed
http://support.microsoft.com/kb/295732/en-nz
Here is a thread with similar issue:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c9f80af7-5b51-4c43-a2a0-f9c7d97aa41d/sql-disk-dependency-problem-on-sql-2008-cluster-including-errors
Hope it helps.
Tracy Cai
TechNet Community Support

Sql 2012 cluster

Hi guys
We have the following scenario:
Our sql servers are in a cluster consisting of two servers. All running sql 2012. Both off the servers DNS is configured for a primary in a local AD site and a secondary DNS to a different AD site.
When we reboot the local dc in the local AD site, sql get the following error:
"Cannot generate SSPI context."
When the local DC is back online everything works fine.
My question is why dont SQL query the secondary DC? Or is this a SPN/kerberos issue? Or should we rather add a secondary dc in the local site aswell?
Thanks

This could be a DNS issue or a DC replication issue. Check the primary and alternate DNS settings of the network adapter on both nodes to make sure they are configured to connect to the correct DNS servers
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Install SQL 2012 sp1 Named Instance on SQL 2008 r2 Cluster

I am attempting to add a 2012 instance to my 2008r2 cluster, but at 'cluster node configuration' step, the drop down for sql server instance name is empty

Hi,
Seems you have worked it out. You can mark the answers accordingly. It will be nice to let thread stay there so other
community members
can benefit from it.
Please let us know if you would like further assistance.
Thanks.
Tracy Cai
TechNet Community Support

SQL 2012 Cluster Installation AddNode

Hi All.
I am trying to do a clsuter installation and I get the error below, when I try to add the second node as part of the cluster.
Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQL_INSTANCE
Error result: -2061828095
Result facility code: 1307
Result error code: 1
Please review the summary.txt log for further details
Microsoft (R) SQL Server 2012 11.00.3000.00
Copyright (c) Microsoft Corporation. All rights reserved.
(01) 2015-01-28 13:24:49 SQLBrowser: This is a cluster-related scenario. IsCluster = 'True'.
(01) 2015-01-28 13:24:49 SQLBrowser: CalculateStartMode: bIsNamedInstance = 'True', bIsDbmsEngineInstall = 'True', bEngineNetworkProtocolsOn = 'True', bIsAsInstall = 'False',bIsCluster = 'True'.
(01) 2015-01-28 13:24:49 SQLBrowser: CalculateStartMode: Named instance needing SQL Server Browser: setting intended SQL Server Browser StartMode property to 'Automatic'.
(01) 2015-01-28 13:24:49 SQLBrowser: EndMethod Type='SqlBrowserPublicConfig' Method='CalculateStartMode'.
(01) 2015-01-28 13:24:49 SQLBrowser: EndMethod Type='SqlBrowserPublicConfig' Method='Calculate'.
(01) 2015-01-28 13:24:49 SQLEngine: Obtaining FDLauncher service account from active node
(01) 2015-01-28 13:24:49 SQLEngine: Active node is SERVERNAME
(01) 2015-01-28 13:24:49 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine SERVERNAME
(01) 2015-01-28 13:24:49 Slp: Sco: Attempting to open registry subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQLINSTANCE
(01) 2015-01-28 13:24:49 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.FinalCalculateSettingsAction" threw an exception during execution.
(01) 2015-01-28 13:24:50 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQLINSTANCE ---> Microsoft.SqlServer.Configuration.Fulltext.FulltextFeatureException: Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQLINSTANCE
(01) 2015-01-28 13:24:50 Slp: at Microsoft.SqlServer.Configuration.Fulltext.Util.GetFDLauncherAccountFromRegistry(ServiceContainer Context, SqlRegistryKey keyHKLM)
(01) 2015-01-28 13:24:50 Slp: at Microsoft.SqlServer.Configuration.Fulltext.FulltextConfigurationPublic.Calculate()
This is the detailed log section when I look in the folder of the cluster log.

Hi MrFlinstone,
As discussed in this similar
thread, it seems to be an known issue when adding a second node in a SQL Server failover cluster using option “
Integration Installation with Add Node ”.
To work around this issue, you can use the Advanced/Enterprise installation option to install SQL Server failover cluster.
SQL Server Advanced/Enterprise failover cluster installation consists of the following steps:
• On each node that is a possible owner of the new SQL Server failover cluster, follow the Prepare Failover Cluster setup steps that are listed in the
Prepare section. After running the Prepare Failover Cluster on one node, Setup creates the Configuration.ini file that lists all the settings that you specified. On the additional nodes to be prepared, you can supply the auto-generated Configuration.ini
file from first node as an input to the Setup command line.
• After the nodes are prepared for clustering, run Setup on one of the prepared nodes. This step configures and finishes the failover cluster instance.
Reference:
Create a New SQL Server Failover Cluster (Setup)
Installing a Two-node SQL Server 2008 Cluster - Advanced option
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

SQL 2012 cluster installation fails with an IP address error

I am building an eight node cluster and have successfully installed two SQL instances on it. Now, I cannot install any additional instances because of the following error:
The resource with identifier 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (WEBAPPS)' Resource='SQL IP Address 1 (ACHSQLWebapps)'' could not be found on the cluster. Please check if it exists.
I can verify that the installation builds the SQL Name and then adds the IP address. After the IP address comes online, the installation stops and that error pops up. It results in a failed install that must be removed by the "Remove Node"
wizard.
A search on the web comes up empty. Any ideas?

Hello,
To add a node to an existing SQL Server failover cluster, We should run SQL Server Setup on the node that is to be added to the SQL Server failover cluster instance.Please verify the account that you using has permission to log in as a service on all nodes
of the failover cluster.For local installations, you must run Setup as an administrator.
Reference:http://msdn.microsoft.com/en-us/library/ms191545(v=sql.110).aspx
Regards,
Fanny Liu
If you have any feedback on our support, please click
here.
Fanny Liu
TechNet Community Support

How is the impact when a sql server cluster instance failover to a downlevel version node?

Hi,
I have a one instance two nodes sql 2012 cluster, node1's sql 2012 version is 11.0.5522, node2's sql 2012 version is 11.0.3000, node1 is active.
When sql server failover from node1 to node2, it succeed. I want to konw if this downlevel failover impact database (data or usage)?
Many thanks.

I would not say this as a correct configuration although you can do it. Downside is suppose node 1 which is on higer version has some bug fixed with patch when you failover to lower version that bug might re surface. I have never used nodes with different
version nor i recommend.
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 Articles

SQL 2012 failover cluster\mirroring VS AlwaysOn for VDI?

Hi, we have to build high availability SQL 2012 cluster for VDI and we have two options. One option is to build a server cluster with combination of failover and mirroring and other option is to build failover cluster with AlwaysOn.
We are not sure which option to chose. We have contacted Microsoft support to provide us some documents and instructions for failover\mirroring combination but they have send us instructions for AlwaysOn option.
What would be best way to build high availability cluster for VDI? Also, since first option is very complicated, we would appreciated if someone could provide us with some documentation for it (how to build it, what to look out for, etc.) because that is the probably the option we are going to use.
Thank you in advance.
This topic first appeared in the Spiceworks Community

I was recently quoted in eCampus News regarding the recent cyber attack against Penn State, which triggered a number of conversations with CISO’s at various academic institutions. One of these conversations was with Helen Patton, theChief Information Security Officer for Ohio State University. I had a very interesting dialogue with her via email, and asked […]…Read MoreThe post In the Trenches: Helen Patton, Ohio State University CISO appeared first on The State of Security.
Read More

MSMQ and SQL 2012

Trying to get MSMQ working in a SQL 2012 Cluster. We have two nodes, OS server 2012 R2, and an instance of SQL 2012 on each node. I can send test messages to private and public queues. However when trying to send message through a stored procedure call the
message doesn't arrive to the receiving server. I keep getting a message queue service is not available. Any insight or documentation would be greatly appreciated.
Thanks

Hi,
How's everything going? If there is any progress from your side, feel free to share it in the forum.
Thanks.
Tracy Cai
TechNet Community Support

SQL 2012 Cluster Multi Instances !

Similar Messages

Maybe you are looking for