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

deprecates the older sp_attach_db functionality and has the advantage of access to as many as 32,000+
files — sp_attach_db is limited to 16.
If you use FOR ATTACH, you must complete the ON PRIMARY portion of the file location information.
Other parts of the CREATE DATABASE parameter list can be left off as long as you are attaching the database
to the same file path they were in when they were originally detached.
WITH DB CHAINING ON|OFF
Hmmm. How to address this one in a beginning kinda way . . .. Well, suffice to say this is a toughie, and
is in no way a “beginning” kind of concept. With that in mind, here’s the abridged version of what this
relates to.
As previously mentioned, the concept of “schemas” didn’t really exist in prior versions of SQL Server.
Instead, we had the notion of “ownership.” One of the bad things that could happen with ownership
was what are called ownership chains. This was a situation where person A was the owner of an object,
and then person B became the owner of an object that depended on person A’s object. You could have
person after person create objects depending on other people’s objects, and there became a complex
weave of permission issues based on this.
This switch is about respecting such ownership chains when they cross databases (person A’s object is
in DB1, and person B’s object is in DB2). Turn it on, and cross database ownership chains work — turn it
off, and they don’t. Avoid such ownership chains as if they were the plague — they are a database equivalent
to a plague, believe me!
TRUSTWORTHY
This switch is new to add an extra layer of security around access to system resources and files outside of
the SQL Server context. For example, you may run a .NET assembly that touches files on your network —
if so, you must identify the database that the assembly is part of as being Trustworthy.
By default this is turned off for security reasons — be certain you understand exactly what you’re doing
and why before you set this to on.
Building a Database
At this point, we’re ready to begin building our database. Following is the statement to create it, but
keep in mind that the database itself is only one of many objects that we will create on our way to a fully
functional database:
CREATE DATABASE Accounting
ON
(NAME = 'Accounting',
FILENAME = 'C:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AccountingData.mdf',
SIZE = 10,
MAXSIZE = 50,
FILEGROWTH = 5)
LOG ON
(NAME = 'AccountingLog',
FILENAME = 'C:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AccountingLog.ldf',
SIZE = 5MB,
Chapter 5: Creating and Altering Tables
121