A server upgrade prompted me to migrate some SSIS packages. These packages were going from SQL 2008R2 to SQL 2008R2, so there was no change there; however, the new server had a different version of the SharePoint List Adapters, which allow you to easily write to and get data from SharePoint Lists. When I opened the package on the new server, the list adapter was not recognized and I got the following error.
“Error 1 Validation error. %Job Name% The component metadata for “component “SharePoint List Destination” (529)” could not be upgraded to the newer version of the component. The PerformUpgrade method failed. %Job Name% 0 0″
The ‘version’ of the adapter was same; however, I was using an updated release as shown here by the release date for the adapter. Upgrading was straightforward, once I found this post on codeplex. My experience was going to the package in Windows Explorer and opening the file in Textpad. Now I guess I should lament here that I didn’t do it in PowerShell, but one thing at a time here! I then replaced the PublicTokenID as mentioned in the post. I saved the text file and had to re-open the SSIS project. There is a newer version of the file itself and one would need to update the Version and the PublicTokenID if upgrading to the latest version.
The last step was to add a SharePoint Credential to the List Adapter as this is a new feature. I right clicked in my connection manager and choose new connection. I was then able to choose SPCRED and enter the appropriate information. My package was converted to the new server and worked well.
SQL Saturday RVA is just under two weeks away and we have been busy trying to get everything in place. I have had a great team with Wayne Sheffield (b|t) and Geoff Johnson (t) doing some heavy lifting. Our event will be at the University of Richmond, hosted by the school for continuing studies. Tammy Alexander has been wonderful to work with and has opened a couple of doors where we thought we had hit a dead-end.
I thought I was familiar with the work required to pull off an event like this; however, it has been a challenge. PASS has been wonderful and it has been nice to work with Karla Landrum (t). Our event opened about 6 months ago and I am glad we did, we needed almost every day of it. I am unsure how some of these events can go up in less than 3 months.
If you are planning to attend the event, I am sure you will have a good time. We have a great speaker lineup and it continues to amaze me that people will give up their weekend to come and help others learn. I am excited about being at the University of Richmond and I hope the area we are in fosters conversation and networking. We will have several items to raffle off and some of our sponsors have free items for every attendee! I hope to see you there.
One of the great aspects of the SQL Server community is the willingness of people to share what they know as they discuss resolutions to problems they face. There are a variety of opportunities to engage these people–blogs, user groups, SQL Saturday, the Summit, and there may be a few I am not aware of; however, I can say that none of them are quite like a SQL Cruise. I’m glad I found it–SQL Cruise is the real deal.
I did not, at first, consider SQL Cruise to be right work/play model. I had not been a cruise before and I wasn’t sure what to expect. My track record shows I tend to do things on the cheap and cruising screamed expensive–at least to my ears. The price of the training itself was another concern as I would be paying for the training out of my own pocket. While Tim Ford (blog|twitter) is a recognized name in the community, I hadn’t met him nor had I met the other speakers. A self-proclaimed people person, I needed a connection and that connection came in the way of Wayne Sheffield (blog|twitter), who attended the Alaska 2012 cruise. I met Wayne at the Richmond SQL Server users group and had attended several of his SQL Saturday and user group sessions. Wayne gave it his seal of approval and after my wife and I agreed the numbers would work out, we booked our ticket on the SQL Cruise.
After conference activity area
As a first time cruiser, I was pleasantly surprised by the whole experience and would go again. If I was not part of a conference, a seven day cruise might be a little long; however, there is plenty to choose from to occupy yourself on board. As a frequent foreign traveler, I enjoyed chatting with the staff about where they were from, what locations we had been to in common, and where they enjoyed going on the Islands. Everyone was extremely friendly and when I found out they worked 10 hours a day, 7 days a week for 9 months I was super impressed.
Upward and Onward!
Being in the Caribbean was very nice and I had not traveled to that part of the world before. I was surprised how many Spanish speakers there were on the islands and many had lived and worked on the different islands their whole lives. Again, one to do things on the cheap, I had purchased a Lonely Planet book beforehand and we went to several local places to get a better feel for life on the island. On St Thomas of the Virgin Islands, we boarded a local bus and I struck up a conversation with a high school student. I asked him what he call US citizens from the ‘mainland’–his response: “tourists”.
Beaches in St Maarten
Favorite Island treat: French pastries on French side of St Maarten
Favorite Island Activity: Snorkeling on St Johns.
Favorite Island memory: Traveling back to the Cruise Ship with Big Joe, his son and Jason Brimhall (blog|twitter), his wife and my wife. We had taken local transportation and no one, even me, was sure we were headed the right direction until we could actually see the cruise ship. We shared the bus with several high schools students.
Chris Bell(blog|Twitter) is detailing his adventures on his site for a better day by day feel.
You do, after all, sign up for SQL Cruise because of the training and the technical presentations, given in two hour blocks were very good; however, they are what you would expect at any SQL Saturday. I did learn something new in each session and I have a notebook with pages of writing to prove it. The real value came in less structured settings called office hours. In those sessions, I would could ask ‘my’ questions to either a single person or the group I happened to be with at the time and get different viewpoints. We all know there are a million different ways to do the same thing and I personally valued getting different opinions. In preparation for the cruise, I made a list of some of the areas I was struggling with or needed help with and asked them. Some were discussed in front of the whole group and I was a little nervous about being labeled a ‘stupid question asker’, but then I realized I was with the SQL community and EVERYONE was willing to help.
Getting my learn on!
Not all of the training is technical in nature. Most, if not all, of the attendees have been DBAs for 5+ years and like me, have good technical skills. Many are looking to expand the nature of their work and it was fascinating to discuss the paths they traveled. For instance, talking with Tim about his experience of going from developer to DBA to then organizing SQL Cruise and talking with Neil Hambly (blog|twitter) about how he got his job with Confio showed me there are multiple ways to find fulfilling work in our field.
(Possible) Favorite Training Moment: The class reaction when Kevin Kline opened the execution plan I submitted for the Execution Plan contest. The collective grown in the room let me know I wasn’t going crazy.
(Possible) Favorite lesson learned: Office Hours discussion on communicating with management. See Takeaway #4.
There are lots of little things I took away from the experience. I have areas I need to improve in, some I knew before the cruise, and I have the following plan based my experience on the cruise. In no particular order
- Become proficient in PowerShell. This goal is really about being comfortable with the PowerShell language to the point I can begin to administer my environment in it. I would like to begin collecting server data/stats about the different environments and having that in a central place. Phase II would be to create my Minion (You should have been there)–a repository of metadata that each system uses to perform admin functions. IE the backup location is in this table and an update to it would affect the next backup job cycle. I ordered “Learn Windows PowerShell 3 in a Month of Lunches” to start me in this process.
- Implement policy based management. I have been bitten more than once by a ‘standard’ setting that was different on this one server. There are several ways to implement this; however, I just need to start.
- Master the execution plan. As an attendee, we all received a copy of Grant Fritchey’s “SQL Server Execution Plans” courtesy of Red Gate . As the winner of the SQL Sentry’s Hairy execution plan contest, I received a copy of SQL Sentry’s Execution Plan explorer Pro. No specific session focused on this; however, I realize I need to place a little more effort in reading execution plans and now I have some awesome tools to do it with.
- Create a management report that allows them to easily see the health of the SQL Server. This is not the same type of report a DBA would want to see, just the number of executions per second and how long those executions are taking with some history for comparison. Stretch goal–make it available to the SQL Community in a way users can easily deploy and use.
- Go on another SQL Cruise. I would hop on the Alaska cruise in a minute, but my schedule won’t allow it this year. I would surely enjoy chatting with Buck Woody and the others, but I will have to take a rain check and check out the 2014 offerings.
As an aside note, I went on the cruise with my wife and she had a great time as well. If you can swing it, I recommend bringing the spouse along. Beside the technical sessions, everyone has the opportunity to get together and we enjoyed getting together with the other family members. My wife now has a few more Facebook friends she might also meet on the SQL trail. It was a great time and I am glad I had the opportunity to go. I would recommend it to anyone.
Tim posted some great photos on his site. Check them out!