I’m an optimistic person. But for the first time in my life, with all my problems, I focused more and more on me–and it was depressing, literally. Sometimes I just wanted to quit trying to learn and speak and write again and just go into my basement and build furniture. I learned an important lesson from this. I learned that focusing on my own problems does not bring happiness. God didn’t say, “Okay. For those with problems it’s okay to focus on yourself. And for those who don’t have problems, I want you to focus on helping others.” Even in dire times God does not exempt me from his commandment to focus my life on others, because it transforms hardship to joy.

Another article ends with this powerful quote:

The person I decide to be has to be robust enough that it doesn’t matter what happens in my life… Life will happen to me. But I don’t want what happens in life to determine who Clay Christensen becomes.

—Jake Warga

Maybe you haven’t heard of Gary Fong. Even though I’m interested in photography, I hadn’t heard of him until a photographer buddy clued me in. He is known as an innovative wedding photographer, entrepreneur and writer.

In The Accidental Millionaire, Fong tells us his life story so far, giving the details of the personal philosophy that has worked so well for him. This is not the same recycled self-help crap everybody else writes. In contrast to vision, goals, tasks and actions, Fong’s more Zen-flavored philosophy comes down to exploring things that interest him, creating space for insights to happen and then working his ass off. He admits he acts on hunches, sometimes decides by flipping a coin and understands the role luck has in success.

This book will be appealing even if you aren’t a photographer.

Notes and Quotes

The bumper sticker said: SINCE I GAVE UP HOPE, I FEEL MUCH BETTER. I read it, laughed myself sick, and immediately felt the proverbial weight of the world lift from my shoulders.

In that one instant, I gave up all my focus on things going the way I wanted them to. Ever. I surrendered all my goals, my visions, my fantasies, my expectations. My Plans. I was suddenly knocked from my inner railroad tracks and felt my perspective opening up like a morning glory in the sun.

That bumper sticker gave me my freedom.

~

Zen is not really about patience, though. Because when you’re patient, you’re still secretly waiting for the outcome. Zen is about the process, not the outcome.

~

I recently read an interview with an emergency room physician who was asked, “How do you handle stress?” He replied, “Rather than focus on the outcome, I focus on the process.”

~

As a teenager, I began to see life as a game filled with creative strategies. Once I uncoupled my mind from the box of self-imposed limitations (otherwise known as “rules”), I started to realize that there were unlimited possibilities for achieving anything I desired.

And one I started to be open to anything, the game of life began to be ridiculously fun.

~

What I do is clearly define the problem at hand, then sit on it for a few days. Rather than miserably pound out a forced solution, I just keep the question percolating in my mind and let the world fill in the holes to the puzzle. My brain’s filtering process does all the work; it unconsciously scans for answers that fit the “mold” of the question. Great ideas that I never would have conjured up on purpose come to me this way. This approach has been successful countless times in my life, and it continues to be so.

When I lock into thinking about a problem, rather than pushing for a solution, the answer lands in my lap. The reason is that I’m open to seeing it. I’ve set my filters to receive it.

~

I had caught a small break, but I also knew there was no option to fail. It was do or die, sink or swim.

Rocky had once told me, “Never refuse help, Gary. Always run as far as you can with it. That’s the best way you can show gratitude.”

I took his words to heart.

~

…something [else] I’d learned from Rocky. He said, “Gary, the thing to remember is that you need to make friends with people. These people will refer you to their friends. Nobody needs another annoying salesman knocking on their door, but everyone could use a new friend.” I like that. Rocky had lots of friends. So would I.

So when I started out, I frequented the various hotels and catering facilities and florists, just trying to meet fellow travelers in the wedding industry. Instead of playing the salesman, I was honest and personal. I figured, make friends first, and the rest will follow.

~

Marketing Without Advertising teaches that people are usually passionate about at least one product or service that they have told multiple friends about. “Oh my gosh, I have the best accountant,” or, “You’ve got to got to this place for bagels.” If you can create client/allies who become the trumpeters of your product, the book says, you will never have to worry about business again.

~

Their friends would then say, “I want the name of your photographer.” That’s when my business really took off. All on word-of-mouth referrals, just like it said in Marketing Without Advertising. And all I had to do was make people happy.

