Disable Remote Resigtry service for SQL Server failover cluster

Hi,
Is it safe to disable Remote Registry service from the the two nodes of SQL Server failover clustering?
Operating system: Microsoft Server 2008 R2 Enterprise Edition (64-bit)
Database software: Microsoft SQL Server 2008 R2 Enterprise Edition (64-bit), Failover Clustering
Thank you.
Regards,
Gan

Hi Pradeep,
You are right. I tested and verified that the GUI of cluster (Failover Cluster Manager) was not working properly after disabling Remote Registry service. Thank you :)
Regards,
Gan

Similar Messages

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

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

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

Unable to install Integration Services for SQL Server 2005

I'm not able to select "Integration Services Project" in Business Intelligence Development Studio (it is not in the templates below):
When installing, it says that it is already installed. Why can't I see it in the project templates?

Microsoft Visual Studio 2005
Version 8.0.50727.867 (vsvista.050727-8600)
Microsoft .NET Framework
Version 2.0.50727 SP2
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41773
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 77626-009-0000007-41773
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 77626-009-0000007-41773
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 77626-009-0000007-41773
Microsoft Visual J# 2005
Microsoft Visual Studio 2005 Tools for Applications 77626-009-0000007-41773
Microsoft Visual Studio 2005 Tools for Applications
Microsoft Visual Web Developer 2005 77626-009-0000007-41773
Microsoft Visual Web Developer 2005
Microsoft Web Application Projects 2005 77626-009-0000007-41773
Microsoft Web Application Projects 2005
Version 8.0.50727.867
AnkhSVN - Subversion Support for Visual Studio 2.5.12440.9
AnkhSVN - Subversion Support for Visual Studio 2.5.12440.9
* Ankh.Package 2.5.12440.9
* Subversion 1.8.8 via SharpSvn 1.8008.3178.19
SharpSvn is linked to: Apr 1.5.0, Apr-util 1.5.3, Cyrus Sasl 2.1.25, eXpat 2.0.1, OpenSSL 1.0.1g 7 Apr 2014, serf 1.3.4, SQLite 3.7.17, Subversion 1.8.8-SharpSvn-1.8.8, ZLib 1.2.8
SharpSvn is optionally linked to: Berkeley DB 4.4.20, SharpPlink 1.8008.3178.19
Hotfix for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2938803)
Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1 (KB926601)
Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2251481)
Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2538218)
Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2548826)
Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB971090)
Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB973673)
SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00
Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB932232)

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.

SQL SERVER Failover Cluster switch failure because the passive node automatically reassign drive letter

I switch the sql server resource group to the standby node , when the disk resource ready bring online in the passive node ,then occur exception. because the original dependency disk resource the drive letter is 'K:' , BUT when the disk bring online , it
automatically reassign new drive letter 'H:' , So the sql server resource couldnot bring online . And After Manual modify the drive letter to 'K:' in the passive node , It Works ! So my question is why it not use the original drive letter
and reassign a new one . what reasons would be cause it ? mount point ? Some log as follows:
00001cbc.000004e0::2015/03/12-14:41:11.377 WARN [RES] Physical Disk <FltLowestPrice_K>: OnlineThread: Failed to set volguid \??\Volume{e32c13d5-02e6-4924-a2d9-59a6fae1a1be}. Error: 183.
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk <FltLowestPrice_K>: Found 2 mount points for device \Device\Harddisk8\Partition2
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Update volume exit, status 1168
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Updating volume
\\?\STORAGE#Volume#{1a8ddb8e-fe43-11e2-b7c5-6c3be5a5cdca}#0000000008100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
00001cbc.00001cdc::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: PNP: Update volume exit, status 5023
00001cbc.000004e0::2015/03/12-14:41:11.377 ERR [RES] Physical Disk: Failed to get volname for drive H:\, status 2
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk <FltLowestPrice_K>: VolumeIsNtfs: Volume
\\?\GLOBALROOT\Device\Harddisk8\Partition2\ has FS type NTFS
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: Volume
\\?\GLOBALROOT\Device\Harddisk8\Partition2\ has FS type NTFS
00001cbc.000004e0::2015/03/12-14:41:11.377 INFO [RES] Physical Disk: MountPoint H:\ points to volume
\\?\Volume{e32c13d5-02e6-4924-a2d9-59a6fae1a1be}\

