I'm attempting to connect to an SQL Server listener serving an SQL Server multi-subnet cluster. HeidiSQL seems to be unaware of the OR-ed nature of the IP addresses associated with the listener via DNS. Sometimes HeidiSQL connects and other times I see SQL Error(0): Unable to complete login process due to delay in opening server connection. It's possible to work around the problem by doing an nslookup on the listener host name. One IP address will work while using the other will result in SQL Error (0): TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond Login timeout expired. Of course, I would like to see HeidiSQL connect reliably to the listener. Am I missing something or is HeidiSQL unable to handle this? Thanks.
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.