~

I’ve always bristled against conformity. This girl’s incomprehensible wedding behavior helped me to see that in the absence of rigid rules, common sense becomes one’s guide. The rules lock you into an immovable position, whereas the absence of rules permits you to respond fluidly and come up with creative solutions—the best solution for the here and now.

~

She started screaming at him. “You fucking idiot! Why are you always so stupid? Do you take pills for it?”

[Too funny not to include.]

~

I had tried setting goals, and I’d realized that all it had done was make me miserable. Heading straight for a destination with blinders on prevented me from looking at the scenery along the way. And it was within the scenery that I usually spotted the detours that led to the next glorious destination. These new opportunities were then affirmed by mysterious “clues” that told me I was on the right track.

~

…had she been more open to the infinite possibilities that the world offers on a daily basis, maybe she would have made a fortune inventing something amazing out of the blue…

~

…I allowed others to have the deciding vote in my personal life. Only later in life did I learn to heed that inner voice telling me to follow both my heart and my mind.

~

I thought, I want to feel better, so I’m going to give up hope. It may seem strange, but it felt like nothing less than a spiritual awakening.

Right there in that moment, I decided I was not going to worry about anything anymore. I had worked my ass off in business and had absolutely nothing to show for it. In fact, I had more debt than case and a future that appeared bleak. But I just said, “You know what? I don’t care. I completely and utterly don’t care.”

I’d never felt better in my entire life.

~

Just as a passing curiosity, I asked him what his secret to success as an inventor was. He said that most of his success didn’t come from pulling new ideas out of a magic hat. Inventing wasn’t at all the way it was portrayed in the cartoons—light bulbs over the head and fevered cries of Eureka! You don’t wait for inspiration to strike you like heaven’s ball-peen hammer. You don’t even need to be particularly creative or technologically savvy.
The secret, Enzo said, is that if you look at anything, you will see that it cam be improved. Any object or service, especially the ones you use often, has features that just aren’t working for you. You simply have to learn to identify those things and propose solutions. Most of your ideas won’t stick, but some of them will.

~

…when one focuses on the goal rather than the process, one can be easily led astray.

~

The point I’m trying to make is that hammering away at The Plan is as likely to cause you to miss greater opportunities, or to bring about the exact opposite of your goal, as it is to bring about success. So I don’t put much stock in it as a success strategy.

Being prepared though, that’s different. As Louis Pasteur said, “Chance favors the prepared mind.”

So that’s my great success advice, after all these pages? The corny old Boy Scout motto, “Be Prepared?” Well, yeah. Except with a little twist, My motto is actually, “Be preparing.”

Preparing for what, though?

It almost doesn’t matter. For whatever cheetah you’re hot to photograph.

As long as you’re fully engaged in the process of preparing for something, that mean’s you’re learning and growing, you’re stretching and adjusting, you’re adapting to a changing world, you’re learning to read the landscape, you’re throwing out old maps. And that alone is preparing you for some next stage, even if the cheetah you were hoping for doesn’t show up.

There isn’t much here in terms of an overarching philosophy. I’m still working on that. In general though, I would say SSIS development and management is better when:

1. Packages are focused on a tight set of functions rather than doing a lot of different things.
2. Packages are easy to test.
3. Configuration is done using variables or better yet external configuration.
4. Packages can move through environments without connection managers or other components being modified (which means your configuration is done through variables or external configuration).

I’ve only worked in small and medium environments. Some of these ideas may not be applicable in larger environments.

Configuration

• Behavior and configuration should be separate where possible. Ideally you should be able to move a package through different environments (DEV -> TEST -> PROD) simply by altering configuration, never by opening up and altering connections, components and tasks. This approach makes packages easier to test (which means packages get tested more, improving quality) and simplifies deployment.
• EncryptSensitiveWithUserKey should not be used for ProtectionLevel.
• Handle configuration with variables or configuration files.
• If you are going to store sensitive information inside connection managers, at the very least choose EncryptSensitiveWithPassword for the ProtectionLevel. This way other team members can access the package (you’ll need to give them the password) without losing connection information and the team can deploy packages without having to reconfigure them on the target deployment machine. Don’t rely on the package password for security as much as for convenience.

Connections