Sounds like you have an cluster hive that is out of date/bad, or some registry settings which are incorrect. You'll want to have this question transferred to the windows forum as that's really what you're asking about.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Hardware Requirement for SQL Server 2012 Cluster

Hi All,
We are going to share System Requirement document with the customer and one of the technical staff from Customer has request us to provide Microsoft Disk space requirement at least for below 2 section and why?
Quorum & MSDTC (Both will be SAN and what will be their RAID type)
Please share your advice.
Regards, Sachin

Hello,
The quorum disk needs only to have a few MB to hold the file used for arbitration. Normally if you're needing a disk vote, it can be extremely small (100MB or less is what most SANs can do, some can only do 1 GB or greater). The actual file size is a few
KBs.
MSDTC holds the DTC logs, so this will be sized to how much logging and usage of MSDTC is needed and used. If you're not using distributed transactions then it doesn't even need setup.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Group managed service accounts for SQL Server

Hey guys,
Unfortunately I missed that (g/s)MSAs aren't supported yet for SQL Servers but I'm using them without any worries since ages.
As i digged a bit deeper I could find different informations due to the related TechNet entrys. So it seems Microsofts Informations about (s)MSAs and gMSAs aren't consistent.
I'm not a SQL Server guy and use SQL only for System Center testing stuff so i would like to get a real world exps of SQL Server guys.
Should I continue using gMSAs or are there any worries I should know?
some sources I found so far:
Not supported:
"Hi Adam,
Thank you for your feedback. Windows Server 2012 Group Managed Service Account is not currently supported as SQL 2012 released earlier than Windows Server 2012. We will consider to support gMSA in future SQL Server release.
Regards,
Min He, Program Manager, SQL Server"
11.2012 -
https://connect.microsoft.com/SQLServer/feedback/details/767211/gmsa-for-sql-server-failover-Clusters
gMSA are not yet available, are not yet supported for SQL Server. gMSA exist and are available and supported in Windows Server 2012 and higher.  SQL does not support them , but
from an OS perspective, they exist and are supported.
http://blogs.msdn.com/b/sqlosteam/archive/2014/02/19/msa-accounts-used-with-sql.aspx
Within the FAQ Task Scheduler isn't supported as well ...
http://technet.microsoft.com/en-us/library/ff641729%28WS.10%29.aspx
... but also PFEs using them for Tasks... this is confusin... 0o
http://blogs.msdn.com/b/arvindsh/archive/2014/02/03/managed-service-accounts-msa-and-sql-2012-practical-tips.aspx
supported?:
Configure Windows Service Accounts and Permissions
... New Account Types Available with Windows 7 and Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Default_Accts
The MSA must be created in the Active Directory by the domain administrator before SQL Server setup can use it for SQL Server services.
others sources won't mentioning s/gMSAs...
I couldn't find clear informations about using gMSA for SQL Server 2014.
only the same page which also Looks like the page for 2008 R2 and SQL 2012.
Configure Windows Service Accounts and Permissions
            SQL Server 2014
http://msdn.microsoft.com/en-us/library/ms143504.aspx
annoying topic so far... ;)

Hi Enrico
aside from what Dan says about the risk for support, on which I agree, the following thread may clear it up a bit:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/acb2048c-ffce-4d44-b882-6aafc7eb689d/managed-service-accounts-to-run-sql-server-service?forum=sqlsecurity
Andreas Wolter (Blog |
Twitter)
MCM - Microsoft Certified Master SQL Server 2008
MCSM - Microsoft Certified Solutions Master Data Platform, SQL Server 2012
www.andreas-wolter.com |
www.SarpedonQualityLab.com

