Imagine for a moment if you will. As a DBA, and as the protector of your organization's data, you have implemented many safeguards to protect your data. You have set up periodic jobs to back up your databases; you check daily to ensure that the backups were actually taken; and you periodically perform test restores to ensure your backups work. In addition, you have established an appropriate backup retention policy and you store backups offsite. With all of this planning and hard work, you are confident that your organization's data is safe. But is it?

What would happen if your backups, in transit from the data center to the offsite storage, were misplaced or stolen? Or what would happen if the backups at the offsite storage location were stolen? Sound unlikely? Not really. There have been many reported instances of backups being misplaced and stolen. In fact, I personally know of a multi-billion dollar company that sends their backup tapes to their offsite location using an employee's car, then stores them in a locked, but very cheap metal cabinet that could be broken into in seconds with a crowbar. What would be the organization's liability if their data was stolen? I'm even afraid to think about it.

Although it is unlikely that your backups will be misplaced or stolen, I personally don't want to take the risk that this might happen to the backups I am responsible for. As you probably know, by default, data from a SQL Server database backup can easily be restored to any other computer and the data viewed. The exception to this is if the data has been encrypted, which is the exception rather than the rule.

In SQL Server 2008, Transparent Data Encryption (TDE) was introduced in the Enterprise Edition of SQL Server. This feature allows data at rest (such as backups) to be fully encrypted and protected should a backup be misplaced or stolen. If you are using SQL Server 2008 Enterprise Edition, I recommend you take a look at TDE and consider implementing it.

But what if your company doesn't use the Enterprise Edition of SQL Server 2008, how do you protect your backups from prying eyes? Currently, your only realistic choice is to use a third-party backup compression program that offers data encryption as a feature (which virtually all do). This way, your backups, wherever they are located, will be protected and you can rest assured that your organization's data won't be compromised.

So my first question to you is this, do you think backup encryption is as important as I think it is? And second, how do you go about protecting your backups? Do you encrypt them, do you use some other form of backup protection, or are you crossing your fingers, hoping that you never face the situation of missing or stolen backups?

I have spoken at many conferences over the years, including the PASS Community Summit and SQL Server Connections, and one of the things I have noticed is that there is very little overlap between the DBAs and developers who attend each of these conferences. There seems to be a group who likes to attend the PASS Community Summit, and another group who likes to attend the SQL Server Connections conference.

In the past, and still today, SQLServerCentral.Com is a strong supporter of the PASS Community Summit. But because of the lack of overlap between these two conferences, we feel that we have been missing out on supporting those DBA and developers who choose to attend the SQL Server Connections conference. Because it is our goal at SQLServerCentral.Com is to be as inclusive as possible, SQLServerCentral.Com has now teamed up with SQL Server Connections to present our own SQL Server track at the conference. This will give us the opportunity to reach out to an entirely different group of DBAs and developers who we don't normally interact with.

If you are not familiar with SQL Server Connections, it is part of a larger conference called DevConnections that is put on twice a year by Penton Media (they same people who publish SQL Server Magazine.) The annual spring event is held in Orlando, FL, and the annual fall event is held in Las Vegas.

The umbrella DevConnections conference include multiple, simultaneous break-out conferences, which include ASP.NET Connections, SharePoint Connections, Visual Studio & .NET Connections, and of course, SQL Server Connections. When you sign up for one event, you can attend any of the sessions among these concurrent conferences, which give attendees a rich learning experience.

The next SQL Server Connections is going to be held November 9-12, 2009, at the Mandalay Bay Hotel and Conference Center in Las Vegas, NV, and will follow this schedule:

Monday, November 9, 2009: Two SQL Server pre-conference workshops:

• Advanced T-SQL for SQL Server 2005 and 2008 with Itzik Ben-Gan
• SQL Server 2005/2008 Database Maintenance Best Practices with Kimberly L. Tripp and Paul S. Randal

Tuesday, November 10, 2009: Microsoft Day:

• There will be three different tracks (DBA, DEV, BI), all presented by members of the Microsoft SQL Server Product Team

Wednesday & Thursday, November 11-12 2009: SQL Server Connections and SQLServerCentral.Com Tracks

• There will be three DBA tracks that are managed by Paul S. Randal and Kimberly L. Tripp, which includes a wide variety of speakers.
• There will be a single SQLServerCentral.Com track, that is managed by Brad M. McGehee, which includes five different speakers.
• Attendees will be able to attend any of the sessions in these four concurrent tracks.

Friday, November 13, 2009: One SQL Server post-conference workshop:

• SQL Server 2005/2008 Indexing for Performance with Kimberly L. Tripp

For a list of all the speakers, you can visit this webpage, and for a list of all the sessions, you can visit this webpage.

The SQLServerCentral.Com track includes five speakers presenting a total of nine different sessions. If you recognize any of the speakers, that is because you have probably seen their contributions to the SQLServerCentral.Com and Simple-Talk websites. They include:

Joe Celko	Joe Celko served 10 years on the ANSI/ISO SQL Standards Committee and contributed to the SQL-89 and SQL-92 Standards. He has written over 800 columns in the computer trade and academic press, mostly dealing with data and databases. He is author of seven books on SQL for Morgan-Kaufmann: SQL FOR SMARTIES (1995, second edition 1999, third edition 2005), SQL PUZZLES & ANSWERS (1997), DATA & DATABASES (1999) and TREES & HIERARCHIES IN SQL (2004), SQL PROGRAMMING STYLE (2005) and ANALYTICS & OLAP IN SQL (2005) and THINKING IN SETS (2008). Joe will be presenting two session: Darling, Your SQL is Sooo Last Season! and Naming and Modeling Data Objects.
Grant Fritchey	Grant Fritchey, Microsoft SQL Server MVP, works for an industry-leading engineering and insurance company as a principal DBA. He's done development of large-scale applications in languages such as Visual Basic, C#, and Java, and has worked with SQL Server since version 6.0. Grant spends a lot of time involved in the SQL Server community, including speaking, blogging, and he is an active participant in the SQLServerCentral.Com forums. He is the author of SQL Server Execution Plans (Simple Talk Publishing, 2008) and SQL Server Query Performance Tuning Distilled (Apress, 2008). Grant will be presenting two session: Scouting Out Execution Plans and MUQT: More Unnecessary Query Tuning.
K. Brian Kelley	Brian is a SQL Server author, columnist, and Microsoft MVP, focusing primarily on SQL Server security and administration. He currently serves as a database administrator / architect for a large bank where he can concentrate on his passion: SQL Server. He is a contributing author to How to Cheat at Securing SQL Server 2005 (Syngress) and Professional SQL Server 2008 Administration (Wrox). In the technical community, Brian is president of the Midlands PASS Chapter. Not only is Brian an active blogger at SQLServerCentral.Com, he is a prolific forum participant and is one of the top forum posters on the website. Brian will be presenting two sessions: Keeping on Top of Your SQL Server Using Dynamic Management Objects and Catalog Views and Best Practices in SQL Server 2008 Configuration Management.
Steve Jones	Steve Jones, Microsoft SQL Server MVP, is the founder and editor of SQLServerCentral.Com. He has been working with SQL Server for 18 years as a DBA at a variety of large and small companies. He is a frequent speaker at user groups and SQL Server conferences and has written hundreds of articles on SQL Server. He is well known for his prolific blogging, editorials, and podcasts at SQLServerCentral.Com. Steve will be making one presentation: The Modern Resume: Building Your Brand.
Brad M. McGehee	Brad M. McGehee is an MCSE+I, MCSD, and MCT (former) with a Bachelors degree in Economics and an MBA. Currently the Director of DBA Education for Red Gate Software, Brad is an accomplished Microsoft SQL Server MVP with over 14 years of SQL Server experience, over six years of training experience, and has been involved in the industry since 1982. Brad is a frequent speaker at SQL PASS, European PASS, SQL Connections, SQLTeach, SQLBits, SQL Saturdays, TechFests, Code Camps, SQL Server user groups, and other industry seminars. Brad is the author or co-author of more than 14 technical books and over 100 published articles. His most recent books include, How to Become an Exceptional DBA, Brad's Sure Guide to SQL Server 2008: The Top Ten New Features for DBAs, and Mastering SQL Server Profiler. Brad will be presenting two sessions: Optimizing tempdb Performance and Free Software for SQL Server DBAs.

