this eror message :
16/05/2022, 13:40:01node: MSSQLmsg : Object
message: "Failed to lookup instance on (localdb) - getaddrinfo ENOTFOUND (localdb)"
details: "Failed to lookup instance on (localdb) - getaddrinfo ENOTFOUND (localdb)"
Which MSSQL node are you using (full name please)?
What authentication are you using?
I am using the SQL server authorized.
Steve was asking for the full name of the node. Something like node-red-contrib-?????
SELECT TOP (10) [ID]
I see from the screenshot the OP is using
Are you definitely using sql server authentication ( NOT windows authentication )?
- Please verify this by using another application to log in using SQL Server Authentication to verify your user name and password can actually log in
Can you show us a screen shot of the MSSQL config settings?
Is the SQL Server an instance? If yes...
- what is the name of the instance?
- did you enter the instance name in the MSSQL config settings?
- Can you look in the SQL Server log and show be the instance port number assigned? (how to get port number of instance)
Where is the SQL Server installed - on same machine as node-red?
What version of SQL Server are you using?
I have verified this by using C# to save data in MSSQL.
I installed it on the same machine as node-red.
if I would like to connect it by windows authorization is ok?
so no need to put the password is it right?
I've not tested that so cant answer - however SQL Server auth definately works.
PS: I cannot help you if you dont answer all questions
SQL Server Management Studio 15.0.18410.0
SSMS is of no interest
Can you just answer the questions I asked please otherwise I cannot help you.
Then it wont work - thats why I asked ...
... but you have still not showed me!
Like in the link I provided ...
The "how to get port number of instance" link i posted 3 hours ago
Yeah - that tells me absolutely nothing.
I need to see the MSSQL Config Node settings e.g...
I need to know the Instance Name e.g.
I need to know the port number for the SQL instance e.g. 7801 or 1440 or ???? as described in the SQL Server Log