Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mazhil
Starting Member
3 Posts |
 Posted - 2004-02-10 : 17:03:11
|
| Do you have any idea to alias NT user group to a database as dbo? |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-02-10 : 20:40:18
|
| Create a user in the database using that group/login, then add it to the db_owner database role. |
 |
|
|
mazhil
Starting Member
3 Posts |
Posted - 2004-02-11 : 11:16:09
|
| If we add the group in the db_owner database role and when a user from the group creates one object(Table/ proc) the object is created in the owner's name not as dbo and others cannot directly access the table. It happens to change the statement as select * from [Domainname\User].tableDo you feel any other method? |
|
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2004-02-11 : 11:37:32
|
| You Could have the user add this to the create table procidure.GRANT SELECT , UPDATE , INSERT , DELETE ON [dbo].[Tablename] TO [public]JimUsers <> Logic |
|
|
|
mazhil
Starting Member
3 Posts |
Posted - 2004-02-11 : 18:33:23
|
| The problem here is say for example a table Account exists in the database, the owner is dbo if the group user creates a table in the same name the database will allow to create with owner Domain\user. Here two tables with same name and different user exists in the database when we grant permission there will be confusion to the other user |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-02-11 : 22:10:54
|
| Since SQL Server doesn't support synonyms (don't worry, they will in Yukon), this is one of the reasons why it's cosidered a best practice to have all database objects created by dbo. Non-admin users should either not create any objects, or at least no objects that need to be available to other users. Anything that must be publicly available should be created by the actual dbo. |
|
|
|
|
|
|
Alias NT user