What are the different between users,Roles and schemas?
-
Hi all I am reading SQL server 2005 Administrating and Maintaining course and I have -I can say- good knowledge about user , Roles and shcemas but I need anyone to help me to differentiation between them. thank you
Mohammad bin taleb
-
Hi all I am reading SQL server 2005 Administrating and Maintaining course and I have -I can say- good knowledge about user , Roles and shcemas but I need anyone to help me to differentiation between them. thank you
Mohammad bin taleb
User (of a database) is a login that's permitted to use a database. Role grants privileges to objects or to the system to a user or login etc. Schema again is a logical "context" for database objects.
The need to optimize rises from a bad design.My articles[^]
-
User (of a database) is a login that's permitted to use a database. Role grants privileges to objects or to the system to a user or login etc. Schema again is a logical "context" for database objects.
The need to optimize rises from a bad design.My articles[^]
thanks a lot I was looking for that since I sent this topic but in additional to your clarification I understand more. My Best Regards
Mohammad bin taleb
-
thanks a lot I was looking for that since I sent this topic but in additional to your clarification I understand more. My Best Regards
Mohammad bin taleb
-
Hi all I am reading SQL server 2005 Administrating and Maintaining course and I have -I can say- good knowledge about user , Roles and shcemas but I need anyone to help me to differentiation between them. thank you
Mohammad bin taleb
I hope this help also. SQL Server 2005 introduces schemas to the database. A schema is simply a named container for database objects. Each schema is a scope that fits into the hierarchy between database level and object level, and each schema has a specific owner. The owner of a schema can be a user, a database role, or an application role. The schema name takes the place of the owner name in the SQL Server multi-part object naming scheme. Schemas solve an administration problem that occurs when each database object is named after the user who creates it. In SQL Server versions prior to 2005, if a user named Bob (who is not dbo) creates a series of tables, the tables would be named after Bob. If Bob leaves the company or changes job assignments, these tables would have to be manually transferred to another user. If this transfer were not performed, a security problem could ensue.