Well I am getting ready to head off for another trip, this time I am going to film some sessions for the upcoming SSWUG Summer Conference. As I am looking into a few of the subjects I will be speaking on I got lost in the blog chain where I found one great post after another. One that I stopped on was an interview done with Claire Brooking by Sarah Blow. The entry in whole was well done, as it talked about how Claire saw women in technology. What I found of most interest was the last question that I think I get asked most often. What piece of advice would you give to anyone wanting to get into an IT career?

If you want to look into the original article it can be found here.

As I was contemplating the answers that Claire gave one in particular jumped out at me. Listen to other people…, the more and more that I thought about this I could not help to think about what this means. I think this piece of advice could be meant to everyone everywhere, but as I apply it to what I have done over the last 5 years I cannot help but to think of really how important this is and how much this is not happening. So I challenge you as readers are you really listening to what is being said?

A number of years ago I was the Senior Administrator at a company where a major upgrade was being developed that would dramatically impact the business. I was always caught off guard by the number of times that management would push deadlines and deliverables. There were a number of times when management would not ask the development time of a specific task but instead would state what they wanted done and when they wanted it done by. The lead developer on the project would try to meet those project timelines but when deadlines were missed or were under delivered, the wrath of management was felt. The employees under this one manager would even get to the point where they knew every 6 months the VP of that group would have a week where no matter what the circumstances were everyone in the group was a slacker, everyone in the group was at risk of being fired and everyone in the group was worthless.

Phil Factor posted an entertaining piece on IT in the Sci-Fi world and how the teams could or could not reprogram a ships function. As he went through this he pointed out the sad but true methods that we have put in place. If the future holds the same attitude as the present for moving towards a single goal we are in sad shape. Well that is my opinion.

As I am now no longer in the employment of the company that I mentioned earlier it is much easier to see the issues. The biggest one is the lack of anyone’s ability to listen.
If the VP would have listened then maybe the developers would have been able to set a better expectation on management of the challenges they were going to face and either get the help needed to overcome those, or adjustments to make sure that proper expectations were being set. If the development team listened a little more they may have understood the importance of the release and how much it would have impacted the company.

As basic as it sounds I am surprised at how much that I see this. Everyone wants to do the best they can, many want to be the Hero or the Super Star, the Most Valuable Player, how many people set out to be the supporting guy or gal, the backup singer, the team equipment manager? Does all this desire to be the “Hero” put people in the place where they are in the mindset of, “I know what needs to be done and I know how to do it”? I don’t mean to take away from people who are the go getters or the just get it done. Maybe this is a little of self refection, I know that If I were to listen more then I could be in a better place.

Well I guess today is a true rambling. I am amazed at how a simple statement can get me thinking.

First of all I would like to send a congrats out to all the new and Renewed MVP’s.

Over the last couple months I have been working on a few consulting jobs and helping out here and there with different projects and companies. I can’t help but notice that I see a number of reoccurring problems. The funny thing is that it first appears as a technical issue, and it ends as a technical issue. But I cannot help but notice over the last 5 years how some problems become magnified just because people are afraid to say, “let’s review my area because I may have missed something”. I use to think this had a lot to do with Empire building. Empire building is something that a person does when he believes his or her responsibilities are not as well rounded as they would like them to be. Today I am not so sure.

For Example:

I worked at a company for a number of years; they decided to implement a SAN as storage. There was a very lengthy process that we went through to move databases from local to SAN storage. One database in particular was of interest, It had a Delphi App that would gather data and then insert into the database every night. When the database was on local storage this process would take about 4 hours if I recall correctly, however when we moved it over to SAN storage the performance degraded.

There was only one change that was made to the system. It was the introduction of the SAN. However, when it came around to it the hardware people, the developer, the network people and the vendors were not willing to approach the situation openly. To be honest I am not sure that I did it as openly as I could have.

The answer that I would really like to get down to is why we put a fence around our area of responsibility, if we all have the same goal of correcting a problem. Maybe even a more important question is how do we break down that wall and ask the right questions or take the right approach so that the time spent finger pointing is put to a better use by trying to correct and or fix an issue.

If you have not seen this yet, I recommend that you take a look at it. I got this e-mail about a week ago and thought I would look into it. It ends up that this will install a trojan in your system if I am reading correctly. It appears that Firefox and IE will not display this page. However, I would not even try at this point.