In the months ahead, I will be doing interviews with all of these speakers so that you will get the opportunity to learn a little more about them.

If you have been procrastinating about submitting a speaking abstract for the 2009 PASS Community Summit, you have been given a short reprieve. The Call for Speakers has now been extended until midnight on April 24, 2009. See this link for more details: www.sqlpass.org/Community/SpeakerResource.aspx.

For a book project I am working on, I have started compiling a list of reasons why heaps aren't usually a good choice when designing a database. Now, I didn't say that heaps are always bad, but in most cases, I think they should be avoided (read the list to see why).

As I compiled the list, in some cases I have had the opportunity to verify that they are true, but in other cases, I have not had the time to verify them. I would like your input on the list. Is there anything on the list that is not true, or only partially true (under some circumstances, but not others), and what other reason are there to avoid using heaps that have I left out?

I look forward to your feedback.

1. If non-clustered indexes are not added to a heap, then all queries against a heap will require table scans to retrieve the requested data. If the heap is large, then these queries will be very resource intensive and hurt SQL Server's overall performance.
2. Since the data in a heap is unordered, performing a table scan on a heap can cause a lot of extra I/O activity because inefficient random reads, not efficient sequential reads, are more the norm.
3. While a non-clustered index can be added to a heap to speed up some queries, when the non-clustered index is non-covering, the use of a RID bookmark lookup is required. A RID lookup means that once the record(s) to be returned by the query are identified in the non-clustered index, additional reads (the RID bookmark lookup) must be made of the related rows in the heap, so that all of the data requested by the query is returned. This is not very I/O efficient, especially if many rows are returned. At some point, it may be faster for SQL Server to do a table scan than it is to use a non-clustered index when returning many rows. On the other hand, if the non-clustered index is covering, then the non-clustered can be used to immediately return the data to the user without having to lookup anything in the heap.
4. Heaps cannot be replicated using SQL Server replication.
5. If you want to create an XML index on an XML data column, a clustered index must exist on the table.
6. If you want to create a spatial index on a spatial data column (GEOMETRY or GEOGRAPHY), a clustered index must exist on that table.
7. If a heap has a non-clustered index on it (as the primary key), and data is inserted into the table, two writes have to occur. One write for inserting the row, and one write for updating the non-clustered index. On the other hand, if a table has a clustered index as the primary key, inserts take only one write, not two writes. This is because a clustered index, and its data, are one in the same. Because of this, it is faster to insert rows into a table with a clustered index as the primary key than it is to insert the same data into a heap that has a non-clustered index as its primary key. This is true whether or not the primary key is monotonically increasing or not.
8. When data is updated in a heap, and the updated row is larger than the old row and can't fit into the old space, a forwarding record is inserted into the original location that points to the new location of the page. If this happens a lot, then there is a lot of space wasted in a database maintaining the forwarding records. This also contributes to additional I/O activity as both the pointer, and the row, have to be read.
9. Even if data updated in a heap is not larger than the old row (the updated data is smaller or the same size than the original data), updating a heap with a non-clustered primary key is slower than updating the same table that has a clustered index as the primary key. This is because updating a table with a clustered index is less write intensive than updating a heap with a non-clustered index as its primary key.
10. If a row is deleted from a heap with a non-clustered index as its primary key, it is slower than deleting the same row from the same table with a clustered index as its primary key. This is because it takes more I/O to perform this task on a heap than on a clustered index.
11. When data is deleted from a heap, the data on the page is not compressed (reclaimed). And should all of the rows of a heap page are deleted, often the entire page cannot be reclaimed. This not only wastes space, it contributes to fragmentation of the data pages within a database.
12. If you take two identical tables, one that is a heap with a non-clustered index as its primary key, and a table that has a clustered index as its primary key, the heap with the non-clustered index will be substantially larger, wasting valuable space and increasing disk I/O.
13. The ALTER INDEX rebuild and reorganize options cannot be used to defragment and reclaim space in a heap (but they can used to defragment non-clustered indexes on a heap). If you want to defragment a heap in SQL Server 2005, you have three options: 1) create a clustered index on the heap, then drop the clustered index; 2) Use SELECT INTO to copy the old table to a new table; or 3) use BCP or SSIS to move the data from the old table to a new table.

Share this post :

In this article, we examine the various ingredients that will help you establish a successful career as a DBA, and then contribute to your long-term career success.

• Formal Education – you don't need a degree in database administration, but a solid computer technology background will help
• Getting Experience – getting experience as a new DBA can be tough, but it can be done
• Technical skills – sound knowledge of SQL Server is not enough on its own, the DBA needs to understand the underlying operating system and hardware, as well as the productivity tools that are available to them
• Soft Skills – the DBA needs to supplement sound technical skills with excellent teamwork, time management, writing skills, and more.

Where Does Formal Education Fit In?

I frequently get asked whether or not you need a formal degree to become a DBA. While having a formal degree is not mandatory for becoming a successful DBA, it is a great start. Let’s start this discussion talking about higher education opportunities.

Very few universities offer an Associates, Bachelors, or Masters degree in database administration. Those that do tend to be on-line schools, or technical schools, not the typical university most students attend. I believe the reason for the lack of database administration degrees in most schools is twofold. First, the market for database administrators is smaller than most other educational markets. Second, very few people come out of high (secondary) school wanting to become a database administrator. In a perfect world, a degree in database administration would be an ideal platform from which to embark on a DBA career. The reality is that there are few of these educational opportunities available.

