SQL Database What?

This may or may not depict how I feel right now.

I’m sitting in my database class right now. That’s right. I’m in class. I will attempt to focus for the next 3 hours (6 pm – 9 pm), but I make no promises. Actually, as I write this, my instructor is discussing something about how SQL server uses FILESTREAM, which stores data in a shared folder outside of the database, but SQL stores the location pointer in the database. Awesome! (Actually, I bet that description is completely wrong. That’s what happens when you don’t pay attention, ha!). 



SQL Server Administration class. Coffee is neccesary.

You see, the class I’m taking is Microsoft SQL Server Administration, which is part of my Certificate in Relational Databases through the University of Calgary. I’m all about learning and stuff. The first two courses in the certificate were related to SQL programming. At work, my statistical and database programming is done using SAS, and I can use the SQL procedure for my data manipulation. It makes life easier. So the first two courses were very helpful. However, SQL Server Administration? Say what? Exciting topics include installation and configuration, database management, SQL security, backup and restoring, automation, server monitoring, and high availability. Basically, I’m learning things that I probably won’t ever use, but I think they’re good to know. You never know when or what information will come in handy! For example, apparently it’s not a great idea to put your database on the C: drive. Makes sense I guess :). And a question was just asked- What are the important reasons for a transaction log? My answer: [Umm…. thinking… thinking… nothing]. Correct answer: backup, restore, and performance. Well then… *shrugs*… close enough. Obviously, I need to pay more attention.
Wrong answer. Close enough.