I wasn't sure if the Browser service was required for the default instance on port 1433 or not, but I generally start the browser service as soon as I install...

As I said multiple times - Firewall.  Just because port A is open in the firewall and you can connect to SQL instance B doesn't mean that port C is...

First, I think you would likely get better support on a MySQL forum than a SQL Server forum.

Second, my understanding of MySQL is that it keeps the temporary tables in...

I think there are multiple approaches to this, but if it was me, I would start by trying to define the problem you are trying to solve rather than starting...

Jeff - My GUESS is that it was an implicit conversion due to the division by int.  I expect that Length is a CHAR or VARCHAR datatype, but holds FLOAT...

To me it sounds like you have an Azure SQL instance, not an Azure SQL Managed Instance.

Did a quick google and found this document from Microsoft:

https://docs.microsoft.com/en-us/azure/azure-sql/database/features-comparison

If you scroll down a...

• This reply was modified 3 years, 11 months ago by Mr. Brian Gale.

The reason it is not implicit is that there is no hard rule saying the default instance must run on port 1433, and most people change it off of the...

I second the "nonwork_days" table, but I would make sure to design the reason code table well.

You would want to make sure that the reason code table has a reason...

Could you post the DDL for the tables?  Mostly, I am wondering what the datatype on "Length" is.  If it is not a numeric data type (numeric, decimal, float, int,...

• This reply was modified 3 years, 11 months ago by Mr. Brian Gale. Reason: adding potential fix

I am not 100% certain on the Access syntax for this, but I see a few potential solutions.

My recommended solution would be to do this as a stored procedure rather...

There are other solutions for sure, but they include risk.  For example, you can take the database offline and modify it in a hex editor to correct the bad data.

If...

A lot of my advice still applies.  I would try connecting by the FQDN name of the server as well as the port.

You ruled out DNS because you can RDP,...

Can your client machine see the servers?  Could be firewall issues (that would be one of my first guesses) or network related.  I would try connecting by the full name...

To add to what Johan said, I'd also check to make sure your database owner is a valid, enabled user.  I've had service broker fail to send messages because my...

Did a quick google and came up with this link:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9a68b2f5-a033-44a5-ab1b-ec76967ebfd4/protocol-error-in-tds-stream

Which suggests turning up the remote execution timeout period at the SQL server side OR hardware/network issues.  Since the query runs...