Therefore, the most common approach people take to prepare for a career as a database administrator (either through foresight or dumb luck) is to get a degree in Computer Science or Management Information Systems, which includes database-specific courses. In fact, when many people attend a university to attain one of these degrees, they are not even aware that the career of DBA even exists, and first discover databases when taking database theory classes as part of their degree program. Such a degree provides a rounded education in computer technology and provides a great foundation for becoming a DBA.

The truth is that most people don’t go to college to become a database administrator, or even work in the technology field, so they get Bachelors degrees in other subjects, ranging anywhere from English to Business, or from Art to Math. It is not until after they enter the workforce that they realize they are interested in computer technology, or becoming a database professional.

Many people wind up as database administrators through a set of often-random circumstances. Many DBAs don’t have degrees in computer technology, and I am one of them. I have a Bachelors degree in both Economics and Business Administration, and a Masters Degree in Business Administration.

When I was getting my Bachelor degrees, personal computers were just becoming available. In fact, the original IBM PC became available about six months after I graduated. I bought one of the first IBM PCs and became captivated with the possibilities it offered. Shortly thereafter, I had the opportunity to become a computer salesperson and trainer (an odd combination indeed) at a newly opened computer store, one of the first computer stores opened in the United States. I got the job because I owned an IBM PC, which was a rare tool for most people to own at that time, and because I had taught some BASIC programming classes at a local community college.

From that first computer-related job, I began writing about computer technology, and have had a wide range of computer-related jobs over the years, ranging from application development, software support, network administration, full-time trainer, and finally database administrator. Virtually all of my computer training was self-taught, especially in the early days when computer instructors were rare. Later, I did take some week-long training classes, but most of my training was, and still is, self-taught.

While a bachelors degree in a non-computer technology field may not be as ideal a foundation as having a degree in a computer technology, it can still provide a rounded education that people can leverage to reach whatever goals that interest them. My degrees in Economics and Business Administration actually helped my computer career a lot. As I had a good understanding of accounting and how businesses worked, I was much better equipped to work in the real world than most newly minted programmers just coming out of college who had little or no experience in how businesses operated.

Now, let’s talk a little about what employers expect when it comes to formal education. Whether we agree or not, a Bachelors degree is becoming the minimum educational credential for most any type of professional job. Many companies won’t even consider someone for a job unless they have at least four years of higher education. It's a fine line though: a two-year degree is generally not considered an adequate substitute for a four-year degree, but a Masters degree can often make a person seem to be over-educated for most jobs (unless the job specifically requires a Masters degree as the minimum educational requirement). This makes the standard four-year Bachelors degree the best route for most people. I only got my Master’s degree because I wanted to be able to teach at the college level, and this requires a Master’s degree at the very minimum.

If you look at job-wanted ads for database professionals, you will find that most employers want someone who has a four-year computer technology degree, or equivalent. In other words, they prefer someone who has a computer technology education, but they are willing to accept someone with any four-year degree if they meet the other skills and experience required by the position.

So, in order to have the best job opportunities open to you, as a DBA, you should have a four-year degree. A computer technology-related degree is preferred, but not essential. If you are starting out in your career, and want to become a database professional, the more closely aligned your education is to computer technology, the easier it will be to find related jobs.

How about those people who don’t have a four-year degree? Is it possible for them to become database professionals? Yes, but it is tougher. I know DBAs who have not attended a university, or perhaps attended for a while, but never attained a degree. These people often start with companies in a low-level computer technology job, such as working the help desk. Then, through self-study, on-the-job training, and experience, they eventually move into the DBA role.

Most of these individuals stay with a single company as they develop their skills. Once they have developed a lot of experience as a DBA, they can move to other companies, who are willing to waive the four-year degree minimum requirement in return for the hands-on experience that they offer. Of course, some companies won’t waive this requirement, and so certain job opportunities will remain closed to non-degree candidates.

Up until this point, we have been considering formal university training at the beginning of one’s career. What if you already have an IT career, but want to switch to become a database professional? For example, maybe you are a developer who wants to stop writing code and focus on database administration. How does formal education fit into this scenario? If you already have a computer technology-related degree, you are in good shape. All you need to is gain specific database-related skills and experience. If you have a non-technology-related degree, and you have lots of technology experience (say you have been a network administrator for three years or more), you are also in good shape for making the transition, if you attain the necessary DBA skills.

If you don’t have a technology-related degree, or technology-related work experience, then changing careers to become a database professional is more problematic. In this regard, it is as if you are starting from scratch. You might want to consider going back to school (part- or full-time) to get a degree in computer technology or database administration (where available). If you already have a degree, getting a second degree should be much faster.

While a good and relevant formal education is an excellent first step to becoming a successful DBA, it is just a start. Universities generally only cover database theory, not specific database skills. Because of this, you will need additional technical skills to pursue a DBA career. In the next section, we learn what those skills are, and how to attain them.

Getting Experience

In almost every job ad you see for a DBA, experience is required. So how do you get your first job as a DBA if you don’t have any experience as a DBA, and how can you get experience as a DBA if you can’t get a job as a DBA in the first place? Most new job seekers face this same dilemma, especially if they are looking for professional-caliber jobs. So what do you do?

One option is to apply for DBA jobs that don’t require experience. If you have training as a DBA, and have a degree or certification to verify your credentials, then some companies will hire you. DBAs are in such great demand now that some companies hire DBAs without experience. If the company is large, they may even offer a training program to get you started out right.

While getting hired without experience is great if you can find such a job, most DBA jobs require experience as a DBA. The fact is that most people who become new DBAs are promoted to that position from another position within the company they currently work for. In other words, they have been working for a company for some time in some computer-related position, have a good track record, and have expressed an interest in becoming a DBA. Oftentimes, if a company cannot find an experienced DBA to fill a position, they will recruit from within, and train the person for the job. That is what I did, along with many of the DBAs I know.

However, what if you are working for a company that doesn’t have a DBA position open? Or maybe the company is too small to need a full-time DBA. What do you do then? One option would be to identify any DBA-type work done within your current company and volunteer to do it as part of your regular job. This will start getting you hands-on DBA experience, even if it is only on a part-time basis. If your current job does not afford you the opportunity to gain any DBA experience, you may have to consider changing jobs, and finding a company where DBA opportunities exist. It is either this option, or trying to find a job that will hire a DBA without experience.

What if you can’t change jobs right now, and don’t have any opportunities to get any practical DBA experience? At this point, you are running out of options. You might contact non-profit organizations and volunteer your services, or you might attend a local SQL Server user’s group and ask the members for their suggestions on how you can get experience in your local area.