• Don’t use explicit server names in connection managers. This becomes confusing when you are moving a package between environments. Using a more granular name (the name of a database, the name of a file) that is not tied to a physical location is better. Example: Using SQLETLPRD01.Datamart is bad. Using just Datamart is better.
• When you create flat file connections, don’t try to define the schema by hand in BIDS using the connection manager. Instead, go outside of BIDS, create a sample file using Notepad or Excel that is in the final flat file format and put some sample data it it. Then go back inside BIDS and point the connection manager to that file. BIDS will build all the metadata it needs to define that flat file’s schema. You’ll need to review it but you’ll save a ton of work.

Containers

• Break control flow tasks up into units of work using Sequence Containers.
• Containers can help readability of a package. The can also be used to group units of work that can easily be tested or rerun together.

Deployment

• (Painful. File system deployment seems like a clear winner in terms of deployment and maintenance but may not be as secure?)

Documentation

• Don’t forget that you can include documentation inside a package with annotations.
• Documentation should include notes on deployment.
• Documentation should note whether a package can be rerun after failure or whether it needs intervention by an operator, a package developer or a process owner.

Expressions

• To use a backslash in an expression, you must escape it. For example, C:\temp\ won’t work in an expression. You have to write it as C:\\temp\\.
• Building a date tag is a pain. This snippet can help. It produces the current date in the form of DDMMYYYY:

  RIGHT("0" + (DT_WSTR,2)MONTH(GETDATE()), 2)
  + RIGHT("0" + (DT_WSTR,2)DAY( GETDATE()), 2)
  + (DT_WSTR,4)YEAR(GETDATE())
  

Error Handling

• A package should never fail a SQL Agent job for non-exceptional reasons. Example. Every Wednesday a job runs an SSIS package that downloads a remote file, transforms a few fields and writes the data to a database table. The SSIS package should not fail the job just because this Wednesday the file can’t be found on the remote server. This is a non-exceptional state for the process, meaning it’s not something that should be considered outside normal operation. It happens all the time in the real world. The SSIS package should be able to handle it gracefully and notify the process owner via email or some other method.

File Operations

