If the dbo had owned the table from the start, there would have been no problem removing Ted’s account.
The code would not have to use the fully qualified name, though there is a slight performance gain in doing so and is considered a best practice.
The way to determine the owner is by looking at the fully qualified object name which you can see using SQL Server Enterprise Manager or Management Studio when you are viewing a list of the tables. Only user accounts in the db_owner role can create objects owned by dbo.
Even then, under certain circumstances, the owner will end up being the actual user account instead of dbo.
In this article, I'll walk through a basic Rails (3.2.x) setup for creating a nested resource for two models.This assumes the database schema has already been created using SQL Server.In my example, I have commented out the code-first context named BPath MVCContext and replaced it with the database-first context named BPath Entities: Repeat the process for any additional controllers and you are done. However, with a little finagling you can get it work in a database first scenario.I'm sure there are several different ways to do this but here is what I did that was pretty easy.The managers of each department are members of an additional group, Widget Managers.