SQL Safe Backup: How to Troubleshoot SQL Server Connectivity Issues

http://bit.do/dfuhs Secret discount page at HandyBackup.
How to troubleshoot SQL Server issues with connectivity. SQL Safe Backup provides hands-free backup across your SQL Servers. With it, you'll save time and space, reduce failures, and recover quickly. Automate full, differential and transaction log backups and scale to the growth of your business with this best-in-class solution. Troubleshooting connectivity issues when using SQL Safe Backup. ——— Transcript: Welcome to Idera Virtual Education. My name is David Terry, and today we're going to be discussing different ways that you can solve authentication problems within SQLsafe. If you notice in my screen, we have an authentication failure on the SQLPROD01, and there's a couple reasons why that might happen. It may be that the ports that are used to communicate with SQL Server are blocked, it could be that I have a poorly configured username or password, or I it set to use Windows Authentication in going across domain, or it could be something related to cloud services that you're using, depending on where your SQL Server Instances are. So let's take a look at some ways that you can troubleshoot these issues. The first thing that I might want to do is test whether or not 1433 or whatever port you're using for SQL Server is available on that particular instance. So, I might go and use Telnet to do that. So if I go look at Telnet, we can telnet out that server and test the port. So, telnet "telnet sqlprod01" and 1433 default SQL Server port's what I'm using. So, when I put in telnet space server name space port number, hit "Enter", comes back as a connected Telnet service, meaning that we have connectivity. So, obviously we don't have a Firewall issue necessarily in this case. So the next thing that I might want to look at is look at the properties of how that server is configured. In my case, I'm using Windows Authentication to communicate with that SQL Server instance. The problem with that is this server is in a different domain. So I'm going to need to use SQL Server Authentication to communicate. So I can change that to SQL, and then Idera will be my account, and then we can hit "Ok" and hopefully that solves my problem. And in this case, it does. So, what we now see is we have complete visibility into that SQL Server Instance and we can do backups and restores as usual. So that's one way that you might need to go in there and address an authentication issue. The third way that we typically see is really related to people who are hosting SQL Servers in the cloud. Amazon's a good example. In some cases, even though you have the ports available and you have the correct authentication available, we still can't communicate. So basically, what you would want to do is go under "User Experience", and there's a little check mark here that you can enable that says "Do not use ICMP Ping when contacting hosts". So by disabling ICMP Ping, that typically will resolve any cloud-based issues that you might have in communicating with instances. So those are really the three ways that I would troubleshoot connecting to a SQL Server Instance. I hope that information is very useful for you guys, and please come back for more videos from Idera's SQL Virtual Education. Thank you for your time.