For the last couple weeks I have been on the road working on a contract located in Richmond VA. I can tell you that this has been an experience. I have had so much fun. There is a lot to be said for being a contractor. However, I am ready to go home; I miss my family and really need to know what it’s like to sleep in room where kids are not running around screaming their heads off. In the weeks to come and at the upcoming SSWUG Conference, I am going to talk about some of the new things that I have learned. But for now I thought I would share some of the things that I have learned that were outside of SQL Server. I will update this list over the next couple of days if something comes up.

• Tossing the Chicken – This computer malfunction is one that is unexplainable. Many times these are associated with errors that are very open in nature and really don’t point to a lot.
• This is the South – The first day that I was here, I figured I was in the east, maybe even as far to say I was in the North East. Being that I am from Colorado and have spent almost my whole adult life on the west coast I know very little about where the lines are drawn. With that being said a very kind waitress in a local restaurant told me that I am indeed in the south, not just the south but the SOUTH. I guess I should have paid more attention to my history.
• I’ll tell you what – Still working on how to define this. I know when I was in Texas a number of people used this term; I guess it’s sort of a term that you have to use to enforce what you are defining. For some reason I believe that if someone were to use this term, it is very close to when someone in Colorado finish’s a statement with “Honestly”. If I were to use this in a sentence it would have to be something along the lines of: You think he is crazy well I’ll tell ya what. However, being the Cowboy that I am still not sure if I have a grasp on this.
• Same issues – I did find it odd that even though I was about 1800 miles from home, many of the basic problems that we see in Colorado are shared all around the country.
  • Hardware does not fix all issues
  • Reboots do not correct all issues
  • Issues are solved by gathering info.
• It’s a dry heat – Welcome to crazy 101. Today it is 86 degrees but it feels like 110 in AZ. I kid you not (another new term I learned). I use to come from the school of if its 86 in Colorado it will feel like the same 86 degrees on the east coast. This is so not true.
• Not have e-mail sucks – I have never put it together on how much we rely on e-mail. How did we live in the days before e-mail? I have been insane running around town trying to find hot spots just so I can check e-mail at lunch. That is another fun thing to do is look for a hot spot in a city where you have no idea where you are or where you are going.
• Work is not the most important thing in your life – Well I hope it’s not.

I was tagged by Tjay for this latest viral quiz. I am not sure where this one started but what the heck, it’s the summer and many times I am fighting the desire to be on one long vacation.

Here are the Quiz details

“So You’re On A Deserted Island With WiFi and you’re still on the clock at work. Okay, so not a very good situational exercise here, but let’s roll with it; we’ll call it a virtual deserted island. Perhaps what I should simply ask is if you had a month without any walk-up work, no projects due, no performance issues that require you to devote time from anything other than a wish list of items you’ve been wanting to get accomplished at work but keep getting pulled away from I ask this question: what would be the top items that would get your attention?”

Well there are a number of things that come to mind. First would be how do I get my camper, where is the power to hook my camper up to and do I have enough food for Smores. The reality is that I when I go camping or if I was stuck on an island my mind would continue to head back to work. I think the number one thing I would do would want to start testing and playing with the new features of SQL Server 2008. I would want to pick up enough detailed information where I could teach a workshop on something like database mirroring or the resource governor. As much fun as it is to learn something new and to do it in the idea lab environment I think I would have to use it on a real live system, that is where it is put to the test. Where I learn the most.

Now who should I tag…

I think I will tag Ted Malone, Jeremy Lowell and Donald Farmer.

Well the SSWUG Fall event is starting to be planned. It just seems like yesterday and we were doing the spring conference, but now we are looking at the fall. The SSWUG Ultimate conference will be October 21^st to 23^rd. This is going to follow the summer show that is planned for July 22nd -24^th. If you are interested in the summer conference, it is a best of event. This means it has all the best sessions from the Spring 09 show and the fall of 08. You can find more information for the summer show here.

If you would like to be a speaker for the upcoming fall event please send me an e-mail at Chris@sswug.org. We are looking for topics about SQL Server, .NET Development, Business Intelligence, and Share Point. We are requesting that speaker present at least 3 topics.

What I really like about the upcoming conference is that these are all sessions that were scored high by the attendees. Here is a short list of the great speakers. I truly feel honored to be numbered among them.