• Using wildcards (ex: /*.dat) does not work in the file system task.
• Using a script task is often a better way of handling bulk file operations (like deletes) than using the foreach loop task. You’ll need to reference the .NET System.IO namespace. (Remember that you can access package variables inside script tasks.)
• But use a foreach loop container if you need to execute other SSIS tasks each time through the loop.
• It is easier to delete a directory full of files than to try to delete a large number of files using scripts or file system tasks (especially if you need a foreach loop container). So if you need to create a large number of files and then delete them later, put them all in a folder. Then just create/delete the folder using file system tasks.

FTP

• Using wildcards (ex: /*.dat) does work in remote FTP paths.

Packages

• Give packages a unique name instead of Package.dtsx.
• A good package name might take the form of Project-Module-Function.dtsx.
• Packages should not have too many functions. Smaller packages are easier to test and deploy. They minimize risk of breaking functionality when making changes and redeploying. If you need to use SSIS to provide multiple related functions in the same module of a project and run them on the same schedule, it may be better to create separate packages and put them in separate steps of a single SQL Agent job. That is often preferable to developing and managing a single monolithic package.
• If functionality in a package is deprecated, take it out. If it needs to stay there for reference, clearly mark it as deprecated.

Logging

• Log to a text file instead of a SQL table. A SQL table is convenient but the file system is a more robust subsystem than SQL in the event of database problems.
• Be careful about the amount of information you include in logging. Production packages should generally only log errors (SQL Agent logs steps and run times). In other environments, more verbose output is ok.

Variables

• Create as few variables as possible.
• Using the package variable scope is usually just fine (vs. getting more granular).
• Using variable expressions is an easy way to set variable values before the control flow starts. An alternative is to set variables at the start of the control flow using a script task. The drawback to that though is that if you want to only test part of a package you can’t just execute a single container to test it—you must disable all containers/components you don’t want to execute and then run the entire package to make sure those variables are set.
• It’s a good practice to distinguish between directories and paths. A path is a directory + a filename. For example, \\fileserver01\inbound\ is a directory while \\fileserver01\inbound\2011-09-01.zip is a path.
• If you need to reference a path or a directory more than once in a package, put it in a variable.
• If you only reference a path or directory once but it is dependant on some other variable (such as the home directory for a process, which changes from environment to environment), set it in that connection’s or component’s Expressions collection.

Please leave a comment with any improvements and additions to this list. I’ll keep the list updated. Also, take a look at Jamie Thompson’s list of SSIS: Suggested Best Practices and naming conventions.

But oh wait—they want to be able to open it in an older version of Excel, which will only display ~ 65k rows per sheet. This file has 190k rows. So they ask you to write the output to multiple files, limiting the total rows per file to 60k.

Now what?

You could simply open the raw flat file, go to line 60,001 and cut-paste lines 60,001–120,000 into another file and repeat as necessary. That’s ok for a one-off task but not a good strategy if you are going to be doing this several times. It can be cumbersome and error prone to manually create several files this way.

No—the better approach is to make SSIS do the heavy lifting. I had to do this recently and thought I’d share my solution.

Here is how the process roughly breaks down:

1. Pull the data from the source.
2. Stage the data.
3. Use the number of records returned and the max number of rows I want in each file to determine how many files I’ll need.
4. For each file I need, run through a loop, figure out which rows go into the current file, give the file a name and write the rows to the file.

There are a few other details to cover too, like how to name output files and read from write to variables. We’ll look at all of that.

Package Variables

For this package I set up the following variables:

I’ve hidden the scope in this screen cap. They are all in the package scope.

Package Overview

And here is what the package looks like. It’s bare bones simple.

Create Staging Table

I drop and create the staging table from scratch each time. It contains an identity field and I want to make sure I’m always starting with a seed value of 1. I could handle this differently but this method is simple and works reliably.

Stage the Data

Next, I stage the data. That Data Flow task looks like this:

I query the source database, get the number of rows returned so I can update the TotalRowCount variable, then update the staging table.

Determine Number of Files to Write

For this particular request, the user wanted a maximum of 60,000 rows per file. I don’t show it above but the MaxRowsPerFile package variable value is set to 60000. The logic to determine number of files needed is simple:

NumFiles = Ceiling(TotalRowCount / MaxRowsPerFile)

So if the process returned 190k rows and we only wanted 60k per file:

190,000 / 60,000 = 3.16
Ceiling(3.16) = 4
NumFiles = 4

Pretty basic.

Here is the C# code to do that and set the NumFiles package variable:

Remember to set your ReadOnlyVariables and ReadWriteVariables variables appropriately in the Script Task Editor:

At this point we have pulled our source data and put it into a staging table. We know how many total rows we have. And we know how many files we will be writing. Now we need to select from the staging table and write the results to output files.

The For Loop Container

In a For Loop Container, you create some kind of condition. The loop will execute until that condition is met. I use the NumFiles variable to control how many times I run through the loop. To do this, I used the LoopCounter variable and the NumFiles variable. I start with LoopCounter = 1 and I increment the LoopCounter each time the loop executes. The loop runs while LoopCounter <= NumFiles. If I’m creating 4 files, the loop executes 4 times. Here is how the loop is configured:

The @LoopCounter and @NumFiles variables reference package variables.

Inside the loop we have to do a few things:

1. Determine which rows are going to be selected for output.
2. Name the output flat file.
3. Select the right data.
4. Write the data to the flat file.

Calculate Which Rows to Select

How can I control which rows to select? Remember above I wrote that the staging table has an identity column and it is guaranteed to start at 1 each time I run this process. I called this field RecordNum. This means I can qualify my query using the RecordNum.

To do that, I’ll need to figure out which row to start on and which to end on each time I go through the loop. I’m going to refer to that as the window and it’s defined by two package variables: LoopWindowStart and LoopWindowEnd. The logic behind calculating the window is:

LoopWindowStart = (LoopCounter * MaxRecordsPerFile) - MaxRecordsPerFile
LoopWindowEnd = LoopWindowStart + MaxRecordsPerFile

Let’s use the same numbers again and say I only want 60k rows in each file.

The first time through the loop my window looks like this:

LoopCounter = 1
MaxRecordsPerFile = 60,000
 
LoopWindowStart = (1 * 60,000) - 60,000
LoopWindowStart = 0

LoopWindowEnd = 0 + 60,000
LoopWindowEnd = 60,000

The 2nd time through:

LoopCounter = 2
MaxRecordsPerFile = 60,000
 
LoopWindowStart = (2 * 60,000) - 60,000
LoopWindowStart = 60,000
 
LoopWindowEnd = 60,000 + 60,000
LoopWindowEnd = 120,000

The 3rd time through:

LoopCounter = 3
MaxRecordsPerFile = 60,000
 
LoopWindowStart = (3 * 60,000) - 60,000
LoopWindowStart = 120,000
 
LoopWindowEnd = 120,000 + 60,000
LoopWindowEnd = 180,000

And you can guess what the 4th time looks like.

But won’t there be overlapping values?

No. And you’ll see why below. But first, here is the C# script that shows how we set the LoopWindowStart and LoopWindowEnd variables:

Again, don’t forget to set the ReadOnlyVariables and ReadWriteVariables.

Name the Output File

I created a Flat File Connection in the Connection Manager. (Hint: always create a sample file first with 1 row and create your flat file connection by pointing it to the sample. That way you don’t have to create the entire definition in the connection editor, which is about as appealing as getting jabbed in the eye with a rusty can opener.) In the flat-file connection properties, I used the Property Expression Editor to set the ConnectionString.

When I created the package initially, I set the HomeDir variable to point to my final output directory (including a trailing slash). The HomeDir might look like C:\output\. (Like the MaxRowsPerFile variable, I set this at design-time. It’s not something I set through scripting.)

OutFileName is a variable but we haven’t set it through any scripting. So how does it get set?

Go to the property editor for the variable and set EvaluateAsExpression to True.

Then go into the Expression Editor and use a combination of literal strings and the LoopCounter to create the filename:

Your outputfiles will evaluate to:

output-1.txt
output-2.txt
output-3.txt
etc...

Each time through the loop then you will be writing the following files:

C:\output\output-1.txt
C:\output\output-2.txt
C:\output\output-3.txt
etc...

Select Output Data and Write to Output File

Here we need to select specific rows to bring into the Data Flow. That Data Flow task looks like this:

The staging table query uses the LoopWindowStart and LoopWindowEnd variables. There are two parts to this. The first is to write the query with the parameter placeholders:

Notice how I’m using WHERE RecordNum > ? with AND RecordNum <= ?. This is why the records won’t overlap. Say I have 190k records and will be writing to 4 files. This means 4 times through the loop and it means 4 windows. Here is how things will look.

1st Pass through loop:

LoopWindowStart = 0
LoopWindowEnd = 60,000

WHERE RecordNum > 0
AND RecordNum <= 60,000

Records 1 - 60,000 output to c:\output\output-1.txt

2nd Pass

LoopWindowStart = 60,000
LoopWindowEnd = 120,000

WHERE RecordNum > 60,000
AND RecordNum <= 120,000

Records 60,001 - 120,000 output to c:\output\output-2.txt

3rd Pass

LoopWindowStart = 120,000
LoopWindowEnd = 180,000

WHERE RecordNum > 120,000
AND RecordNum <= 180,000

Records 120,001 - 180,000 output to c:\output\output-3.txt

4th Pass

LoopWindowStart = 180,000
LoopWindowEnd = 240,000

WHERE RecordNum > 180,000
AND RecordNum <= 240,000

Records 180,001 - 190,000 output to c:\output\output-4.txt

Pass the variables to the query using the Parameters editor:

This pulls the rows I want into the Data Flow.

The last task simply points the Data Flow to the Output File. That's it.

I'm interested to see if anybody has come up with something better.

(This was a quick SSIS package I threw together to handle a simple request. It lacks error handling and logging and I wouldn't use it like this in a mission-critical scenario.)

Caitlin on Facebook Business Pages and Twitter

• Facebook is good for connecting with people you already know.
• Twitter is great for getting to new people.
• Post on both personal and business topics.
• Personal posts help build trust.
• Engage. Don’t just promote.
• Ask questions, start conversations.
• Use Twitter lists to help identify people you want to connect with.
• Follow others that do the same thing that you do. Retweet them. Don’t be afraid to share.

Caitlin on Blogs

• A blog is good because it’s interactive.
• Think about blogs and social media in terms of sharing.
• Even if you give people information, don’t think that means they won’t still need you to help them out. Don’t be afraid to share.
• Don’t take easy things for granted. Share them. What may seem simple of obvious to you may be something that somebody else needs help with.

Caitlin on LinkedIn

• Fill out your profile to 100% completion.
• Link to Twitter, your blog and Facebook.
• LinkedIn is great for getting introduced to 2nd and 3rd degree connections. Connect with everybody you know. This will build your 2nd and 3rd degree connections.
• Don’t send the default generic invite to people. Personalize it. Let the person know where you met them or how you know them.
• Never SPAM people.
• Ask for recommendations from the people you’ve done business with.
• Use groups and discussion pages to connect with people.

Andrew on Brand and Clarity

• When businesses stray from their core business values, they tend to falter or outright fail.
• Brand Position = Expectation
• Strategic Positioning = Sustainable Competitive Advantage (advantages to clients, advantages to self).
• A sustainable competitive advantage is: doing different activities than competitors OR doing similar activities in a way that is different than competitors.
• Have a clear position (what you say you stand for) and communicate it clearly.
• Distinct or Extinct. It’s better to be rejected than ignored.

Andrew on Relationships and Social Media

• Basic human relationship principles apply to business relationships.
• As a business, ask yourself if you are right for the customer. Ask if they are right for you. Learn to say no when the fit is not there.
• Customers are more active now in how they engage you.
• Even if you don’t engage in social media you must at least listen and address social media feedback. What is the sentiment? How do people feel about you?
• When clients ask for something, find out why they want it or think they need it. Just because they want it doesn’t mean it’s a good fit for their strategy. Some tactics can do more harm than good. It’s your job to help guide the client.
• You can use social media to listen in on a conversation to understand how you may want to position a brand.
• A business owner must answer the question: “What does a real lead look like to me?” Know what you want. Use BANT to qualify a lead. Budget, Authority, Need, Timetable. Does the client have a budget? Does the person you are working with have the authority to make a decision? Is there a clear and legitimate need [My notes missed Need so I'm guessing a little on this one. - Rob]? Does the client have a deadline?
• It’s ok to say no and refer a lead to somebody that is a better fit.

Andrew on Websites

• A website must deliver an experience that is consistent with the rest of your interactions.
• A website doesn’t have to be amazing [thank you for saying this - Rob]. It merely has to be adequate. BUT! It must address and answer prospects questions.
• Websites must support mobile even if it supports it in a very simple manner.

Andrew on Other Things

• (A speaker gets points if they talk to audience members before the event then weave details of those conversations into the thread of their talk.)
• Before you invest in something always consider: “What do I want to get out of this?”

Andrew also talked about Some Keys to a Business that Will Survive

1. Establish your brand:

• You need a Sustainable Competitive Advantage.
• Be clear on who you are and who you are not.
• Be clear on who you serve and who you do not serve.
• Be clear on what you do and what you don’t do.
• Pick your market and pick your battles.
• Clarity is incredibly important in this.

2. Have an adequate website.

3. Talk to customers using their language (not your jargon).

4. Be authentic. This is a clear massive advantage small businesses have over bigger competitors. It is hard for big businesses / corporations to be authentic.

It was a great event. Caitlin and Andrew shared a lot of solid information. Also, City Steam‘s ravioli was excellent.

—Jack Welch

You may not be aware of this fact but DBAs (database administrators) are actually world renowned for their impeccable display of sartorial savvy. What the average man knows about fashion would fit nicely within a CHAR(4) field. What the DBA knows about fashion requires a VARCHAR(MAX) field. At least.

By the way, the author would have you know that he can speak with total and complete authority on female DBA fashion as well as male. But he will let a female DBA tackle her own sex. Today he will tackle only the male.

Moving right along then, we will begin at the bottom and work our way to the top.

Shoes

The discerning DBA accepts only the finest shodding. He is always careful to balance the need to optimize for cost and speed vs the effort required for maintenance.

Shoe laces should be made with a material that facilitates speedy lacing to accommodate the DBA’s nimble fingers. If the DBA can get velcro, even better.

The sole should be thick and sturdy for kicking the stuffing out of servers. The shoes should fit snugly so they don’t fly off during these frequent maneuvers. The color, texture and material of the rest of the shoe is of absolutely no concern.

As everyone already knows, the first DBA was Herman Munster. So the respectful DBA will often try to find shoes that honor Herman’s memory and our shared DBA heritage.

Socks

The sock of choice for the well-dressed DBA is the white knee-high tube sock.
Stripes are preferred but the careful DBA will observe that too many stripes will make him look the dandy.

Tube socks are low maintenance and the color white is compatible with any color pants or shoes. This sock is also on the compatibility matrix for most versions and editions of Microsoft Windows Server.

A bonus is that tube socks hold their shape well and can be pressed into service as puppets when the DBA is elucidating DBA concepts to a non-DBA.

Pants

It is important for the DBA to always present a professional, polished look. The appropriate pair of pants is one of the keys to achieving this look.

The green, pleated, creased, elastic-waisted, stain-resisting, no-iron, no-wrinkle, tumble-dry-on-high khaki is the obvious pant of choice: green pants go well with white socks. They go well with everything else for that matter.

All professional pants are creased. The DBA is not going to be caught behind the curve so his pants will also be creased. Pleats and an elastic waist give the DBA a large degree of freedom and maneuverability, both necessary for communicating with his storage engineer and accommodating the digestion of late night pizzas.

After a few washings, the pants will become fasionably distressed. The edges of the creases will start to turn white giving the pants that “I live in these pants 24/7/365″ look. This is exactly what the DBA wants. And he will consider himself lucky if he can get there after just a few washes. This is a subtle way the shrewd DBA demonstrates a commitment to hard work and thus boosts his worth in the eyes of his manager.

A belt is entirely optional. Bits of lashed together twine, rope or USB thumb drive lanyards are acceptable substitutes as they help the DBA convey his “I can fix anything, just like MacGyver” attitude.

Shirt

The DBA’s shirt is the second mainstay of his professional look. To make sure his arms always stay cool, the pragmatic DBA chooses short sleeves. Always. This also keeps his arms and hands moving freely while typing and making wild gesticulations to his storage engineer. All other details such as color, stitching, pattern, fabric and texture are entirely immaterial.

Otherwise, the DBA will choose a short-sleeve polo shirt. They require some prep work before they can be worn however. Most polo shirts are made with too much material. Therefore it is crucial that the DBA run it through the washer and dryer on high heat multiple times to remove any billowing. It’s important that superfluous shirt doesn’t get in the way of getting the job done.

But how to know if the shirt fits properly? If the arms are lifted straight overhead, approximately 3 inches of belly should be showing above the belt but below the bottom of the shirt.

In certain cirumstances it may be necessary for the DBA to wear a clip-on tie. In this case, the button up short-sleeve shirt is often the best choice. A polo will certainly do just as well in a pinch.

Above and Beyond

It is hard to improve upon this look. It is vintage DBA. However, there are a few touches that can add that extra bit of oomph to the DBA’s look:

1. Calculator watch for instant storage calculations.
2. Cell phone holster.
3. A second cell phone holster for a second phone.
4. Several pens for the shirt pocket (button up only).
5. Cheetos crumbs sprinkled liberally on shirt and pants.
6. A moustache. Just a moustache.
7. Cheetos crumbs sprinkled liberally on moustache.

Clickity-click-done. (I know, being a DBA can be tough sometimes.)

Ok. But what about the default location for backups?

Microsoft has done you a favor by hiding this configuration value. Now is where you get to show off some real skills.

Click Start -> Run. Type regedit and click Ok.

Now that you’re in the Registry Editor, navigate as follows starting from My Computer:

-> HKEY_LOCAL_MACHINE
 -> SOFTWARE
  -> Microsoft
   -> Microsoft SQL Server
    -> MSSQL.1 (default instance)
     -> MSSQLServer

Look for the BackupDirectory REG_SZ entry. You can change this to wherever you usually put your backups. You don’t need the trailing slash. For example on one machine backups are on S:. On another, smaller machine, they are on P:\Backups.

I’m not sure why Microsoft didn’t expose this configuration value directly through SSMS but it’s no big deal to make the change.