Forum Discussion
SQL Server Management Studio
1) The tool doesn't matter, bothe send plain T-SQL commands to SQL Server engine, in this case "CREATE DATABASE".
2) SSMS = "SQL Server Management Studio" is to manage SQL Server, you can not create reports with. For this you have to use Visual Studio with SSDT (SQL Server Data Tools) / SSRS (Reporting Services) extension.
3) For simple purpose you don't need a paid certificate to encrypt (SSL) connection/communication.
Even if you want to you can use on first hand a "self-sign" certificate.
1) The tool doesn't matter, bothe send plain T-SQL commands to SQL Server engine, in this case "CREATE DATABASE".
2) SSMS = "SQL Server Management Studio" is to manage SQL Server, you can not create reports with. For this you have to use Visual Studio with SSDT (SQL Server Data Tools) / SSRS (Reporting Services) extension.
3) For simple purpose you don't need a paid certificate to encrypt (SSL) connection/communication.
Even if you want to you can use on first hand a "self-sign" certificate.
olafhelper Thank you. I thought (hoped) that. It is just that I have had no luck in VS2022 getting a thorough connection. If its not the port, its the certificate, or something else. I will persist. Thank you again Olaf, appreciated.
- Do you get an error message regarding SSL/encryption?
Then add the parameter "Encrypt=false" to the connection string to surpress it.- Yes, this is likely it.
The latest SQL Clients default to "Encrypt=True;TrustServerCertificate=False", which will trip up a lot of first time users.
Defining either "TrustServerCertificate=True" or "Encrypt=False" in the connection string should allow the connection.