High availability SQL Server requirements for Remote Desktop Services in Windows Server 2012

Good night,
Thanks for reading this question, I do not write much English.
I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf, I searched in different microsoft link but I have not received a response.
Kindly appreciate your cooperation and attention.

Hi Alejandro,
I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf
If you want to know the size requirements of .mdf abd .ldf files, since they are parts of SQL database, I suggest you refer to SQL forums below to get more professional support:
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlgetstarted
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home
In addition, here are some articles regarding RDS deployment for you:
Remote Desktop Services Deployment Guide
https://technet.microsoft.com/en-us/library/ff710446(v=ws.10).aspx
Remote Desktop Services (RDS) Quick Start Deployment for RemoteApp, Windows Server 2012 Style
http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Hyper-v Failover clustering for SQL Server lab

Hi,
After 20yrs years of IT software experience, now I am realizing that I don't know much about hyperV clustering. :) I am trying to setup a lab. I badly need help on configuring network adapters
to make the machines accessible from each other. Please see details below:
I have a laptop with 8gb ram with windows 8.1 hyper-V. I created 4 VMs with Windows 2008r2 on it and further I intend having SQL Server Failover Clustering. VM details are as below:
DC - Domain Controller
SanStorage - MS iSCSI target
Win1 - Primary node in the cluster that will have SQL Server instance
Win2 - Secondary node in the cluster that will have SQL Server instance.
The laptop has 1 Qualcomm network adapter (generally used for connecting Lan cable) and a Broadcomm (wifi) adapter. I intend setting up three virtual adapters
First for regular communication
Second for Data (SQL Server Data to be stored on SCSI)
Third for HeartBit
Normally, (on my laptop) I connect to internet using Broadcomm (Wi-Fi) and want to ensure that whenever needed:
Run this lab even when Lan or wifi is NOT connected. If one of them is mandatory then even that could be the option.
I should be able to use internet within all VMs as well- though this is good to have requirement.
Internet needs to be available on laptop at least. Even if it is unavailable in VMs that is ok.
Now the actual problem.
I DON'T KNOW how many virtual internal/external/private switches to be
defined and assigned to individual VMs. What should be the IPs, Subnets, DNS, Gateways defined on those?
I was able to setup the stuff up-to certain extend and then it stopped working for unknown reasons. I have VMs ready. Next what should I do? Steps...
setup network adapters in each VM
setup DNS on DC
Add remaining 3 VMs in domain
Define Win1 and Win2 as cluster
Configure Target
Configure initiators and access the target
e. Install SQL Server
Is above correct?
My queries probably demands a separate article. But I have already referred many articles and couldn't figure it out so posting it here. I sincerely request your help!
PS – Even after disabling firewall (with and without having DNS setup) I am unable to ping VMs from each other.
Regards,
ThingToLearn
Thanks, Pravin

Hi,
You need create another guest vm as the NAT device, attach the NAT external to the Wifi adapter or cable adapter, then you can set all your vms in internal network
vswitch.
The related third party article:
Using Wireless with Hyper-V
http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx
Hope this helps.
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
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.

[Forum FAQ] How do I disable all subscriptions without disabling Reporting Services and SQL Server Agent?

