WindowsAzure released the PersistentVirtualMachine trial version in March, and now you can deploy SQLServer on the cloud. However, it is inconvenient to manage databases deployed in the cloud, because you have to remotely log on to the VM through RDS, and then open SQLServerManagementStudio for management. All of this
Windows Azure released a trial version of Persistent Virtual Machine in May June. Now you can deploy SQL Server in the cloud. However, it is inconvenient to manage databases deployed in the cloud, because you have to remotely log on to the VM through RDS and then open SQL Server Management Studio for Management. All of this
Windows Azure released a trial version of Persistent Virtual Machine in May June. Now you can deploy SQL Server in the cloud. However, it is inconvenient to deploy it on the cloud, because you have to remotely log on to the VM through RDS, and then open SQL Server Management Studio for Management. Because all this is done through the Internet, sometimes the performance is unsatisfactory. If there are multiple clouds, it will be more troublesome to manage them. You may want to directly register and manage databases in the cloud on the local SQL Server Manager. The following describes the practices.
1. Suppose we have applied for an SQL Server VM called "SQL-2 ". First, we need to set the Virtual Machine endpoint so that the virtual machine can be accessed over the Internet. Click "Endpoints" in the figure ". Then create a new Endpoint for VM SQL-2
2. the endpoint is named SQLConnection. Here, private port is 1433, which is a commonly used port Number of SQLServer. Public port is the external port of the VM. We recommend that you use a custom port number for security reasons, port 5433 is used below
3. After setting the endpoint, you must set a firewall for the SQLServer VM to allow access to port 1433 of SQLServer. Click Connect in VM SQL-2 to Connect to VM SQL-2
4. Choose Server Manager> Configuration> Windows Firewall with Advanced Security> Inbound Rules to create a new rule.