Wednesday, July 22 – Friday, July 24 SSWUG’s Summer ‘09 Refresher vConference Business Intelligence, SQL Server, .NET Development and Sharepoint. Top content, top industry speakers and top accessibility…all online.  Hi Everyone,We’ve opened up the Early Bird Registration for the SSWUG.ORG Summer Refresher vConference!     Mark your calendar for July 22-24, 2009 and join us for three days of amazing content. We’re showing the “Best-of-the-Best” during this vConference. Check out everything that’s included here.   Early Bird registration is $60/discipline. You can also get the Summer vConference and the Fall vConference (with all new content) for only $145/discipline.     These Early Bird rates go up on June 22 so don’t hesitate! See you online!

Speakers:  Chris Shaw Paul Nielsen Brent Ozar Buck Woody Eric Johnson Hilary Cotter Jason Strate Josh Jones Kathi Kellenberger Kevin Kline Ted Malone Thomas LaRock

Well I don’t normally do this, because I think if you put something on your blog it should be something you did. However, this one at this time I think is really important and I cannot find a web based link for it. The author of this is a Teena Rose. I got this passed to me by a recruiter I know in North Carolina. If you are looking for work in that area, you may want to send me a note and I can put you in touch with someone who is really putting every effort forward to help her candidates.

Enjoy…

10 Things You Must Do Before That Successful Interview

You’ve worked hard to get here. You’ve sent out 31 resumes, networked, attended job fairs, enrolled in school for more education – you’ve taken all the right steps.

Then, one afternoon the phone rings. “Yes, we’d like you to come in for an interview. Is next Tuesday at 10:00 alright with you?” Alright???!!! You can be there in 10 minutes! But you gather your composure, pretend to rifle through your “appointment book” and calmly reply, “Yes, Tuesday at 10:00 works for me. See you then.” Now what?

The sequence goes like this: the resume gets you an interview; the interview gets you the job. This is when you become more than a bunch of employment dates and workplace accomplishments. This is your opportunity to shine. It’s show time!

Go in cold and you’re working at a disadvantage. You prepped the perfect resume, now it’s time to prep for that all-important interview. Here are ten steps you should take before you show up at the interviewer’s door.

1. Review your resume.
   

   Sure, you know it by heart. But what was it that caught the eye of this recruiter or the HR pro? Specialized experience? Unique training? A steady history of career advancement? Revisit your resume from the point of view of the interviewer. It may provide insight into the company’s employee needs – something that would certainly be advantageous to know going in.
   

2. Get back on-line.
   

   The Internet served you well in the preparation of personalized cover letters targeted at the recipients’ needs. Okay, visit the company web site again and start taking notes. Corporate officers, the latest press releases, the company’s annual report. Gather as much information as you can on your soon-to-be-employer.
   

3. Study, study, then cram.
   

   The more you learn about your callback company, the better you’re going to feel walking in that door. Knowledge is power. Knowledge will make you more confident in your attitude and your answers. You know this stuff. You’ve studied it! Knowledge of company products, services, protocols and procedures shows the interviewer that you’re proactive, with an eye for detail and an appreciation for the power of preparation. In other words, you’ll make a positive impression.
   

4. Rehearse your interview.
   

   How can you rehearse for something that doesn’t have a script? Write one. You know the typical questions you’ll be asked so write down some of your most insightful, witty thoughts regarding the state of your industry and profession. Be prepared to describe past positions, responsibilities and accomplishments. This is not a time for false modesty, so don’t be afraid to highlight your professional strengths and play down your terrible typing skills. Remember: it’s no brag if it’s the truth. Ask your spouse, your child or a friend to play the role of interviewer so you become more comfortable speaking about yourself in front of others. Again, this is a confidence builder. The more you practice, the more confident you’ll be.
   

5. Develop your list of questions.
   

   Your interview shouldn’t be seen as some type of interrogation. It’s a “getting to know you” meeting, so feel free to ask questions. However, your first question shouldn’t be “How much do I get paid?” or “How’s the 401k plan, here?” Instead, ask questions that show you understand the job and the company’s needs. Be quick to pick up on the interviewer’s comments and ask relevant questions.
   

   Interviewer: We’ve had some issues with field reports coming in late recently. You: How are the reports transmitted? (Oh, you’re good. Very good.)
   

