Table naming convention in Adventure Works DataBase in SQL Server 2005
I have noticed that some tables in the Adventure Works DataBase in SQL Server 2005 are named as dbo.[TableName] and some are named as
Person.Address,
Person.Contact,
Person.ContactType etc etc
How can i create a table along these lines.. i.e Person.[tableName] rather than dbo.[TableName]
when i try creating a table and naming it as Person.ContactDetails it does'nt do it.. Instead it creates a table as dbo.Person.ContactDetails.
when i see the properties of the these tables (Person.Address, Person.Contact, Person.ContactType ) i notice that the table Schema is declared as 'Person' what does table schema mean?
Any Suggessions??
COllin
Person.Address,
Person.Contact,
Person.ContactType etc etc
How can i create a table along these lines.. i.e Person.[tableName] rather than dbo.[TableName]
when i try creating a table and naming it as Person.ContactDetails it does'nt do it.. Instead it creates a table as dbo.Person.ContactDetails.
when i see the properties of the these tables (Person.Address, Person.Contact, Person.ContactType ) i notice that the table Schema is declared as 'Person' what does table schema mean?
Any Suggessions??
COllin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you so much for your Quick reply...
Just a couple more things...
Does it mean that in Adventure Works DataBase the Database Owner(dbo) is changed from its Default i.e dbo to Person.
So How does that help ?? I mean what benefits does it gain to change the dbo to someone else within the same Database
Just a couple more things...
Does it mean that in Adventure Works DataBase the Database Owner(dbo) is changed from its Default i.e dbo to Person.
So How does that help ?? I mean what benefits does it gain to change the dbo to someone else within the same Database
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>> Multiple tables with the same name in the same databases but haing different schema.
Exactly, It might also be clearer if you group different tables together in this way. No real benefits in my opinion though.
Exactly, It might also be clearer if you group different tables together in this way. No real benefits in my opinion though.
second thing should create table like this
CREATE TABLE [person].[Table_1]
instead of
CREATE TABLE person.Table_1
CREATE TABLE [person].[Table_1]
instead of
CREATE TABLE person.Table_1
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
exec sp_changedbowner 'Person'