I need your help about creting roles & permissions in NAV. I do not want the user to use 'File --> Database --> New', is there a way to enable/disable?
But, do you think it will work?
I think the permissions get activated only after logging in and the user can always create a NEW (native) database without first logging into another DB???
Willing to learn more on this line!
"A bove maiore discit arare minor"-"From the old ox, the young one learns to plow."
System 2510 Edit, Find Yes Yes Yes Yes Yes
System 2520 Edit, Replace Yes Yes Yes Yes Yes
System 3220 View, Table Filter Yes Yes Yes Yes Yes
System 3230 View, FlowFilter Yes Yes Yes Yes Yes
System 3410 View, Sort Yes Yes Yes Yes Yes
System 3510 View, Design Yes Yes Yes Yes Yes
System 5830 Tools, Security, Password Yes Yes Yes Yes Yes
3. Syncronize the specific login and check.. it will work...
In which database? And it will work even if you open client and you will not login into any database? ;-)
This cannot be done thorugh any permissions, because permissions are conencted to some DB, but creating new DB is no connected to any other DB because in time you are creating new DB, you are not logged into some DB with permissions to disable this... :whistle:
But if you're running on sql you can alter the permissions there.
But the question remains, why?
There is no reason why a user would create a db on their own.
Unless the users are children.
|Pressing F1 is so much faster than opening your browser| |To-Increase|
Yes, it is like permit creating new folder with name "New folder" or to create new document within MS Word because else user will have many empty word files in his folder...
CREATE DATABASE permission defaults to members of the sysadmin and dbcreator fixed server roles. Members of the sysadmin and securityadmin fixed server roles can grant CREATE DATABASE permissions to other logins. Members of the sysadmin and dbcreator fixed server role can add other logins to the dbcreator role. CREATE DATABASE permission must be explicitly granted; it is not granted by the GRANT ALL statement.
CREATE DATABASE permission is usually limited to a few logins to maintain control over disk usage on the computer running SQL Server.
So, if the user is in the role public, they can't create a database.
But they can on their own SQL Express installed on their PC etc. It means, you can permit where they can create the database, but you cannot do that in general in the client. 8)
But they can on their own SQL Express installed on their PC etc. It means, you can permit where they can create the database, but you cannot do that in general in the client. 8)
Hehe thats right, but you can permit it on the main server or test server ....
Exactly what problem are you trying to solve? I know you say you want to prevent a user from creating databases. But why? If you've setup your system properly, then no non-admin user wil be able to create a database on the server (native or SQL). Yes, they could create one locally on their own workstation. But would that create a problem?
Comments
I think the permissions get activated only after logging in and the user can always create a NEW (native) database without first logging into another DB???
Willing to learn more on this line!
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
2. Select permission as follow as
System 2510 Edit, Find Yes Yes Yes Yes Yes
System 2520 Edit, Replace Yes Yes Yes Yes Yes
System 3220 View, Table Filter Yes Yes Yes Yes Yes
System 3230 View, FlowFilter Yes Yes Yes Yes Yes
System 3410 View, Sort Yes Yes Yes Yes Yes
System 3510 View, Design Yes Yes Yes Yes Yes
System 5830 Tools, Security, Password Yes Yes Yes Yes Yes
3. Syncronize the specific login and check.. it will work...
In which database? And it will work even if you open client and you will not login into any database? ;-)
This cannot be done thorugh any permissions, because permissions are conencted to some DB, but creating new DB is no connected to any other DB because in time you are creating new DB, you are not logged into some DB with permissions to disable this... :whistle:
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
But the question remains, why?
There is no reason why a user would create a db on their own.
Unless the users are children.
|To-Increase|
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
RIS Plus, LLC
CREATE DATABASE permission is usually limited to a few logins to maintain control over disk usage on the computer running SQL Server.
So, if the user is in the role public, they can't create a database.
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Open SQL Server Login Properties (by right click on the Login). Select "Server Roles" --> "Database Creators" --> You should uncheck this..
Even no need to check anything in the server roles. You just have to give Database Access for the specific database.
Definitely it will work.. why because i have implemented same in my client place too..
Hehe thats right, but you can permit it on the main server or test server ....
How can we disable this permission of creating new database with classic ?
You help regarding this is highly appreciated.
S.V.Sudhakar
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.