I'm starting out on the road to be a DBA. I've completed a SQL Server course at my local community college, and I started diving into a good book, <a href="http://www.red-gate.com/community/books/fundamentals-sql-server-2012-replication" rel="nofollow">Fundamentals of SQL Server 2012 Replication</a>.
I'm at a chapter where the author says that I need to use SQL Server on three separate "machines," not <em>instances</em>, which can be connected to each other on a network, ideally with a domain controller/Active Directory. (I need to be able to connect to server A from server B, etc.)<blockquote>
To make sure you get the most out of this and the following chapters, using three machines is indispensable. Because most enterprise networks are set up with a Windows domain, we'll assume that the three machines are part of a Windows domain. While it's possible to set up replication outside of a domain, it is not recommended. This book will therefore not go into any details on how that works. However, if you're forced to work outside of a domain, you must ensure that each user account used for replication exists on every machine and is configured with the same password, instead of existing just on the domain controller. (Page 79)</blockquote>
I have an Azure account, and I've been able to create three virtual machines without much effort. However, I'm not very knowledgeable about networks, so I'm running up against a wall on how I can get these machines to talk to each other. I assume that part of the problem is the particularities of Azure.
<strong>Is there a reasonably simple way that I can do this, at least for training/testing purposes?</strong>
FYI, this is what I have tried:<ul><li>Creating standard virtual machines on the default Azure network and connecting to them remotely. I'm unable to use SQL Server Management Studio (SSMS) on one machine to locate any other machine.</li> <li>Creating a virtual network and some virtual machines that reside on them. I'm still unable to locate the other machines.</li> <li>Attempting to connect after starting the SQL Server Browser service, enabling named pipes, and creating an MSSQL endpoint.</li> <li>Using the Windows Server Manager to "Add other servers to manage." The other servers are not visible. The Active Directory tab says "The local computer is either not domain-joined, or it cannot access a domain controller."</li> <li>Pinging one machine's virtual network IP address from one of the other machines. The host was not found.</li> <li>Creating an Active Directory "forest" on Azure using <a href="http://azure.microsoft.com/en-us/documentation/articles/active-directory-new-forest-virtual-machine/" rel="nofollow">online documentation</a>. I stopped since I saw a lot of comments saying there were problems, and since I didn't really know what I was doing. </li> </ul>Answer1:
I'd recommend looking at the <a href="http://msdn.microsoft.com/en-us/library/dn249504.aspx" rel="nofollow">tutorial for creating a SQL Server Always-On availability group</a>. It covers creating the VMs, joining them to a domain and registering them with a DNS all via a virtual network. Even if you're not actually creating the availability group, the tutorial will cover most of the topics you'd need to know with regards to sharing security and DNS resolution. :)