- An application server in Azure can’t connect to an IaaS SQL Server on Windows (also in Azure).
- The Connection Troubleshoot utility in the Azure Portal says network connectivity between the App server and SQL server on port 1433 is allowed:
- PowerShell Test-NetConnection on the App server shows that communication with the SQL Server is blocked on port 1433
Windows Firewall on the SQL Server is blocking communications from the App Server
Add a rule to the Windows Firewall on the SQL Server to allow SQL Traffic. See Microsoft Docs for details on how to do this.
DBI-B220 – Introduction to SQL Server Management for the Non-DBA
A very interesting and entertaining session to round off Tuesday. This covered the things IT Pros need to do when they need to run SQL Server- backups, restores, checking for corruption, and more.
Here are my 5 key points from the session. This was definitely one of those sessions which I could have listed many more from!
- Keep the number of TempDB files down. 8 is a good number, and set growth to 1GB increments
- Corruption Will Happen. Check for it. Deal with it.
- Backup regularly. Try a daily full backup and transactional backups every 10-15 minutes for starters.
- Good Indexing can speed up your queries. Too much slows down your iNSERT/UPDATE/DELETE tasks
- Keep your statistics up to date
DBI-B220 Talk at Tech-Ed Europe 2014.
Some work I’ve been involved with (see here and here) with UNIX Timestamps threw up another challenge today- getting the timestamp for midnight on January 1st of the current year. This is what I came up with: Continue reading