17.06.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 5: Creating and Altering Tables<br />

146<br />

Figure 5-2<br />

Next comes our file name, size, and growth information.<br />

I’ve expanded the dialog out manually to make sure you could see everything. You may see less than<br />

what’s pictured here as the default size of the dialog is not nearly enough to show it all — just grab a<br />

corner of the dialog and expand it to see the additional information.<br />

Next let’s move on to the Options tab, which contains a host of additional settings, as shown in Figure 5-3.<br />

Perhaps the most interesting thing here, though, is the collation name. We have the choice of having each<br />

database (and, indeed, individual columns if we wish) have its own collation. For the vast majority of<br />

installs, you’ll want to stick with whatever the server default was set to when the server was installed<br />

(presumably, someone had already thought this out fairly well). However, you can change it for just the<br />

current database by setting it here.<br />

“Why,” you may ask, “would I want a different collation?” Well, in the English-speaking world, a common<br />

need for specific collations would be that some applications are written expecting an “a” to be the<br />

same as an “A” — while others are expecting case sensitivity (“a” is not the same as “A”). In the old<br />

days, we would have to have separate servers set up in order to handle this. Another, non-English example<br />

would be dialect differences that are found within many countries of the world — even where they speak<br />

the same general language.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!