However you gain your DBA experience, you will find that it is the most important asset you can have.

Mastering DBA Technical Skills

Even if you were to graduate from a university with a Masters degree in database administration, you won’t be prepared for the day-to-day work as a DBA. Learning the practical side of being a DBA takes additional technical knowledge and a lot of practical experience. In this section, we take a broad look at the specific kinds of technical skills you need to become a DBA, along with suggestions on how to attain them.

Obtaining Specialized Database Skills

As we discussed earlier in the book, it is virtually impossible for anyone to know everything there is to know about databases. Because of this, I suggested that you specialize in an area that interests you. This might be DBA System Administration, DBA Database Designer, DBA Development, DBA Business Intelligence, among others.

The key to becoming a DBA is to select a specialty, and then master all the technical information related to it. For example, if you want to become a DBA System Administrator, you need to learn about how the database engine works, how to perform routine maintenance tasks, how to performance tune, how to troubleshoot problems, and so on. Pick whatever DBA specialty interests you, and make it a point to master it, inside and out. If you don’t know what specialty to pick, I recommend you start as a DBA System Administrator. As you begin to master these skills, you will also be learning about the other specialties, and you can always change specialties when the option arises.

Understanding Hardware

Not only are most DBAs expert in their chosen SQL Server specialty, they are also very knowledgeable about the physical computer hardware on which SQL Server runs. Getting the best performance and scalability out of SQL Server requires DBAs to know how to select the optimum hardware for their SQL Server. In addition, hardware skills are necessary for knowing how to best configure the hardware, along with how to diagnose and troubleshoot hardware-related problems. DBAs usually don’t depend on others to figure out problems with their servers.

Knowing the Operating System

Another critical component the DBA needs to understand is the operating system. It is fully intertwined with SQL Server and the physical hardware, and can’t be separated. The DBA needs to know how to install it, configure it, manage it, and troubleshoot it. Many problems that are associated with SQL Server are operating-system related, and the DBA needs to understand its intricacies in order to resolve them.

Mastering Tools

Whatever database specialty you choose, you will have both built-in and third-party tools available to help you do your job and be more productive. In my experience, many DBAs don’t take the time to learn how to master the tools available to them. This means they end up being less proficient and productive at their work.

Not only do most DBAs master all the tools included with SQL Server, they also learn about related third-party tools that can help him become more productive. This means they often are downloading new tools, and trying them out, seeing if they help them do a better job.

Adopting SQL Server Best Practices

In addition to the raw technical knowledge that a DBA requires, in order to know how to perform specific tasks with SQL Server, there is an additional layer of knowledge DBAs must know, and that is SQL Server Best Practices. As a DBA, you are often many faced with many different ways to perform the same task. Some of the options are better than others, especially if you factor in the requirements of a specific situation. Best Practices refers to the best way to perform a specific task, given the circumstances you are facing. For example, there are different ways to back up and restore databases. The best way to do this often depends on the situation.

Unfortunately, most SQL Server Best Practices have not been codified anywhere. Instead, you have to search them out from books, articles, and websites. In other cases, you have to learn them by trial and error. Many DBAs often develop their own set of Best Practices and use them in their day to day work, helping not only to bring consistency to their work, but also to help perform their job better and more efficiently.

How to Obtain DBA Technical Skills

As you can see, DBAs need to have a wide variety of technical skills. So how does the DBA attain them? It really comes down to time, both time for learning and time for gaining experience. As mentioned earlier, these are many technical skills required that you won’t generally learn from a university. Instead, they are skills that are acquired in many different ways. Most DBAs master technical skills by using one or more of the methods detailed below.

Most DBAs will probably use all of these training methods at one time or another. You may find that some are better suited to you than others. It really doesn’t make much difference which option you choose, as long as you take the time to learn. Mastering the technical skills to become a DBA is your responsibility. In other words, you have to design your own education program. Nobody is going to do it for you. You need to decide what you need to know to meet the educational needs of your DBA specialty, and decide how you are going to acquire those skills.

Formal Classroom Training

Formal classroom training is offered by corporate training companies, and some colleges and universities (usually non-credit), and is one of the fastest ways to master multiple technical skills, including SQL Server, hardware, and the operating system. Many of these classes are called certification classes because the assumption is that once you take the class then you should be ready to take the related certification test, assuming you want to become certified. While these can be expensive, they are an effective way to learn a lot of information very quickly, especially if the subject matter is new to you.

Seminars and Workshops

These are training sessions that last one day, or less, and focus on a very specific topic. Generally speaking, these are best for people who already have some background in the subject matter and are looking for more in-depth knowledge of a particular subject.

Conferences

Conferences encompass many different learning formats, including formal classroom training, half-day and one-day workshops, short (60-90 minute) seminars, hands-on training labs, and general sessions. They even offer opportunities to ask database experts specific questions about any topic you want to learn more about, on a one-on-one basis. If you are a new DBA, conferences can be a little overwhelming, but educational. In many cases, you will see experienced DBAs attending conferences not only to learn something new, but to network and make new connections.

On-Line Training

Learning over the Internet is becoming more and more common, but the cost and the quality of the learning varies substantially. In some cases, you can take free lessons that range from average to exceptional in quality, and in other cases you can pay a lot of money for mediocre to exceptional training. If you are paying a lot of money for on-line training, be sure you carefully check out the company first before you send them your money.

Self-Study Booking Learning

One of the most popular ways to master SQL Server technical skills is to read books. There are books on virtually every topic and at most every learning level. Books allow you to choose when you learn, but on the other hand, you have to be disciplined enough to take book learning seriously if you want to get the most out of your time.

Magazines and other Publications

There are few technical magazines or publications that focus on SQL Server, or databases for that matter. Of those that are available, they are most useful for keeping up with SQL Server news and third-party products, but they are not always the best way to learn new skills.

Websites, Blogs, News, RSS Feeds

By contrast, there are many different websites and blogs devoted to SQL Server. Unfortunately, the quality of the content varies widely, and much of it can be out of date. This means that you may have to spend a little extra time searching for SQL Server-related websites and articles that cover the specific material you want to master. Many DBAs consider this type of learning as “just-in-time” learning. In other words, if you need to learn a specific skill or task very quickly, then the Internet is often the quickest way to find the content and to learn it.

On the Job Training Opportunities

If you work for a larger organization, they may offer on-the-job learning opportunities, including formal instruction and mentoring. If you have these options available, you will want to take advantage of them.

Mastering DBA Soft Skills

If you want to become a successful DBA, not only do you need exceptional technical skills, you also need to master many soft skills. Yes, I know what you are thinking. You are thinking that if you are a technical wiz, you don’t need soft skills. Unfortunately, that’s not the case.

Following is a description of the numerous types of soft skills that the DBAs should master.

