topic Re: Enable Windows Athuntication for sql server data source in Qlik Compose

Enable Windows Athuntication for sql server data source

abTech — Fri, 14 Mar 2025 20:49:07 GMT

I'm installing Qlik compose locally on my PC, wanted to connect to SQL server database which is already configured for WA, i cant find the attunity compose service on windows services, any help..

Re: Enable Windows Athuntication for sql server data source

Dana_Baldwin — Mon, 10 Jun 2024 17:23:12 GMT

Hi @abTech

In more recent versions, the service name was changed from "Attunity Compose" to "Qlik Compose", please look for it with this name.

Thanks,

Dana

Re: Enable Windows Athuntication for sql server data source

sureshkumar — Tue, 11 Jun 2024 02:26:48 GMT

Hello @abTech

As Dana mentioned, please refer the below screenshot for reference

Regards,
Suresh

Re: Enable Windows Athuntication for sql server data source

abTech — Tue, 11 Jun 2024 08:39:53 GMT

Thank you for your great support, i check the compose service and its running probaly, but still cannt connect to the SQL server database.

i have enabled SQL Server login from the SQL server and asign a user name and password, but still the same issue.

Re: Enable Windows Athuntication for sql server data source

sureshkumar — Tue, 11 Jun 2024 09:40:18 GMT

Hello @abTech

This is a connection issue which is caused at the source DB.

I would suggest verifying the Server name given or try with IP address.

Pease verify remote connection is enabled on the server.

Try restarting the Qlik Compose Server and Qlik Service and check.

And also ping/telnet SQL Server ip address in Compose Server

Regards,

Suresh

Re: Enable Windows Athuntication for sql server data source

Dana_Baldwin — Tue, 11 Jun 2024 18:27:06 GMT

Hi @abTech

Related to one of Suresh's comments, you can check & set remote connections in the SQL Server database here: View or Configure Remote Server Connection Options (SQL Server) - SQL Server | Microsoft Learn

Thanks,

Dana

Re: Enable Windows Athuntication for sql server data source

cekar — Sun, 16 Jun 2024 12:21:48 GMT

I like to see installers ask for service accounts as they are most likely going to be different than the installer credentials. You don't want your service to run with DBO or under a person's account (both are against best practice), but the installer may need elevated permissions for table manipulation, etc.
If the instance is on the same server as the service, you can use a local machine account to run the service under, and grant that account permissions within the database just like any other user. Maybe you can change the service account after installation?
As for security, typically, I like a database role with all the permissions needed, and then add whatever user the app is going to run as to that database role - it has the added benefit of allowing you to test those permissions separately from the application.
If I didn't hit on what you're trying to solve, let me know, and I'll see if I can narrow my answer up a bit (Edited to fix wrong advice)