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 |
|
bogey
Posting Yak Master
166 Posts |
 Posted - 2005-06-13 : 10:42:35
|
| Should all tables be owned by dbo or is it ok to assign ownership to specific users?thanks. |
|
|
Thrasymachus
Constraint Violating Yak Guru
483 Posts |
Posted - 2005-06-13 : 10:49:18
|
| It keeps things simple with regards to permissions. Concievably, I could see a nightmare scenario on a production box where users are creating database objects on the fly (yikes) in an application where you may want to establish indvidual ownership of tables and SPs but I would not reccomend it.This is however acceptable on a development server where you have developers creating and destroying objects all of the time.Sean Roussy |
 |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2005-06-13 : 10:57:32
|
| There may be reasons to do this, and I'v e seen several 3rd party vendor apps do this, but every single one I've looked at has been a real pain in the butt.....and I saw no benefit to it.It seemed like they used different owners to isolate tables for security reasons.They very well could have done the exact same thing using groups.I've even seen one where the had the exact same table names with different owners. They must have had a reason, but it was very confusing. Again, here they easily could have used local or global temp tables I would imagine.I never use any other owner in production other than dbo.Brett8-)Hint: Want your questions answered fast? Follow the direction in this linkhttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx |
|
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2005-06-17 : 09:48:28
|
| If the user has an absolute need (which is really pretty rare) to be able to truncate a table, (s)he would need to own the table. This, however, does also convey the right to create over 200 indexes. I could see a user owning an import table that is commonly truncated, but for tables that are in use every day (e.g. the stereotypical orders table), the user does not need the elevated rights, and probably should not own them.Ownership of individual tables mainly seems to be a hangover from Oracle developers/DBAs, who have not done a lot of SQL Server work. |
|
|
|
|
|
|
|
|
Should dbo own all talbles