Entradas

Mostrando entradas de julio, 2014

Cluster adding node with Service Accounts Name empty

Imagen
Right. SQL agent needs to be added as a correct resource type. delete this generic resource (after changing the dependencies) Next - 1 - Add the SQL agent 'resource type'. cluster restype "SQL Server Agent" /create /DLL:sqagtres.dll 2- Add the SQL agent resource .. .         In the Failover Cluster Management use Add Resource to add the SQL Server Agent resource. Name the resource as “ SQL Server Agent ”, as this is case sensitive unless you are on CU3 or above for SQL Server 2008 RTM. a.         Right-click on the SQL Agent resource and go to Properties and fill in values for the two parameters. b.        Specify the Virtual Server name of the SQL instance.   c.         Specify the Instance name . d.        Add the SQL Server Resource as a dependency for the newly created SQL Server Agent resource 3 .         Open Registry Editor and browse to the following location. Default Instance HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MS

SQL Server 2012 Failover Cluster Installation – Step by Step Guide – Part 1

Imagen
Thanks to: http://theadminsguide.net/ Recently i have been preparing some articles that involve step by step guides for installing some applications that require a SQL Server for their databases, that’s when i thought why not also write one about installing a highly available SQL installation which i will eventually use for my lab. So today i am going to walk you through installing a SQL Server 2012 Failover Cluster on top of a Windows Server 2012 R2 Operating System. Software Requirements According to   Microsoft’s KB Article , to install SQL Server 2012 on top of Windows Server 2012 R2 you need to have SP1 for SQL Server 2012 installed. so in this article i am going to use a SQL Server 2012 With SP1 installation media. After you install SQL Server 2012 SP1, you may experience an issue in which Windows Installer starts repeatedly. This issue is described in the following article in the Microsoft Knowledge Base. Please note that it is mandatory that you install this hotfix afte