How to Create Read-Only User in MySQL using workbench

Friends,

Till now I haven’t got chance to vote in any election for PM or CM. This month everywhere talking about elections and here I am busy with my work connect-share-discover with database and applications..

Today I want to share How to Create Read-Only User in MySQL using workbench.

First Go to Users and Privileges option from Workbench Managements Tab.
Click on Add account and give account name and their respective password, after that apply.
In Users and Privileges box there are 2 other tabs, Administrative Roles and schema privileges.
Administrative Roles is Similar to Fixed Server roles of SQL Server.
Schema privileges is schema level authorization process.
Select Schema privileges and click on Add Entry.
Then a Dialog box will come with schema available in server. Now select any schema which privilege we have to configure.
After that give the appropriate rights which we have to give. As I have selected on select.
Finally click on Apply.

To check connect with the same user and try to insert/update/delete.

Comments

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. · 23 May 1995 - First internal release · Year 1996 - Version 3 o Simple CRUD operations o January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o production release 1998, from www.mysql.com · Year 2002 - Version 4 o MyISAM o unions o Tracking o B-trees o s...

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.) Creation of Application/Proxy user where Application is hosted. 2.) Give appropriate access to the user. 3.) Create Database Login user on database. 4.) Authenticate User and provide credential on IIS. 5.) Then Configure web.config on Application.

The Young DBA

Search This Blog