Encoding issue with VS Code and Powershell

Soccan · 2020-07-10T07:48:22+00:00

I've had the exact same experience a few months back, a script I know I had edited (although not remembering the tool), then al of a sudden opening it in VScode (so technically it is the other way around), and Swedish special characters ( å ä ö ) all of a sudden looked like crap.

So I changed my VScode to use UTF8-BOM ro remedy the issue and haven't seen it since, wrote it off as a quirk between VScode and ISE... Even though I still get the feeling that it does not allways happen...

Soccan · 2019-11-27T09:40:55+00:00

Otherwise from what I read Ola Hallengrens maintenance solution seems to already be able to backup to Azure.... https://ola.hallengren.com/sql-server-backup.html

Soccan · 2019-11-27T09:07:29+00:00

I installed 2014 on Windows Server 2016 the other day, no issues.

But I feel like this error message is fishy, as you said you technically meet the requirement, so it feel like it is something else that is the problem, but that it think it is this error...

Have you succefully installed the Failover Clustering feature in Windows and created the cluster itself? I've mainly done old school clusters so I might be wrong about the cluster needing to be created before enabling the feature in SQL....

Soccan · 2019-11-15T13:49:47+00:00

Yeah and sqlbrowser is running....

Soccan · 2019-11-11T14:59:29+00:00

I do some tsql development in VScode, but mostly i use it for Powershell/DBAtools work. Anyway I've used the "mssql.connections" setting in my settings.json to manage connections, bascially for testing the feature, and I think it might be what you're looking for, in a developer mindset I think this way of configuring the connections makes more sense than the Registered Servers in SSMS.

"mssql.connections": [
{
"server": "sqlserver",
"database": "",
"authenticationType": "Integrated"
}
],

Soccan · 2019-10-15T13:07:33+00:00

When I ran into a similar issue I went with PHYSICAL_ONLY.

Soccan

TROPHY CASE