Hi...
Follow these steps:
Provision SQL Server virtual machine in Azure
Unblock the firewall
Enable ODBC callbacks for remote clients
Add network protocols
**
- Provision SQL Server virtual machine in Azure
**
On the Basics tab, provide the following information:
Under Project Details, make sure the correct subscription is selected.
In the Resource group section, either select an existing resource group from the list or choose Create new to create a new resource group. A resource group is a collection of related resources in Azure (virtual machines, storage accounts, virtual networks, etc.).
Under Instance details:
Enter a unique Virtual machine name.Choose a location for your Region.For the purpose of this guide, leave Availability options set to No infrastructure redundancy required. To find out more information about availability options, see Availability.In the Image list, select Free SQL Server License: SQL Server 2019 Developer on Windows Server 2019 if it's not already selected.
Choose Standard for Security type.Select See all sizes for the Size of the virtual machine and search for the E4ds_v5 offering. This is one of the minimum recommended VM sizes for SQL Server on Azure VMs. If this is for testing purposes, be sure to clean up your resources once you're done with them to prevent any unexpected charges
Under Administrator account, provide a username and password. The password must be at least 12 characters long and meet the defined complexity requirements.
Under Inbound port rules, choose Allow selected ports and then select RDP (3389) from the drop-down.
2. Unblock the firewall
To enable access from remote data science clients:
On the virtual machine, open Windows Firewall with Advanced Security.
Select Outbound Rules
Disable the following rule:
Block network access for R local user accounts in SQL Server instance MSSQLSERVER
*3. Enable ODBC callbacks for remote clients**
Make sure you login sql server by sqlrusergroup as a data base user
4. Add network protocol
Enable Named Pipes
R Services (In-Database) uses the Named Pipes protocol for connections between the client and server computers, and for some internal connections. If Named Pipes is not enabled, you must install and enable it on both the Azure virtual machine, and on any data science clients that connect to the server.
Enable TCP/IP
TCP/IP is required for loopback connections. If you get the error "DBNETLIB; SQL Server does not exist or access denied", enable TCP/IP on the virtual machine that supports the instance.
By following these steps, hope this will help you.
Good luck and stay safe.