SQL Server password change - sql-server-2008

I need to change the SQL Server authentication to a different profile.
I need to create a different user with different permissions. But I have used the old username and password in many SSRS reports. How can I change the same with minimal effort?

Related

how to create MYSQL User for tableau connectivity only

I want to allow MYSQL connectivity to business users on tableau without creating a DB user i.e. without allowing direct access to the database through the MYSQL workbench.
right now I have a MySQL user with grant access on only one database to connect through tableau. But business users can use this user to explore data through workbench and run queries, which is not ideal.
Is there a way to give MYSQL database access ONLY on tableau and not any database tools like workbench?
There is not such an option for it. But you can create/define user roles with restrictions on DB/table levels in MySQL or you can create two database(on same machine or another machine), one is Main(Primary) and other one for Tableau only, so if any Tableau users access the new(separate) database from any other application, they will have limited data(only which is using for Tableau dashboards).
So I found a solution for this and here it is, in case someone else has this issue.
I just published a live connection to my database table on tableau server, and embedded user credentials in tableu. This way anytime a user wants to use the data source they just need to select from published data sources. But we wont have to share user credentials with them, that resolves the issue and they wont be able to log in using any credentials from any database client.

Allow any password for a specific mysql user

I have an old application from a friend that is dependent on a table in a MySQL database. The application makes calls directly to the database - Sends login request and subsequent retrieval activities.
The password is hard-coded into the application and he forgot what it is. However, we do have the table structure and is able to allow the database connection to connect if we used skip-grant-tables to bypass the authentication.
Is there a way to only allow a specific user to have such privilege (logging in with any password with a specific username) and not affect the remaining users?
P.s: I understand that this is not the ideal way to create an application and APIs should be used instead. However, the application is useful but not worth to redevelop.

How to give somebody access to only some MySQL tables when I cannot create a new MySQL user?

I am searching for the best solution of the following:
I need to give somebody access to one (out of many) specific database on my MySQL server through PhpMyAdmin or a similar tool.
I am not allowed to create a new MySQL user account.
Therefore I am thinking of creating a cover-up username and password (the credentials might be stored in some table or even directly in PHP somewhere around PMA), with which my somebody would log in to PMA.
PMA would use a securely stored real username and password to connect to my MySQL server. But my somebody would never see the actual database username and password. He would only see and be able to edit tables within the one specified database on my server.
Is this somehow achievable? Thank you!
PMA has a configuration for this.
$cfg['Servers'][$i]['only_db']
Read about it in the documentation: https://docs.phpmyadmin.net/en/latest/config.html
But this does not restrict the privileges of the user. It only makes the user interface show a limited subset of databases to the user. If they know the name of some other databases (or can query them from INFORMATION_SCHEMA.SCHEMATA), they can still access those databases.
If you want to enforce privileges to only a few databases, you'll have to create a distinct MySQL user and limit their privileges with GRANT.
Re your comments:
It sounds like you need to store the MySQL credentials in your PMA config file (and set $cfg['Servers'][$i]['auth_type'] to 'config'). Then you can use Apache HTTP authentication to restrict access to your PMA site (or directory), and you can create multiple user credentials at the Apache level.
phpMyAdmin is not designed to work like this; it uses the MySQL authentication structure without imposing any additional login restrictions.
One part of your requirements (not sharing the actual username and password) might be solved by using the config or signon authentication method, but that still doesn't impose any additional restrictions on the user once they log in so they'd have the same access that your user account has.
Unfortunately for you, if you aren't able to create another user account it's going to be difficult to share the account without giving them the same level of access.

MySQL Workbench - Define database in connection settings

I was wondering whether there is a way to define a specific database in the connection setup of MySQL Workbench (I know this works with other database software). Sometimes I have a lot of different databases on one server and I only want to access one with one connection. Can I specify the database in the connection settings somehow?
YES, On the home tab Click the + in MySQL Connections. And put the database name in the Default Schema: when you fill in all the usual info about ip address etc
Now if you only want to see the one database, then create a new MySQL user account and only allow this new account access to this single database. Then change the connection to the database to use the newly created MySQL account.
I guess you are seeing all the databases because you are using the root account.

PHPMYADMIN User Access

Ok so I got one linux(centos) dedicated server. I was paying someone to look after my server. Now I remember for security purpose I asked him to disable access to PHPMYADMIN for all user exvept root. Now I want to enable access to phpmyadmin for one user only.
how can I do that, so that specific user can access phpmyadmin through cpanel/whm ?
Thanks
Why don't you simply create a new user in phpmyadmin? Then you have root and the new user who can connect to the database. Unless you meant that the restriction is on server side (server user), that's a whole different story.