People Skills

While this phrase may be overused, it is overused with much justification. While DBAs may find themselves working alone more than other professionals do, they still need to work with others. This includes talking with end-users, developers, IT professional, and managers. If you don’t get along well with others, you will severely reduce your chances of becoming a successful DBA, or even of having a long career as a DBA.

If you don’t naturally have people skills, learning them can be difficult, but you do have some options available to you. You might consider reading books on people skills, taking classes or seminars, or even individual counseling. While people skills may be hard to learn, learning them will pay off for your entire life.

Teamwork Skills

I consider teamwork skills a little different from people skills, although there is a lot of overlap. People skills are about getting along well with others. Teamwork skills are learning how to work well with others. Many times, you find yourself in a team of people that you did not pick, and would not pick if you had a choice. Teamwork skills are learning how to work effectively in a team, even if you don’t like each other!

As a part of a team, you might be the leader (also requiring leadership and project management skills), or you may be a contributor, who is assigned a task that needs to be completed. Whatever role you fall in, you need to participate and work together as a team to accomplish the task successfully and on schedule.

If you have difficulty with teamwork skills then, first, be sure you have good people skills. Once you have accomplished this, then focus on building teamwork skills. There are many books and seminars available on building and managing teams. In fact, your organization might even offer one in-house. If so, jump at the first opportunity at taking it.

Personal Time Management Skills

Most successful DBAs have more work than they have time to accomplish it. To get everything done, the DBA needs to be effective at managing his of her time. It is very easy to just sit back and have work come to you, pile up, with much of it never getting done. Instead, you must be proactive when managing your time. Keep a schedule and assign priorities to tasks so you can ensure that what has to get done gets done, on time, and successfully. Don’t be afraid to say no to new tasks if you don’t have the time to do them right.

If you have trouble managing your own time, start small by using a schedule, making appointments for yourself to ensure work gets done. Using Microsoft Outlook, or a similar tool, is a great way to track tasks, appointments, meetings, and other things you need to accomplish. If this doesn’t work for you, there are many books and seminars available on personal time management.

Project Management

If you want to be a successful DBA, you will find yourself managing many projects, from the smallest that take a single day and just yourself to complete, to those that make take a year and many people to complete. Project Management is like personal time management, but on a much larger scale. Depending on the complexity of the project, you may spend all of your time managing it instead of actually producing any work yourself.

Project management is a skill set most people don’t naturally have. It has to be learned through training and experience. It is much more than just learning how to use Microsoft Project and creating nice-looking PERT charts. It involves managing people and other resources over time to accomplish a specific goal. While you can buy books about project management, the best way to learn it is by taking formal classes or seminars on it. Once you have learned the basics, then it is usually trial by fire when you begin your first project. Hopefully, it will be a small project that will give you the experience you need before tackling large projects.

Leadership Skills

Leadership is a hard concept to define. Essentially, it is the ability to define an objective, to clearly communicate what the objective is and why it is important to others, and then to get other people to help you reach that objective.

When many people think about leadership, they think about politicians or corporate CEOs. While they need to have good leadership skills, so does the successful DBA. In many cases, the ability to be able to clearly define goals, communicate them to others, and then get others to work toward the common goal, is a valuable skill. Leadership can come into play in meetings, teams, or large projects. You don’t have to be a manager to be a leader.

Most people don’t consider themselves leadership material. However, in many cases that person is doing themselves an injustice. Everyone has the ability to define goals, communicate them, and get other people to help attain them. Essentially, it is a matter of planning and execution, sprinkled with a lot of people skills. While you can take leadership classes, the best way to learn leadership skills is to take on the responsibilities of a leader, and get hands-on experience.

Writing Skills

As much as you might dislike writing, it is a very important skill to learn. Virtually every day, you will find yourself communicating with others in writing, whether it be an e-mail, some documentation, or a formal report. Unfortunately, writing is a skill that is poorly taught by most schools, including universities. If you realize you don’t have the skills to be a good writer (grammar, punctuation, style), then you need to take it upon yourself to learn these. This is not easy, especially if your previous schooling has been weak. Your best option is to take formal writing classes to master these skills. While you can read books and take short seminars on writing, it is hard to learn how to write well unless you get regular feedback.

Once you have learned writing basics, the next step is to develop your skill by practicing. The more you write, the better you will become. Many DBAs who want to become better writers get experience by writing articles for websites and magazines. As a beginner, you may not get paid much, or not at all. Nevertheless, and more importantly, you will get the experience and feedback that will help make you a better writer, a better communicator, and a better DBA.

Speaking Skills

We all have heard that public speaking is the most feared of all human activities. I am not sure that I fully agree with this statement, but public speaking does not come naturally to many people. Learning public speaking skills is important for the successful DBA because you will find yourself doing it, whether you plan to or not. For example, you may have to present at a meeting, teach an in-house seminar, or even find yourself talking at a user’s group meeting. What most people don’t realize about speaking is that you have to plan it, you just can’t wing it.

Like writing, I feel that the best way to learn public speaking is by taking formal training classes and/or seminars. You might also want to join a speaking club, such as Toastmasters International. Once you have the fundamentals down, then you need to practice and practice. Start practicing at work. Then practice at presenting at organizations you belong to, and so on. Start small and work yourself up to speaking to larger and larger groups, and from short sessions to longer sessions.

Knowledge of Legal Responsibilities

As DBAs, we often find ourselves involved in fulfilling legal responsibilities, such as maintaining data privacy, or archiving data for legally defined periods of time. In order to carry out the legal responsibilities of the job, you have to know what your responsibilities are. Simply claiming to be ignorant of the law won’t work. In fact, it is possible to go to jail for failing to meet your legal obligations.

The difficulty is in finding out what those legal responsibilities are, as they vary from industry to industry, state to state, and country to country. Because you are not an attorney, and because your manager is not an attorney, it is important that you ask the upper management of your organization to specifically define what your legal responsibilities are.