6. Dress for success.
   

   An interview is a performance with people playing different roles. Your role is successful job prospect. Play the part. Whether you’re female or male, the conservative business suit is the recommended attire for any interview. If your business suit needs a pressing, send it to the dry cleaners. If you don’t own a suit (you’d be surprised at the number of us who don’t) go out and get one. It doesn’t have to be an $800 designer suit, but it should be conservative black, blue or gray.
   

7. Get cut or coiffed.
   

   You’ll have 15 minutes to make a good impression. Treat yourself to a visit to the local hair stylist. You bet looks matter. They’ll be plenty of time to show your talent once you land the job. For now, look like a success, feel like a success – be a success.
   

8. Practice positive visualization.
   

   Professional athletes do it. So do actors, yoga instructors and new age thinkers who sleep under makeshift pyramids to absorb that mystical energy. It’s called positive visualization – and it works. It really does. In the days leading up to the interview, picture yourself sitting opposite the head of HR. Picture yourself relaxed, comfortable, at the top of your game. Play that clip over and over in your mind until it becomes so familiar, it actually becomes a part of your self-image. It simply can’t be stated too often – your confidence during an interview should be obvious and genuine.
   

9. Gather your materials.
   

   The day before the interview, gather your materials and place them in a briefcase or attaché. Don’t have one? Buy one or borrow one. It’s another opportunity to project that professional image you wear so well. Bring extra copies of your resume in a manila envelop. Bring a pad and pencil to take notes. Bring a calculator (you never know). Bring your address book and copies of your business card. If you’ve been asked to provide additional information (school transcripts, e.g.) make sure you’ve got clean copies ready to hand over.
   

10. Sleep tight.
    

    You’ve done it all. You’ve prepared yourself; you’ve built your confidence so you can look the interviewer straight in the eye. You are ready to rock ‘n’ roll! Okay, too psyched. You’ll never get to sleep. The night before the interview, go to bed early. Have some warm milk, coco or herbal tea (stay away from the 3rd scotch). Relax. Set the alarm and sleep comfortably in the knowledge that you’re as prepared as you’ll ever be. No, not every interview will be a success. You won’t get the job every time – but don’t take it personally. It’s not about you; it’s about the needs of the company. However, you can increase the chances of success by presenting a professional, prepared, and confident you to the interviewer. That’s how you turn an interview into a job offer.
    

You’re hired!

- Teena Rose

Well over the last few weeks I have be busy working on a workshop on how to Backup and Restore your database. I cannot tell you how much respect I now have for people who write the classes from square one. There is a ton of time here. As part of my workshop I described some methods to get around restoring a database. Things we covered were moving data from a warm stand by database such in the case of T-log Shipping and such. What I really found to be of great interest was the section that I did on DBCC CheckDB with the allow data loss options.

Well the only way to show how this works is to corrupt a database. I have never done that, well I never did it on purpose. I remember back in the 6.5 days of SQL Server corrupting them all the time, however never intentionally. How did I do it? Well it really was not as hard as I thought it was, I found a blog entry that helped me identify page numbers that a index was on. The blog that I was looking at referred to Kalen Delany’s books on how he was able to find those page numbers. But once I had the page numbers it was not difficult at all. I downloaded a Hex Editor Did a search for the page number and started to replace the values in the opened .mdf file. Once I completed that I restarted my SQL Server did a DBCC and the database was Corrupt.

This worked as a great tool for allowing me to demo how to get around such a problem. And a problem that I have seen before, I cannot tell you how many corrupt indexes I have seen and a DBA’s that I was working with would want to restore the database.

If you are interested in attending the Workshop on a Deep Dive in SQL Server 911 Backup’s and Restores. You can register here. The workshop lasts 4 hours and 37 minutes without breaks. It takes place this Friday on June 5^th. I will be in the chat room to answer as many questions as I can.

I finished up filming the video for the SSWUG.Org SQL Server 911 Backup and Restore workshop. Once we were done we filmed a little commercial for it. However, we decided to see if we could have a little fun with it. Check it out and let me know what you think. If I can figure out how to get it embedded in the blog you can find the video here: http://www.youtube.com/watch?v=im2Lq_9eGcA

I just find this funny, and it was fun to do.