The Young DBA

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.

In Short for Daniel of Service Attack ( DoS ) is a type of attack attempt to make a machine or network resource unavailable to its intended users .  Risks Associated with Denial of Service Attacks :- Network bandwidth Server memory Application exception handling mechanism CPU usage Hard disk space Database space Database connection pool

What is Difference between Logins and Users. Logins and Users are complete different things in  Microsoft SQL Server.  Many of us assumes that they are the same thing, it can get a little confusing.  The basic difference is login is created on instance level and when a login is given access to a particular database then it's call a user for that database. In simple every database user there should be a login. Logins are created at the database server instance level, while uses are created at the database level.  CREATE  LOGIN TestLogin  WITH  PASSWORD  =  'I4india@2012' select * from sys.syslogins where name='TestLogin' use company CREATE  USER  TestUser  FOR  LOGIN TestLogin select * from sysusers where name=' TestUser '   There are two main categories of logins: SQL Server authenticated logins and Windows authenticated logins. I will usually refer to these using the shorter names of SQL logins and Windows logins.

I n SQL Server, much like other services with users, login accounts can be enabled or disabled. An enabled login can be authenticated and allowed access to database resources. A disabled login is not allowed to establish a connection to the SQL Server instance. For example, let's create a login called  sumank . CREATE LOGIN sumank WITH PASSWORD = 'ipl5@2012' ,DEFAULT_DATABASE = AdventureWorks USE AdventureWorks; CREATE USER sumank In the first statement, the sumank login was created with a fairly complex password and a default database of AdventureWorks. Afterward, we switch to the AdventureWorks database and create a new user for the database. If we attempt to login to SQL Server using these credentials, we can. Next let's disable the login with the following statement. ALTER LOGIN sumank DISABLE If someone attempts to login to SQL Server using the  sumank    login, the connection attempt is rejected and Error 18470 is returned - &q