Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Chapter 5: Creating and Altering Tables
ON
118
It’s worth pointing out that, when you create a new object, no one can access it except
for the person who created it, the system administrator, and the database owner (which,
if the object created was a database, is the same as the person that created it). This
allows you to create things and make whatever adjustments you need to make before
you explicitly allow access to your object.
It’s also worth noting that you can use the CREATE statement only to create objects
on the local server (adding in a specific server name doesn’t work).
This will yield a database that looks exactly like your model database (we discussed the model database
in Chapter 1). In reality, what you want is almost always different, so let’s look at a fuller syntax
listing:
CREATE DATABASE
[ON [PRIMARY]
([NAME = ,]
FILENAME =
[, SIZE = ]
[, MAXSIZE = size in kilobytes, megabytes, gigabytes, or terabytes>]
[, FILEGROWTH = ])]
[LOG ON
([NAME = ,]
FILENAME =
[, SIZE = ]
[, MAXSIZE = size in kilobytes, megabytes, gigabytes, or terabytes>]
[, FILEGROWTH = ])]
[ COLLATE ]
[ FOR ATTACH [WITH ]| FOR ATTACH_REBUILD_LOG| WITH DB_CHAINING
ON|OFF | TRUSTWORTHY ON|OFF]
[AS SNAPSHOT OF ]
[;]
Keep in mind that some of the preceding options are mutually exclusive (for example, if you’re creating
for attaching, most of the options other than file locations are invalid). There’s a lot there, so let’s break
down the parts.
ON is used in two places: to define the location of the file where the data is stored, and to define the same
information for where the log is stored. You’ll notice the PRIMARY keyword there — this means that what
follows is the primary (or main) filegroup in which to physically store the data. You can also store data
in what are called secondary filegroups — the use of which is outside the scope of this title. For now, stick
with the default notion that you want everything in one file.