SQL Server keeps assigning dbo Schema, even though I specify a different schema

Question

I'm using T-SQL to Create a table.
No matter what I do, the table gets created as dbo.TableName.
When I use this script
USE CBirtDev
go
CREATE TABLE [Inventory.PurchaseOrigin]
    PurchaseOriginID        tinyint        NOT NULL    IDENTITY ( 1,1 ),
    PurchaseOrigin            varchar(30)    NOT NULL
    CONSTRAINT [PKPurchaseOrigin_PurchaseOriginID] PRIMARY KEY CLUSTERED ([PurchaseOriginID] ASC),
    CONSTRAINT [AKPurchaseOrigin_PurchaseOrigin] UNIQUE ([PurchaseOrigin] ASC)
go
It creates a table with the following name: dbo.Inventory.PurchaseOrigin, instead of Inventory.PurchaseOrigin.
Why is it ignoring my Inventory Schema? If I incorporate the Database name into the script like
CREATE TABLE CBirtDev.Inventory.PurchaseOrigin it gives me dbo.CBirtDev.Inventory.PurchaseOrigin.
Totally frustrated...please help.

Answer 1

problem is your [] 
it should be this
CREATE TABLE [Inventory].[PurchaseOrigin]
Wrapping everything inside [] will consider it as name of table and hence it creates table with name as
Inventory.PurchaseOrigin under your default schema ie dbo
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page