Starting Honing Your Skills Today (and don't stop)

As we have learned in this article, becoming a successful DBA is more than just knowing a lot about SQL Server. It includes knowing about hardware, the operating system, best practices, leadership, time management, communication skills, and much more. This may seem like a lot of material to master. And it is. Nobody can be expected to master all of this in a short time period. Instead, it is accomplished over time.

If you find that you come up short in some of these critical knowledge areas, start today by picking out one or two of them and start working on them, and work on them every day until you master them. Only through perseverance and hard work will you become a successful DBA.

Being a DBA is not a static career. It changes all the time. While the soft skills you need may not change over time, your technical skills will have to be constantly refreshed as hardware, the operating system, and SQL Server evolves over time.

The successful DBA is lifelong learner, and makes learning a regular part of his or her regular activities. Some DBAs make it a point to read books, magazines, or web-based content on a daily basis, while others prefer to attend formal training or conferences. It doesn’t matter how you continue your learning, as long as you keep it up on a regular basis.

Share this post :

While you may not think of it this way, the impression you create on other people within your organization significantly affects your success as an IT Professional. In other words, how the people you work with view you as a person can make all the difference between you being an average IT Professional and being a successful IT Professional.

I've worked with IT Professionals of wide-ranging ability and attitude. I've worked with people who always show up to work on time, don’t mind staying late if they have to, constantly work hard to keep up with the ever-changing world of technology, and always follow through with whatever they promise to do. Conversely, I've also worked with IT Professionals who come to work late, create a big scene if they have to stay late, know more about DOS than anyone else in the company, and can’t be depended upon to follow-through with tasks that are assigned to them.

Which of these two types of IT Professionals would you prefer to work with? Which of these IT Professionals has the potential to be a successful IT Professional? In this case, the answer is obvious. Most people, however, fall within these two extremes of behavior, standing out neither as an outstanding IT Professional, nor as an IT Professional you'd cross the building to avoid. In this article, we will explore some of the habits and attitudes that will help you develop a good reputation wherever you work, and move you towards the "outstanding and successful IT Professional" end of the scale.

Developing Your Brand Within Your Own Organization

If you want to succeed as an IT Professional, then you need the help of others. One of the best ways to get this help is to create a positive, personal image (brand, if you will) within your organization. People tend to be drawn to “positive” people and to want to help them. This is, in my opinion, one of the most important things you can learn if you want to be successful in your career.

In other words, if you want to be an outstanding IT Professional, you need to manage your internal brand in such a way as to present yourself in the best possible light. This does not mean faking characteristics in order to manipulate people. It does mean working hard, being honest and realistic about what you can and can't achieve, and generally adopting habits and attitudes that will help you work well with other people, and make them willing to help you.

So, how do you set about achieving this? The following advice is designed to get you focused on some of the things you can do differently in order to improve your own personal brand within your organization.

Focus on Business Goals

How many times have you heard something like the following, from a co-worker?

“Why did management cut our budget? We don’t even have enough resources now to do our job.”

I have heard similar comments from co-workers at virtually every job I have ever had. When a decision, such as a budget cut, affects you directly, it is natural to accuse upper management of not knowing what they are doing. Of course, if they had any clue about what was going on, they would increase your budget instead of reducing it, right?

In some cases, your assumption may be right. Upper management doesn’t always make the right decisions. On the other hand, if all managers were stupid, then most businesses would fail and the economy would sink. However, this is not the case. Many businesses adapt successfully to changing market conditions, even if it means that difficult and unpopular decisions need to be made along the way. Over the long term, these businesses continue to thrive, producing more profits, adding more jobs, and generally helping the economy.

So what’s my point? My point is that, as an IT Professional, you might not be privy to all the reasons why your organization’s leaders make the decisions they make. For example, maybe the reason they are cutting your budget is to prevent layoffs. Alternatively, it may allow dollars to be freed up that can be invested in a new market that may be more profitable than your organization's current market. In other words, what you may perceive as a foolish decision may actually be a great decision.

What does this mean to you? As an IT Professional, your focus should be on understanding the true business goals of your organization, and helping it meet them. It is too easy to focus only on what you think the organization should be doing, or on the goals that are most attractive from your own team's point of view.

If you are facing a budget cut, don’t complain or whine to others. Instead, focus on how you can get the most out of the budget you do have. If you are not clear on your organization’s business goals, or why they have changed, then ask for an explanation. If you can build a very strong case that not cutting the budget is better for the organization than cutting, then by all means make it. Just because you agree to focus your efforts on helping your organization achieve its overall business goals, it doesn’t mean you are a "yes" person.

There are exceptions to this advice of course. If you find you work for a company of foolish managers, then I would suggest you start looking for a new job now, as the odds of the organization surviving long term are not great.

Be a Leader, Take the Initiative

Many organizations are leadership wastelands. Nobody wants to take the lead or make critical decisions. Nobody wants to stand out, be a little different and move out of their comfort zone. People often avoid taking the initiative, either because they are scared of failure, or because it might involve too much work, or because they think that their peers may think of them as some sort of company suck-up. For these reasons, and others, many people actively avoid doing anything other than what they are told to do.

I admit that I have painted a pretty terrible picture. How would any organization ever grow and succeed if everyone felt this way? Fortunately, the picture is not quite as bleak as I've suggested and, in fact, should be seen as an opportunity for the you to excel, by taking the initiative, and being a leader.

You don't have to become a manager to be a leader. You can be a leader in many different ways. Consider the following examples:

• On starting a new job, you discover that all the disaster recovery-planning documents are out of date. You immediately volunteer to get them in shape.
• No formal complaint has been made, but several users have been grumbling about the slow performance of a particular application. You take the initiative to investigate further so that the problem can be identified and corrected, before it becomes a serious issue.
• Your company is thinking about purchasing some new management software that could make your team more productive. You volunteer to evaluate the software and write up a recommendation.
• Your boss mentions a new project that is coming down the pipe, and asks for ideas on how to implement it. Rather than leave it to others, you make time to do some thinking, and research, and at the next meeting you offer your advice and suggestions.

A key element of good leadership is not waiting until you are asked. If you identify an area where you can help your organization, or help others in your organization, then take the initiative and do it. All too often, people see opportunities to help out, but don’t do so because they figure someone else will eventually fulfill the need, so why should they.

Volunteer for Hard or Undesirable Tasks

Whenever I start a new job, I take some time to figure out what jobs or tasks are critical to the success of the organization and, make sure I'm prepared for them. At the same time, however, I also identify those tasks that nobody else seems to want to do, and volunteer to do them myself.

I've found that this philosophy can provide many benefits. The most obvious is that your manager and co-workers get to see right away that you are a team player and that you don’t mind getting your hands dirty, and working hard. If you perform your work well, then people quickly learn that you can be depended upon.

Volunteering for the less popular jobs is also a good way to learn the inner workings of an organization. The more you know about how an organization works, the more you can contribute to it, and the more beneficial you become to the organization.

A less obvious benefit is that if you master undesirable tasks, along with the critical ones, then you often become the only one who can perform these tasks. This can make you invaluable to your organization, and can pay off in the long run. For example, you will unlikely be the first to leave during a lay off, and it can mean bigger raises each year.

Have a "Get It Done" Attitude

As an IT Professional, you will be faced with many problems that need to be resolved. Never avoid problems and hope they will go away; they won't. The successful IT Professional regards problems as challenges that need to be resolved now, not later. Likewise, they will never complain about a task assigned to him or her, or try to get out of it. The outstanding IT Professional simply gets the task done as quickly and as effectively as possible.

Don’t Spread Blame

In most organizations, many IT projects don’t get completed successfully, and on time. The causes of this can be many:

• Management had the wrong expectations for the project
• Not enough resources were provided
• The time line was unrealistic
• The team was not properly trained
• The project leader was incompetent

Who knows for sure? In many cases, it is probably some combination of actions or inactions that contributed toward the failure. When situations like this arise, many people start blaming others. Not only does blame not contribute to making the project a success, it can also seed long-lasting bad feeling among many different people in the company. The outstanding IT Professional realizes that spreading blame never helps, and does his or her best to make the project a success.

Accept Responsibility

There is no such thing as a perfect person. Everyone makes mistakes. The difference between average IT Professionals and successful IT Professionals is that successful IT Professionals accept that he or she is not always right, and sometimes makes mistakes. When you make a mistake, don't try to cover it up or blame others. Acknowledge it immediately and do whatever it takes to resolve it.

Help Others Be Successful

One maxim for success, both as an IT Professional, and in life generally, is this: “If you want people to help you get what you want, then you have to help other people get what they want.” I am not talking about bribing people, or even trading favors. The successful IT Professional likes to share his or her knowledge and experience, and one of the best ways to do this is to help others. When help is offered, it should done willingly, with no implication that it is a "favor,” and no expectation of a return.

If you follow the policy of helping others when they need it, you will often find out that you will get many unexpected rewards. You never know who your next manager might be, and it might be the person you helped last week.

Avoid Office Politics

Many people allow themselves to be drawn inexorably in to the mystery and intrigue of office politics. Unfortunately, it is also a great way to make enemies and cause unnecessary division within an organization.

The outstanding IT Professional keeps his or her ears open but, other than that, doesn’t participate in the office politics game. Sharing misinformation, rumors, or even false facts, is a recipe for disaster.

Downplay the Geek Factor

Let’s face it, many IT Professionals are geeks. Some take pride in their geekiness, constantly reminding others of their geek status. Other geeks don’t even admit they are geeks, but unknowingly spread their geekiness wherever they go. And then there are the geeks who know they are geeks, but try to avoid demonstrating the worse examples of geekiness. In other words, they try to fit in with non-geeks.

Geekiness doesn’t really affect how one performs the technical side of one's job, but it can have negative consequences for the "people side" of the job. Unfortunately, geeks have been stereotyped with mostly negative characteristics, such as not being people-persons, not being able to talk in a language non-geeks can understand, and for boasting about their technical knowledge.

This perception of geeks may or may not be well-founded, but it exists regardless. Whether we accept this fact or not, most people like people who are like themselves. If you are the only geek in an organization of non-geeks, it can be a rough ride.

Use Correct E-Mail Etiquette

In our high-speed, high-tech world, we are becoming more and more reliant on e-mail to communicate with others. This may not necessarily be a bad thing, but there are special considerations to using e-mail communication that don't necessarily apply to verbal, or more-formal written communications. For example:

• It is almost impossible to stop an email after you hit send, though most of us have probably wished we could at one time or another. For example, you are a little upset with your manager, or a co-worker, and you dash off a less than polite e-mail. After clicking the send button, you realize that perhaps you did not take the proper amount of time to carefully consider what you wrote, and its implications. Unfortunately, getting the e-mail back may not be possible. One collogue I work with has step up a rule in Outlook that keeps all outgoing e-mails in his outbox for five minutes before it is actually sent, just in case he has a change of heart after pressing send. If you have a tendency to firing off hasty e-mails, perhaps you should consider adding such a rule to your mail client.
• Once an e-mail has been sent, you lose control of its content. It can be forwarded to anyone, and sent anywhere. You probably don’t want your honest assessment of a junior team member shared with others in your organization. Be careful of what you send, and to who.
• If you are not careful, when selecting the "Send To" address for an e-mail, you might end up sending the wrong e-mail to the wrong person. I know one person who was looking for a new job, and sent a cover letter and resume to his current boss by mistake.
• Many people get in the habit of using e-mail for non-business purposes, such as sending jokes or photos to co-workers. This has gotten many people into unexpected trouble.

The successful IT Professional is aware of the advantages of disadvantages of using e-mail to communicate. An Internet search on “e-mail etiquette” will provide many suggestions for improving your e-mail communications.

Participate in Meetings

Whether we like it or not, we all get many invitations to meetings. In some cases, it will be as a participant, other times as a presenter, and other times as the meeting chairperson. Whichever role you play, take it seriously. As a participant, the successful IT Professional listens carefully, asks questions, and provides careful feedback. As a presenter, the successful IT Professional doesn’t wing the presentation, instead preparing for it and, if appropriate, practicing it before hand. As the meeting chairperson, the successful IT Professional only calls meetings that are beneficial for all attendees, starts the meeting on time, ends the meeting on time, uses an agenda to guide the course of the meeting, and takes notes to document any important decisions made in the meeting.

Make Presentations

Many IT professionals are called upon to make presentations. They may be for company meetings, for training sessions, user groups meetings, or even speaking at industry conferences. Before making a presentation, the outstanding IT Professional determines who the audience is, determines what the audience would like to learn from the presentation, outlines and develops the presentation, and practices the presentation before giving it to the audience.

Take Advantage of Learning Opportunities

Many organizations offer a wealth of training opportunities to their employees, covering both technical and soft skills training. This training may be conducted on-site by company trainers, or by contract trainers; it may involve attending a training center, it might be Internet-based, or it might include attending a conference. Successful IT Professionals take advantage of all the training opportunities that are available. There is no such thing as an over-trained person.

Be Internationally/Culturally Sensitive

The IT community is made up of many different people who come from many different countries and cultures. While there may be a few IT Professionals who “don’t fully embrace diversity,” most do. IT Professionals, no matter where they work, come from many different places, each bringing their unique knowledge and experience to the profession. This often requires cultural sensitivity and “bending over backward” to fully understand someone with a different upbringing than your own. While cultural differences may occasionally be the causes for differences of opinions, they are more often a great way to learn more about each other and the world.

You Can’t Be All Things to All People

There is no such thing as a perfect person, so there is no such thing as a perfect IT Professional. No matter who you are, or what you are, there will always be someone who doesn’t like you. This is a fact of life. All we can do is to do the best we can with what we have been given.

Although we are not perfect, we can still go a long way to getting along well with others by managing our own brand within our organization. If you haven’t already done so, take some time to figure out how your co-workers perceive you. You may discover that you get along well with everyone, or you may discover that you display some characteristics that some people perceive as less than ideal.

If you are not perceived the way you would like, then consider trying one or more of the suggestion in this article to help change how other’s perceive you. It might take time, but making the effort to manage your own brand, and taking the necessary time to allow changes to take effect, can be very rewarding to your career. It can make all the difference between being an average IT Professional, and an outstanding and successful IT Professional.

Share this post :

In previous blog entries, I have talked about the importance of managing your online brand. One important part of this is participation in social networking websites. If you are not yet familiar with the term, social networking refers to websites that are designed to make it easy for people to share information about themselves, and at the same time, connect with others who have similar interests.

Social network websites come in many different forms to meet the diverse needs of their members. According to Wikipedia, the 10 most popular social networking websites are:

• MySpace
• Facebook
• Windows Live Spaces
• Habbo
• hi5
• Orkut
• Friendster
• Flixster
• Classmates.com
• Bebo

While you may be familiar with some of these social networking websites, many of them may be new to you. This is because many of these top 10 sites are popular in countries other than the United States.

While social network websites can be fun and bring people with similar interests together, what role do they play for DBAs? While this list is not all inclusive, some of the benefits for DBAs joining social networking websites include:

• Finding and connecting with DBAs locally who you didn't know exist. This may be a way to find out how many DBAs are in your local area so that you can get together and perhaps start a local user's group.
• Connect with DBAs throughout the world who share common interests. For example, if you are into SSIS packages, perhaps you might want to find other DBAs who find SSIS packages as fascinating as you do.
• To keep up with your DBA friends, no matter where they are.
• To make it easy for people to find and connect with you. This can be very important if you are a consultant or are looking for a new job.
• To promote yourself and manage your online brand. Many social network websites are in effect mini-websites you can share with others who you are and what you know.

As you might imagine, some social networking websites are more applicable to DBAs than others, especially if you want to use them for self-promotion or for business-related relationships. In a recent poll on SQLServerCentral.com, DBAs were asked what social networking websites they belong to. The top 6 results included:

• LinkedIn
• Facebook
• MySpace
• Twitter
• Del.icio.us
• Plaxo

As you can see, there is not a lot of overlap between the list of the top 10 most popular social networking websites on the Internet and the top 6 used by DBAs who visit SQLServerCentral.com. I think this is because most DBAs, who do participate in social network websites, choose those that are more business-oriented, not the ones that are more social-orientated.

Personally, there are three social networking websites that I use extensively, all of which happen to be in the top 6 list above. They include LinkedIn, Plaxo, and Twitter. I want to share a little about each of these website, and why I use them.

LinkedIn

LinkedIn is a social networking website dedicated to developing professional relationships, and currently has over 25 million members. Basic membership is free, and allows you to create a profile (essentially a resume) that can be shared with the public, and also allows you to link with others who you have some direct relationship with, such as a friend or business acquaintance. LinkinIn can be used to find new clients, service providers, subject matter experts, business opportunities, connect with industry insiders, ask questions, find a new job, find a job candidate for a new position, and much more. In addition, if you use the free Xobni add-in to Microsoft Outlook, Xobni can display information from LinkedIn profiles as part of your contacts list.

I use LinkedIn because it allows you to identify new contacts from your currently existing contacts. For example, I currently have 213 direct connections in LinkedIn. This are people who I have some sort of direct relationship. But because each of my direct connections have connections of their own, I am one connection away from about 25,000 other people, and two connections away from over 2 million people. So if I want to make a contact with someone who I am not directly connected with, all I have to do is to contact one of my direct connections and ask them if they would introduce me to the person who I want to meet, and so on. This allows me access to a huge number of people with an almost infinite variety of knowledge and interests.

You can see my LinkedIn profile at:

http://www.linkedin.com/in/bradmcgehee

Plaxo

Plaxo started out as a service to help you automatically update your Outlook contacts list. For example, if a contact in my Outlook contacts list is also a Plaxo member, then if they change their contact information, then Plaxo (through an Outlook add-in) automatically update the information in my Outlook contact list. More recently, it has morphed into a business social networking website that offers many other features besides just keeping track of your contact's address and other contact information. I use Plaxo mainly for its automatic contact update feature, but I also use it for my resume (similar to LinkedIn). It is just another way that people can find me.

You can see my Plaxo profile at:

http://Brad_McGehee.myplaxo.com

Twitter

Twitter is a somewhat odd social networking website. Essentially, it is a mini-blog that allows you to enter short (up to 140 characters) entries about what you are doing. Many people use it like a public diary, sharing their daily activities. Personally, I use it to promote myself, such as when I have blogged, written a new article, or spoken at a users group. As a Twitter member, you have the ability to follow others, and others can follow you. In other words, you develop a network of people who you are interested in and want to follow, and others who want to follow you.

You can see my Twitter feed at:

http://twitter.com/bradmcgehee

Should You Join a Social Networking Website?

Is social networking something you should do as a DBA? If you aren't interested in promoting yourself or developing online contacts, or if you don't have enough time to actively engage in social networking, then not participating won't hurt your DBA career.

On the other hand, if you want to promote yourself and develop new contacts, and you have the time to participate, then do so. It's a great way to not only stay in contact with your current network of friends, it is a great way to expand that network.

If you decide to participate, the hardest part is deciding which social networking websites best meet your needs. This will depend on you, and your interests. I suggest you check out multiple social networking websites and see what they have to offer. Start with one, and if you enjoy it, then expand and join several others. Each social networking website has its own pros and cons, and the more you join and engage in, the greater your ability to manage your on-line brand.

Share this post :

After a very long wait, SQLPASS has introduced its new website (www.sqlpass.org). If you were a previous member of PASS, you should have received an e-mail with your new username and password. If you thought you were a member, but did not receive the e-mail, you will need to register again.

The website sports a new, modern look, but on the other hand, still doesn't have a lot of content. More on this later.

One of the biggest differences between the old website, and the new website, is that there is no longer the concept of free and paid membership. Now, all memberships are free, which means that everyone who belongs to SQLPASS can access all the content on the website. This is a refreshing change from the older website, where paid membership didn't really offer you much more than the free membership did.

As I mentioned earlier, there site doesn't have much content on it yet. If you go to the Learning Center, you will see the outline of many good things to come.

And this is where you can get involved. As a member of SQLPASS, you have the opportunity to contribute content to the website. As I have mentioned in past blog entries, and in my book, "How to Become an Exceptional DBA," contributing to the greater SQL Server community is not only a great way to become recognized for your skills, but to also share your knowledge with others. I highly recommend you take this opportunity to share you knowledge with others. Besides being fun, it also provides you with great learning opportunities.

The events page on the website is especially useful. It lists the many various local and national SQL Server events that are available. This is a great way to discover events that may be happening close to where you live.

Besides the event page, there is a web page devoted to all of the local SQLPASS-affiliated chapters.

The sample above doesn't show very much, but the page lists many, many user groups from all over the world. If you aren't a member of a SQL Server users group, now is the time to join. If your area doesn't already have a user's group, start your own. SQLPASS offers a startup kit if you want to take the initiative and start a group.

This is just a small sampling of what the new SQLPASS website offers. Check it out today.

Share this post :