MSSQL connection to Ms SQL Server Management Studio instructions
Hi!
I can't seem to connect to the mssql database using the tool from microsoft. I took the public proxy port and address from the variables + used the sa user + the sa password and left the certificate optional. Can you help me login to the server?
22 Replies
Project ID:
f3f3aa54-1f32-4a2a-9e9a-61d26191712df3f3aa54-1f32-4a2a-9e9a-61d26191712d
what error are you getting?
Connection string error
do you give me permission to attempt the connection myself?
Go for it, the database is empty since I never accessed it
I hope it's a typo on my end or something
i can connect just fine with dbgate
Hmm
Interesting, never used the tool before, only used mssql sms for mssql
you don't need to use it, it just means that there's no issues with the database or connection
I've tried using azure data studio as well with no success
hmm
it's something
there's nothng special about the image, is there?
it's just a barebones mssql image
correct
this isn't anything on the railway side of things
It seems like the template has a 30% success rate, am i reading it right?
let me give you a ss so you on't have to dig for what i'm talking about
yes because trial users attempt to deploy it not knowing that you need hobby to run it
ooooh, okay
so it's not something like "template needs perfecting" it might in fact be readable as "templates not used right"?
it could be either, but in this case it is the latter
Hey Brody
here: some extra nugget of information you can come back to
It's the fact that SSMS (the official tool) is unable to parse ports at GUI data entry for servers. So you can't do server:port, you have to go to the tab Additional Connection Parameters and write it like this:
Data Source=yourrlwypublicaddres.proxy.rlwy.net,YourPortNumberNoQuotes;
Anything written there overrides the info you write in the default server connection tab
However, one must select mandatory encryption and most likely also check the field "trust server certificate" in the first tab
so you got it to connect?
Yeah, with a bit more fiddling than expected on microsoft's side
Turns out this is a universal piece of info you can pass to other sufferers of Microsoft unique software design
it's always the formula: server,port if you have a non-default port for their services