THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is CSO of Linchpin People and SQLPeople, an SSIS Trainer, Consultant, and developer; a Business Intelligence Markup Language (Biml) developer; SQL Server database and data warehouse developer, community mentor, engineer, and farmer. He is a co-author of SQL Server Integration Services Design Patterns and Managing Geeks - A Journey of Leading by Doing, and author of the Stairway to Integration Services.

  • Getting Started with SSIS: Renaming Your First Package

    When you create an SSIS Project using SQL Server Data Tools – Business Intelligence (SSDT-BI), a new, empty SSIS package is added to the project. It is named “Package.dtsx.” One of the first things you want to do is rename this package, providing a more descriptive and more unique name. To rename the package, right-click the package name (Package.dtsx) in Solution Explorer and then click Rename.


    Solution Explorer is a treeview control. Once you click Rename, the Package.dtsx node in the treeview switches into edit mode, allowing you to edit the name of the node. The name of the package – “Package” in this case – is selected, but not the extension (“dtsx”):


    You can now type the new package name – I typed “StageTemperature”:


    When you press the Enter key, the package is renamed:


    It is possible to change the Name property of the SSIS package in the Properties Window. Do not change the Name property of the SSIS Package in the Properties Window.


    Always rename the SSIS package in the Solution Explorer using the method described above.

    Congratulations! You just renamed an SSIS package!

    Learn more:
    Linchpin People Blog: SSIS
    Stairway to Integration Services
    Test your knowledge

  • Some Thoughts on Leadership

    The purpose of leading is not to be out front. Being out front is simply where good leaders find themselves. “Front” is merely a location, it conveys no authority. And it is possible to find oneself out front and not be a leader.

    The goal of a leader should not be to serve oneself, it should be to serve others. “Which others, Andy?” I’m glad you asked. Everyone who crosses your path. This is what is meant by the terms servant leadership. It comes from an idea found in the Bible where Jesus told his disciples leaders place others ahead of themselves and serve everyone.

    Who, Not Where, You Are

    Leaders serve others. By doing so, they inspire others. You can seek leaders by searching for titles but all you will find is holders of titles who may or may not be leaders. How do you identify leaders? Search for followers. People naturally follow leaders; titles are optional.

    But Leaders Are Out Front

    Leadership is not a location, it is not a position; leadership is a role. Yes, leaders are seen as “first” by others. Part of effective leadership is correcting the misperceptions that the leader is “better.” Leaders perform a role on the team or in the organization. Expressed hierarchically, leaders are on the same level as team members performing other roles. Part of the leader’s role is to interface with outsiders and coordinate team activities and facilitate individual activities of team members. These responsibilities are often (and easily) confused with being in charge and dictating the work of the team and telling each individual what to do, but that’s not the true nature of leadership.

    Leaders either lead or they do not. If a leader chooses to not lead that doesn’t make them a non-leader, it simply means they are not exercising their gift or performing their role.

    Born or Built?

    Are leaders born to lead or trained to lead? The short answer is “yes.” Leaders are born with some of the skills and talents of a leader. Leaders learn how to apply their skills and gain experience over time. Some leaders are born with more and some learn more, but all are born with some skill and learn from there. In either case, leadership grows.


    Some see the desire to lead as an automatic disqualifier for leadership – especially servant leadership. I disagree. I think desire is not necessarily an indication that one should be a leader. In and of itself, desire is not enough to make a leader effective. But certainly the inverse holds: if one is born with leadership skills and abilities and has learned more about leadership, it is natural for that person to desire to lead. After all, we all desire to be good at what we do; and if one is good at leadership it is to be expected that one will want to lead.

    Learn more:

    Managing Geeks 


  • Getting Started with SSIS: SSDT-BI


    SQL Server Data Tools – Business Intelligence (SSDT-BI) is a rich Integrated Development Environment (IDE). It is a version of Microsoft Visual Studio, and you can tell by looking at the title bar when you open SSDT-BI. Click on the image to enlarge and you will see “Microsoft Visual Studio” right there in the title bar.

    If the Start Page does not display, you can open it by clicking View—>Start Page. There are several useful links here. Once you begin developing SSIS projects, the list of Recent Projects will populate, providing a handy way to open the last thing you were working on. There are also links to help you get started developing using the Visual Studio Shell (Integrated) IDE.

    Let’s build an SSIS project!


    Click the New Project link on the Start Page to open the New Project window:


    Click to enlarge the image and you will see several project templates listed beneath the Business Intelligence virtual folder. For SSIS development, select the template named “Integration Services Project”. In the Name textbox, type a name for your project: LoadStageDatabase. Note the solution is also named LoadStageDatabase. When you enter a name for your SSIS project, SSDT-BI automatically copies the Project name to the Solution name. You can decouple the Project and Solution names by typing in the Solution name textbox. Click the Ok button to create the SSIS project and solution:


    Package.dtsx is created along with the project and solution. The Getting Started window also opened providing links to articles to help you get started developing SSIS packages. Feel free to click these links to learn more about SSIS development.

    Click the Save button to save your SSIS project.

    You’ve just created an SSIS project!

    Learn more:
    Watch the video!
    Linchpin People Blog: SSIS
    Stairway to Integration Services
    Test your knowledge

  • Testing

    It’s 2015 and we still have no flying cars. (Dear Doc Brown, we still need roads. Love, Andy) On a similar note, we’ve suffered through another year of software breaches and empty promises to fix the issues behind them. Brian Kelley (Blog | @kbriankelley) was right, We Don’t Care About Data and IT Security.

    Part of the issue is testing. Do you test for security?


    I am often asked, “Andy, how long will it take to test this solution?” My response is, “About as long as it takes to develop the solution.” Project managers love me. Well, not so much. It’s not their fault, the blame lies with unrealistic expectations and the response is usually along the lines of, “Will adding people to this project shorten the development cycle?” to which I respond, “I have nine women, can I get a baby in one month?”

    So what happens? The testing cycle is compressed from weeks or months into a few days or a week. And we wonder why there are security leaks? and why the software doesn’t perform?


    Please join me on this asymptote for a little hyperbole…

    If we flew airplanes like we manage software projects the plane would take off, fly to the destination at altitude, and nose-dive into the runway. From 30,000 feet to 0 feet in a straight line; straight down. The results of such a trip match what we see in software development.

    When people talk to me about software projects like, they act as though this is a fluke. It isn’t a fluke; this is how software is developed in the mid-20-teens. Stakeholders say they want quality, but what they mean when they say “quality” is that they want to hit a deadline. Please do not misunderstand me: deadlines are important for a host of legitimate and good and right reasons, but they are no good for software security and solutions testing.

    Developers vs. Estimation

    Stakeholders (rightly) question the estimates of developers because most developers stink at estimation. One of two things must be true, though:

    1. Developers are liars or idiots or pig-heads who will not or cannot or refuse to produce useful estimates; or
    2. The work is inestimable.

    The answer is 2.


    This is not an easy problem to solve. “Why is that, Andy?” I’m glad you asked. The definition of stupid is doing the same thing over and over again and expecting different results. Here are some things to change if you want different (or even better) outcomes to your software development projects:

    • Realistic expectations.  If software is inestimable, how much time should be spent trying to produce an estimate? Let’s see… doing the math here… carrying the one… I get precisely 0 hours. Stakeholders know what they want and – usually – when they want it. Start there, add what developers know, and walk away from this 15-minute meeting with the expectation that work will begin and you will meet again tomorrow to see how much work has been accomplished.
    • Authority. The developers have none, the stakeholders have it all. Scrum places responsibility for development in the hands of developers and equips them with the necessary authority to make decisions about the features that are implemented in each sprint. If developers lack the authority to remove features from the sprint, you are not practicing Scrum. Period.
    • Communication. Scrum supports daily communications between developers and stakeholders. Stakeholders are not allowed to speak during the 15-minute stand-up meetings. If stakeholders are talking, you are not practicing Scrum. If stakeholders are not in attendance, you are not practicing Scrum. (Do you sense a pattern here?)
    • Time. Testing and development take time. The biggest mistake in software estimation is planning for nothing to go wrong. Plan for everything to fail (at least once) and then succeed.
    • Money. If you believe software development and testing are expensive, you should see the price tag for a data breach. Enough said.


    Evidence-based management provides vital feedback. Learn to apply EBS in your organization; it’s the most effective way to improve software estimation.

  • Presenting in Richmond and Charlotte this month!

    I am honored to present at the Richmond SQL Server User Group 15 Jan 2015!

    I am honored to be presenting at the Charlotte SQL Server User Group 21 Jan 2015!

    If you will be in either area on those evenings, please stop by!



  • Getting Started with SSIS: Get the Software and Tools

    People often ask me for tips on getting started with SSIS. My advice is always the same: Get a copy of SQL Server Developer Edition. At the time of this writing, the current version of SQL Server is SQL Server 2014. If you work in an organization that uses SQL Server, you may be able to obtain a copy of SQL Server 2014 Developer Edition from your organization. If not, I highly recommend purchasing your own copy.

    SQL Server 2014 Developer Edition is available at for about $50 USD. Developer Edition has all the features of Enterprise Edition, only the End User License Agreement is different – you cannot use Developer Edition to operate a Production instance.

    You can begin using SQL Server 2014 for free by downloading the 180-day Evaluation Edition.

    Once you have an edition of SQL Server installed, you will need SQL Server Data Tools – Business Intelligence (SSDT-BI) to develop SSIS packages. SSDT-BI is no longer included with the SQL Server installation media. The current version at the time of this writing is SSDT-BI 2013 and you can download it here.

    Once the relational engine and development tools are installed, you are ready to begin working with SSIS!

    Learn more:
    Watch the video!
    Linchpin People Blog: SSIS
    Stairway to Integration Services
    Test your knowledge


  • It’s That Time of Year to Think About Your Career

    If you work with SQL Server (or want to work with SQL Server), this is a good time of the year to think about your career. Why? It’s the holiday season and you should have some time off… unless you have a Crappy Job.

    You can use some of this time to advance your knowledge about SQL Server, especially the new version: SQL Server 2014. How? You can download a free 180-day version here. That version will carry you through the holidays and then some. Install it, poke around some, search for online tutorials (there are some good tutorials available at the Microsoft MSDN site), and learn!


  • A Biml Case Study

    Business Intelligence Markup Language (Biml) is a SQL Server Integration Services (SSIS) design patterns engine.

    A Story of Productivity

    A while back I was contacted by a client experiencing a familiar issue. The Production SQL Server instance was experiencing performance issues due to conflicts between customers and enterprise reporting needs. They contacted a friend who contacted me. When we spoke they asked, “Can you help?” “Yes,” I replied, “I can help.”

    We scheduled a three-day visit. On Day 1 I installed a Linchpin People SSIS Framework and gathered information about the Production databases. The Framework facilitates execution and logging and supports my preference of building a single SSIS package per table. I counted over 700 tables in over 30 databases. I determined an incremental load pattern would serve the customer best for their largest and most active tables. For the smaller tables, a truncate-and-load – whack ‘n’ load – pattern would suffice.

    I fired up Mist, the Biml development environment from Varigence, and started customizing our version of a staging application.

    I need to pause here and let you know that it takes me about an hour to build and test a typical truncate-and-load SSIS package, and two hours to build and test a typical incremental load SSIS package. I was looking at roughly 4.5 months of work with these tables.

    I spent Days 2 and 3 building and deploying SSIS packages using Mist. In the 16 hours that comprised these days, I completed building over 700 SSIS packages, loaded the Framework execution metadata (I used Biml to auto-generate approximately 25,000 lines of T-SQL at approximately 2,000 lines of code per second…), and performed a test load of Production data to the new enterprise reporting instance of SQL Server. When I ran the numbers, I did not do the work of 100 SSIS developers.

    Only 50.

    You can do this, too.


    Biml and Mist are the secrets to my productivity. I not only drastically cut development time and effort, I improved code quality. SSIS packages are generated from tried-and-true templates. If one executes my tests successfully, then all the SSIS packages will execute my tests successfully.

    Learn Biml NOW!

    Would you like to multiply your SSIS productivity while improving code quality? Tim Mitchell and Reeves Smith are delivering an excellent one-day workshop titled Getting Started With Biml 5 Dec 2014 in Vienna, Virginia. The cost for this event is only $129.


    For ETL developers, Biml (Business Intelligence Markup Language) is a game changer. This is a great new tool for Microsoft business intelligence developers who want to make the most of their development efforts. In short, it’s an XML-based language that will allow you to programmatically create SSIS packages. Even better, it can be enhanced with VB.NET or C# scripting to create BimlScript, which allows you to dynamically build and modify a few, dozens, or even hundreds of packages with minimal effort. Best of all, you don’t need budget approval – if you already have Visual Studio, you can use Biml and BimlScript for free!
    In this full-day presentation, we’ll introduce you to dynamic package generation through Biml. Business intelligence consultants Tim Mitchell and Reeves Smith will walk you through the essentials of Biml – getting started, syntax, and common uses – followed by dozens of design patterns to improve your efficiency as an ETL developer.

    Among the topics that we’ll cover:

    • Overview of Biml – What is it? Where do I use it?
    • Introduction to Biml syntax
    • Biml in the Visual Studio environment
    • Introduction to BimlScript syntax
    • Dynamic package generation with BimlScript
    • Metadata management with Biml
    • Create a simple staging package project with dozens of packages in less than an hour
    • Package (re)generation
    • Source control
    • Common design patterns for Biml in the enterprise
    • Taking Biml to the next level with Mist

    By the end of this full-day presentation, you should be equipped to get started immediately using Biml. It’s a revolutionary technology, and we hope that you’ll be as excited about Biml as we are.

    Register today!


  • Some Thoughts on Event Speaker Selection

    I write this from the perspective of experience. I’ve helped organize dozens of events over the past ten years. Feel free to take the parts of this advice that help and discard the parts that don’t. Enjoy!

    Planning an event is hard work. If you’ve never volunteered to help your local User Group or SQL Saturday, I encourage you to get involved. You will work hard and put a lot into it. But I promise you will get more out of it than you put in.

    Every organizer is free to organize their event in whatever way works for them. Different organizers have different goals. Not all goals align and not all goals are compatible. And that’s as it should be. It’s important to have a goal, though. Don’t go into organizing an event without priorities. Perhaps your priorities will include providing a forum for first-time presenters to speak. Perhaps your priorities will include facilitating well-known technologists presenting deep-dive topics. These priorities are mutually exclusive but many other priorities are not. (There’s no rule against mutually exclusive priorities…)

    Thought 1: Set some priorities.

    You may decide to host an open call for presenters. You may decide to invite presenters to deliver certain content. Either is fine. SQL Saturdays and the PASS Summit host open calls for presentations. Each year a number of first-time presenters are selected to present at SQL Saturdays and the PASS Summit. I think this is awesome! In fact, I’ve long encouraged the PASS Summit organizers to include more first-time presenters. Although I doubt I was the only person who made this recommendation, I’m very pleased that there are more first-time presenters than ever at PASS Summit events.

    Growing first-time presenters is good for the community. Will they make mistakes? Probably. I did. Allowing first-timers to get up there and take a shot is an investment in the future of the community.

    Thought 2: If you’re hosting an open call for presentations, set aside some slots for first-time presenters.

    Speaker selection is hard, especially when there are more speakers than available speaking slots. As an organizer, priorities can help here. When I organized events, they grew in popularity to the point where we had more speakers than slots. Our selection committee decided to award a single slot to as many speakers as possible, and promised those not awarded a priority at the next event. Some speakers (few, thankfully) were unwilling to present unless they received multiple sessions. Those speakers were rarely accommodated at events for which I volunteered. While I understand the desire of a speaker to maximize the value of their travel and time, the event is about more than any one speaker.

    It is impossible to please everyone. Are you bored? Do you like a good fight? Tune into Twitter the day after PASS Summit session selections are announced. You will be sure to catch disappointment and complaints (sometimes from me!). It’s simply impossible to award everyone who submits an abstract a session. It gets even more complicated when the (non-trivial) amount of money PASS Summit pre-conference sessions generate are added to the mix.

    The fact someone complains doesn’t mean you did a bad job. It means someone doesn’t like the way you did your job. And since most organizers are volunteers, you don’t have to worry about losing any (more) money. While listening to complaints about the free hours you poured into this volunteer effort stinks to high heaven, please realize this is part of the job. If you are the type of individual who doesn’t tolerate complaints well, please do not do this to yourself!

    Thought 3: Realize someone is going to complain.

    Some of the complaints will be valid. If you select only your friends or only people who fall into this category or that, you can expect legitimate complaints. If you have more submissions than slots and you select some speakers for multiple presentations while not selecting other speakers, again, expect complaints. Ethics come into play here as well. If you select yourself, be prepared to defend your selection – especially if selecting yourself means not selecting someone else, there’s money involved (like the PASS Summit pre-conferences), you have a non-trivial personal relationship with the person selected, or some combination thereof. Remember, you don’t have to be wrong to appear wrong, and all that’s required to breach ethics is the appearance of misconduct. It’s usually best to simply pick someone else.

    Again, priorities can help. Be aware of the perceptions of your choices. People are lousy at reading minds, so publicly communicating your priorities in advance will diffuse mounds of misperceptions. Privately communicating with those not selected will help as well. It sounds trivial – especially when dealing with an experienced, national- or international-level speaker – to drop them a note saying, “We didn’t select you this time but we appreciate your submission and promise to give your submission priority consideration next year.” But it helps. Failure to communicate is a devastating leadership flaw, volunteer or no.

    The best response to legitimate complaints is to admit your mistake, apologize for it, and work to correct it – immediately and / or in the future.

    Thought 4: Respond to valid complaints.

    These are a few bullets I hope will help everyone managing or considering organizing an event. Thank you, event organizers, for all you do for our community!


  • Attending the PASS Summit

    The PASS Summit is an annual gathering of SQL Server professionals and others interested in learning more about SQL Server. Folks come from all over. Here’s a few suggestions for getting more out of your PASS Summit experience.

    “What if I’m Not There?”

    Not everyone can attend the PASS Summit. You can still enjoy a taste of the activities via PASSTV, which will be streamed from the PASS Summit 2014 home page.

    Meet New People

    If this is your first (or one of your first) PASS Summit(s), don’t be shy. If you see someone you want to meet, introduce yourself. If that person is in a conversation or appears otherwise engaged (for example, if that someone is sitting outside the Subway on the fifth level of the Washington State Convention Center furiously typing a blog post… hypothetically…) say “Hi” and, if you want to talk more or discuss some technology question or even just hang out, ask if now or later is a good time. I can speak from experience, most geeks love sharing and will stop typing their blog post or whatever they’re doing to have a chat with you.

    Old timers (like me), if you see someone wearing a First Timers ribbon, you introduce yourself! You remember how you felt your first Summit, break the ice. Our field is disproportionately populated by introverts, take some initiative.

    Be Respectful and Tolerant

    Everyone believes what they believe for a reason. You do not have to agree with what someone says or does. But unless they’re trampling on others, respect their expressions. And if they are trampling on others, intervene. Either personally, or by finding someone who can and will intervene. PASS leadership has gone to great lengths to define a fair and practical Anti-Harassment Policy. Read it. Now. And if you see someone acting in a manner you believe inconsistent with this policy, please tell someone.


    Microsoft has a habit of releasing new cool stuff during the week of the PASS Summit. You can learn about it first by attending or viewing the Keynote addresses Wednesday and Thursday morning. There are too many awesome sessions at the Summit happening at the same time – it’s a fact. But you can view the sessions and powerpoints by purchasing the downloads or USB sticks loaded with them at the PASS Boutique. Even if you cannot attend, you can buy all the content. Plus, the PASS Boutique sells other “PASS-Wear” and data geek paraphernalia.

    I would love to meet you if you’re attending the Summit. You can find me at the Linchpin People booth in the Exhibition Hall or wandering hither and yon. I will also be presenting Wednesday morning. I hope to meet you here!


  • Repost for 2014: Come to the PASS Summit

    I originally posted this five years ago. It’s about my first PASS Summit ten years ago. I’ve made a couple edits and added some links. I hope it will encourage you to attend the PASS Summit 2014. :{>

    "What's the big deal about the PASS Summit, Andy?"

    Allow me tell my story (again): "Hello. My name is Andy Leonard, and I am an accidental database professional." ("Hi Andy.")

    I jumped the fence from applications developer to database person in 2003. I thought I understood databases. I could write queries, design tables, build stored procedures, etc. And then I was standing nearest the server when my team decided to replace the SQL Server person. Bam! Instant SQL Server guru... right? WRONG!

    Yes, I had SQL Server on my resume and had done some cool things with the product. But this was a data warehouse. A large one. The very first thing I learned in my new position was: I didn't know nearly as much as I thought I knew about SQL Server. Or databases. Or anything.

    Sobering, very sobering.

    But Then...

    I met a couple SQL Server heroes at my first PASS Summit - 2004 in Orlando. I met Ken Henderson and Kalen Delaney (blog | @SQLPeople). I learned a lot about database tuning from Kalen Delaney's preconference session. And Ken Henderson inspired me (I wrote about it here).

    The short version: I arrived at PASS Summit 2004 as a developer struggling in his new (accidental) role working with SQL Server. I left PASS Summit 2004 as a database professional.


    Go. Get there. There's lots of good reasons to attend. I firmly believe attending the PASS Summit will change your career, if not your entire life. It changed both for me.

    If you read this and attend, catch up with me. I'm the fat guy with a fu. We can chat about being a database professional, or business intelligence, or about being an accidental DBA (you'd surprised how many there are!). I will be at the Linchpin People booth in the Exhibition Hall. I hope to see you there!


  • [Re-] Updated: Creating a Custom SSIS 2012 Task

    Apologies. My first edition of this post copied outdated links to this series. I have corrected the links but left the comments pointing out my earlier error. Thank you to those who let me know! :{> 

    A while back I asked myself: “Self, do you think it is possible to create a custom SSIS 2012 task using Visual Studio 2012 Express?” That question launched a quest to learn the answer. In this series of posts I describe what I learned. I recently updated the material. You can find the updated series here:

  • Creating a Custom SSIS 2012 Task – The Rambling Introduction
  • Creating a Custom Task in SSIS 2012 – Getting Started
  • Creating a Custom Task in SSIS 2012 – Configuring the Project
  • Creating a Custom SSIS 2012 Task – Signing the Assembly
  • Creating a Custom SSIS 2012 Task – Preparing the Environment
  • Creating a Custom SSIS 2012 Task – Coding the Task
  • Creating a Custom SSIS 2012 Task – Coding the Task Editor
  • Creating a Custom SSIS 2012 Task – Binding the Task and Editor
  • Creating a Custom SSIS 2012 Task – Notes From My Experience



  • Reminder: If You Want to Vote in the PASS Board of Directors Election, You Have 6 Days…

    Per Thomas LaRock’s post titled Board of Directors Election Update on the PASS Blog:

    All PASS members who have not yet received a ballot and who had an existing profile as of June 1, 2014, will be given the opportunity to receive a ballot by updating their profiles before October 5, 2014, at midnight PDT. On October 6, we will pull an updated list of registered voters, filter for duplicates, and then on October 7, we will send all newly registered voters a ballot.  All voting will end on October 14 at noon PDT.

    PASS leadership made this concession and extended the deadline to provide everyone eligible an opportunity to vote. So vote!


  • Well Done, PASS Leadership

    I am impressed with the response of PASS leadership to the controversy surrounding the 2014 Board of Directors election. Others have covered the topic much better than I will here, but a short version is PASS responded to the PASS Board 2013 election controversy (members with multiple email accounts receiving multiple ballots) by requiring members to identify a primary account / email address.

    The issue? Not everyone got the message.

    The initial response from PASS leadership was in line with previous responses from PASS leadership; “We’re not going to change anything” (paraphrased). I was disappointed in this response and said so. But then PASS leadership reversed this decision. In a blog post late Friday evening, PASS President Thomas LaRock (blog | @SQLRockstar) posted Board of Directors Election Update on the PASS blog, outlining the procedure and use cases for those who were hitherto excluded from the 2014 election process; a procedure that would allow them to vote.

    I agree with this decision but I was not impressed. This is what leaders are supposed to do. It’s doing what their constituency elected them to do.

    I was impressed by something I haven’t seen in PASS leadership before. (Maybe it was there and I missed it…) It’s this second paragraph from Tom’s post:

    Before I get started I want to make something very clear: I accept full responsibility for all issues with the current election process. Together we had, and still have, the very best of intentions. On behalf of myself and the entire PASS Board, I offer the sincerest of apologies for all of the frustration caused.

    Two things:

    1. Accepting responsibility. I’ve seen plenty of dictates handed down from the PASS Board in the past, especially when PASS leadership made unpopular decisions. I’ve been reminded of their authority. I don’t recall seeing anyone take responsibility – especially publicly. In my opinion, owning the issue is essential for leadership. I’ll go further and state that I believe not owning the issue is a failure of leadership.
    2. An apology. I believe this apology deflates the harm caused by this issue. More than that, I think this apology puts this issue to rest. Combined with doing the right thing and accepting responsibility, the apology offers closure. Unclosed issues hang out and contribute to the next controversy; they’re “stored fuel” for the next fire. That’s why it’s best to apologize early and often (bad election analogy…).

    I’ve been hoping to see changes in PASS leadership for a while now. Doing the right thing here was admirable. But accepting responsibility and apologizing was one kind of change I’ve been hoping and waiting for.

    Well done, PASS leadership. Well done.


  • Join me for 3 Days of SSIS Training in Denmark – Advanced Integration Services 18-20 Nov 2014

    I am honored to announce Advanced Integration Services will be delivered in cooperation with  in Aarhus, Denmark 18-20 Nov 2014.

    Target Audience

    The target audience for this course is intermediate SQL Server Integration Services developers (or quick learners) who wish to learn best practices and the more advanced stuff, and those who wish upgrade their existing SSIS skills to 2012. Since there are almost no changes between SSIS 2012 and 2014, this course will also be suitable for SSIS 2014 users too.


    • Advanced patterns for loading data warehouses
    • ETL Load Performance
    • Data Cleansing
    • Flow, Precedence, Advanced Loop Containers
    • Error handling
    • ETL Instrumentation
    • Scripting in SSIS
    • Designing Custom Tasks
    • Executing, managing, monitoring, and administering SSIS in the enterprise
    • New features in SSIS 2012 and 2014
    • The (new) Project Deployment Model
    • The (new) SSIS Catalog
    • SSIS Frameworks
    • Business Intelligence Markup Language (Biml)

    I hope to see you there!

    Register today! Sign up for the Advanced Integration Services at the bottom of this page.


This Blog



Source Control 2.0 from Red Gate

My Company

Blog Roll

Check out the Linchpin People Blog...
Linchpin People Blog

Contact Me


Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement