topic Re: Disable Connection w/out Deletion in Management & Governance

Disable Connection w/out Deletion

justindallasverizon — Tue, 22 Jul 2025 21:04:09 GMT

Hello Folks,

I would like to disable some database connections without deleting them. I would also like to prevent sa_repository from invoking them too so users can't reload them through the QMC Tasks UI.

I know I can make my custom rule have a clause like "And 1=0", but I don't think that would stop sa_repository from getting a hold of it.

Any help is greatly appreciated.

Re: Disable Connection w/out Deletion

Or — Tue, 22 Jul 2025 21:06:52 GMT

If you'd like to prevent them from being used to read data entirely, you could just fudge up the connection details, e.g. by adding a 'z' to the start of the connection string. Any attempt to use this connection to pull data will fail.

Re: Disable Connection w/out Deletion

justindallasverizon — Tue, 22 Jul 2025 21:07:53 GMT

That was my first thought, but they are ODBC connections, so they live on the server and not in the QMC =(

Re: Disable Connection w/out Deletion

Levi_Turner — Thu, 24 Jul 2025 12:52:16 GMT

You're right that sa_repository will be able to access the data connection (via rule named ServiceAccount).

I am a fan of @Or 's suggestion to rename the _name_ of the data connection. Even for ODBC (or OLEDB) based connections, the invocation in the load script is via the name of the data connection:

Renaming is a great "sc ream test" to see who uses it. Alternatively, you can audit what apps use the data connection (https://github.com/eapowertools-archive/qs-data-connection-analyzer, warning it may take a while to reload, so you may need to adjust the reload task for >1day).

From an access control standpoint, you could filter out user access via auditing what rules would grant access then adjusting them but to your point, for an existing app which has a reload task, the service user would still be able to access the data connection.