Introduction
There is the scenario that users configured hundreds of subscriptions for reports. Now they want to disable all the subscriptions, but Reporting Services and SQL Server Agent service should be enable, so the subscriptions will not delivery reports to users
and users could run the reports and create jobs on the server.
Solution
To achieve this requirement, we need to list all subscriptions and their schedules by running query, then use loop statement to disable all the subscription schedules by Job name.
On the Start menu, point to All Programs, point to Microsoft SQL Server instance, and then click SQL Server Management Studio.
Type Server name and select Authentication, click Connect.
Click New Query in menu to open a new Query Editor window.
List all subscriptions and their schedules by running the following query:
Use ReportServer
go
SELECT   c.[Name] ReportName,
s.ScheduleID JobName,
ss.[Description] SubscriptionDescription,
ss.DeliveryExtension SubscriptionType,
c.[Path] ReportFolderPath,
row_number() over(order by s.ScheduleID) as rn
into
#Temp
FROM
ReportSchedule rs
INNER JOIN Schedule s ON rs.ScheduleID = s.ScheduleID
INNER JOIN Subscriptions ss ON rs.SubscriptionID = ss.SubscriptionID
INNER JOIN [Catalog] c ON rs.ReportID = c.ItemID AND ss.Report_OID = c.ItemID
select * from #temp
Use the loop statement to disable all the subscription schedules by Job name:
DECLARE
@count INT,
@maxCount INT
SET @COUNT=1
SELECT @maxCount=MAX(RN)
FROM
#temp
DECLARE
@job_name VARCHAR(MAX)
WHILE @COUNT <=@maxCount
BEGIN
SELECT @job_name=jobname FROM #temp WHERE RN=@COUNT
exec msdb..sp_update_job @job_name = @job_name,@enabled = 0
SET @COUNT=@COUNT+1   P
RINT @job_name
END
PRINT @COUNT
Reference
SQL Agent – Disable All Jobs
Applies to
Reporting Services 2008
Reporting Services 2008 R2
Reporting Services 2012
Reporting Services 2014
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Thanks,
Is this a supported scenario, or does it use unsupported features?
For example, can we call exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b64ce7ec-d598-45cd-bbc2-ea202e0c129d'
in a supported way?
Thanks! Josh

HADR Solution for SQL Server Analysis Services (SSAS) 2014 on Azure Iaas

Hi All
I am required to build a HA/DR solution for SQL Server and SSAS 2014 on Azure. So far I could build AlwaysOn high availability solution for SQL Server on Azure but haven't found any solution for SSAS.
Failover Clustering is not an option on azure because of the restriction of not been able to use shared storage. We also determined that the cost savings of using SQL + the cost of the 3rd Party replication tool was a wash (ie no real cost savings).
Any lead on this would be appreciated.
Thanks,
Viral Shah
Thanks - Viral

Hi Viral,
A clustered implementation of SSAS can be configured in Microsoft Azure. Such a configuration would need to meet all the requirements stated in the following document including Active Directory and storage.
How to Cluster SQL Server Analysis Services
http://download.microsoft.com/download/D/2/0/D20E1C5F-72EA-4505-9F26-FEF9550EFD44/SSAS_Failover_Cluster_V4.docx
Thanks,
Lydia Zhang

Cannot connect Remotely for SQL Server 2008

Hi,
I have SQL Server 2008 installed and configured as server locally. So when I try to connect using same machine with IP address it works but when I try to connect through any other computer through internet, it does not work and gives the following error.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
Named pipes provider, error: 40 could not open a connection to sql server) (Microsoft SQL Server,
Error: 53 )
please note that:
- I have amended Internet Protocol version 4 (TCP/IPv4) properties with my current IP address, subnet mask, default gateway and all Sky(ISP) preferred/alternate DNS Server names.
- SQL server configuration manager shows that TCP/IP is enabled and it is on 1433 port.
- SQL, SQL Browser exe and SQL server windows NT is ON for firewall's Port, Domain and public.
- Router is added with outbound services and Inbound services for SQL port 1433 and SQL browser 1434.
- SQL server instance is enabled for remote connections.
Kindly help, I am almost there and do not want to give up. Thanks in advance.
Adnan

Hello Adnan,
See TechNet
Connecting to SQL Server over the Internet for how to setup your enviroment to Access your SQL Server over public Internet
Olaf Helper
[ Blog] [ Xing] [ MVP]

Disable Remote Resigtry service for SQL Server failover cluster

Similar Messages

Maybe you are looking for