Some of the tables in my SQL Server 2005 database is named as lu.[TableName] instead of dbo.[TableName]. What does lu stand for?
Note: I tried google already
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Some of the tables in my SQL Server 2005 database is named as lu.[TableName] instead of dbo.[TableName]. What does lu stand for?
Note: I tried google already
That would be a schema in SQL Server 2005 – which you can create yourself using CREATE SCHEMA.
A schema can be used to separate out database objects that logically belong together, e.g. put all tables related to human resources into a “HR” schema etc. DB Schemas are a bit like .NET or XML namespaces.
A schema can also be used to handle permissions, e.g. you can delegate permissions to user and roles on a schema level.
Have a look at the sample AdventureWorks database which uses schemas extensively.
That’s also one of the reasons you should always qualify your database objects with the “dbo.” prefix. If you don’t, SQL Server’s query engine will first have to check your default schema (which could be different from dbo) for the object of that name, and if not found it goes to the dbo schema. If you always use “dbo.YourTableName”, the query engine knows upfront where to look – a tiny performance gain (which gets multiplied by thousands of accesses).