How to set up development target for MS Sql Server

[Speedy]

After a lot of experimentation I can connect to a local MS SQL Server but only through the “DATABASE CONNECTION” property panel, not the original set up panel which is used to initiate the setting up of the connection. See screenshots below

This never worked:

This worked:

I don’t understand what Wappler is doing here – it seems contradictory, a time waster until I made it work using the second panel.

Also, there were some settings I had to make in SQL Server but that’s another story…
Bottom line is Wappler cannot use Windows Authentication so you must set up a special user account for it.

If anyone needs details on how to connect to a SQL Server, DM me and I’ll write it up for you.
Thanks for your help.

[George]

Maybe this can help:

Error connecting to MS SQL Server

As we switched to newer MS SQL driver in Wappler called Tedious, seems named SQL Server addresses are no longer supported. You can convert them to normal addresses as suggested at:

[Robert_LM]

Howdy

you def. should create another user in SSMS just for access from Wappler, with some limited/specific/non-superuser rights. wappler is no diff. than any other no-code service which would access an API on your server. You’d create a specific user to access that API to gain access.

you should never rely on the “sa” user - in fact, disable it - every hacker is going to try that username

you should never use the default 1433 address, for the same reason. at least obfuscate it by changing that MSSQL port to something else, and open that in windows firewall

IF, you’d already had these steps done, you might have had an easier path, because you’d have had experience with other tools hitting the db. Granted, its odd that MSSQL isn’t in that list you’ve shown - I’ve seen that myself.

Having said that, it is possible, after an install of Wappler, to successfully make a query to a brand new connection AND see data in under 5 mins… its just “first time blues” for you - sorry about that. But it gets easier from here.

Feel free to PM me or Skype for direct help.

[Speedy]

Thanks. My local SS setup mirrors what is suggested in the linked article but still the Database Connector fails.
Can you explain what the difference is between “Connection Properties” and the “Database Connection” (Direct Database Connection) are? I’m not clear why there are two database connection property panels and am unsure what this app will actually do in production–which will it use?

[Speedy]

Thanks. My production SQL Server is hosted so I cannot remove the sa user or change the default port.
Yes, setting up a login/user on SS is necessary and I’m still playing with the Login server roles & user mapping to determine what the minimum amount of permissions and access will be necessary to enable Wappler to run CRUD queries directly and still work in our production environment. From a security standpoint, having an application manage a direct connection to the db is extremely concerning.
Until I get a reliable db connection in Wappler I can’t even start on what the security implications will be though. I’ve always relied on using .NET & Linq to access the db and security concerns are almost zero. Data is never accessed directly from my applications. Wappler presents a new paradigm for me.