Skip to main content

Fall 2009 Conference Odyssey

As promised, I wanted to let you know about a few events where I'll be in the upcoming weeks. This Saturday (10/17), I'm making the trek up to East Iowa for their SQLSaturday event. They pulled in quite a few great speakers, and they've also invited me to speak on my favorite BI products: SSRS, SSIS, and SSAS! It looks like registration is still open, so if you're in the area, you should definitely sign up, come by, and say hi.

The following week, I am pleased to be speaking at the Charlotte SQL Server User Group on Extract, Transform, and Load your Data Warehouse. I'll be making the drive down (audio book suggestions, anyone?) on Thursday, October 22 to speak that evening. I'm looking forward to meeting new people and seeing some old friends in the area. I'll also be staying over for a soon-to-be-announced event on Friday.

The first week of November, I'll be at the PASS Community Summit. These is my third year attending the conference, second year speaking, and first time as a panelist on the WIT luncheon. This conference is so big and has so much going on that I will give it its own post closer to that time.

The following week is the SharePoint Connections conference. My friend and colleague, Kevin Israel, invited me to deliver a joint preconference workshop entitled SharePoint BI - Building Dazzling Dashboards and Sizzling Scorecards in SharePoint. Can you tell which section will be my part? *coughBIcough* ;) The all-day workshop is on November 9, so I'll be taking the rest of the week to attend some sessions and talk shop with attendees. Please do look me up and introduce yourself!

Rounding out the list is the SharePoint Saturday event in Richmond on November 21. I'm not sure if I'm volunteering or speaking yet, but either way, I will be there! The SharePoint Saturday events have taken off like a rocket, and I'm excited to participate.

That wraps up the current list. I hope to see you at one of the events.

Update: Fixed SQLSaturday date

Labels:

Comments

Seth Delconte said…
Awesome lecture. Got me excited about using SSIS again, and to learn more about data warehousing. Thanks!
October 22, 2009 at 5:58 PM
Unknown said…
It was a pity I was not there otherwise I would have asked you to give me your autograph.


Jessica Moss´s eternal slave

robertdba@hotmail.com
February 11, 2010 at 6:39 AM
Post a Comment

Popular posts from this blog

SSIS Configuration to Configuration to Configuration Schema

I've gotten several requests to put down in writing the configuration schema that I use as the base of my SQL Server Integration Services framework. It contains a set of configurations: an indirect environment variable configuration, which points to an XML configuration file configuration, which points to a SQL Server configuration. I learned this configuration from the Project REAL Reference Implementation . If you're getting started with a BI implementation, I highly recommend that you download it for some great ideas and best practices. Steps to implement: 1) Create an environment variable on your machine with the name of SSIS_CONFIG_FILE and the value of: C:\SSIS\Config\MasterConfigFile.dtsConfig. 2) Create an SSIS configuration file at C:\ SSIS\Config\MasterConfigFile.dtsConfig with the line: <configuration valuetype="String" path="\Package.Connections[CONFIG_SERVER].Properties[ConnectionString]" configuredtype="Property"><configuredv
29 comments
Read more

Execute SQL Task Designer Limit

After migrating a package from DTS to SSIS, I had a problem with an Execute SQL Task. I couldn't change any characters in the SQLStatement property; I couldn't add any new characters; I could delete characters, but not retype them! After googling several variations of "integration services" "read only" and "Execute SQL Task", I deleted about half of the entry in a fit of frustration. Lo and behold, I could type again. Apparently, there is limit on the size or number of characters that can be entered in the SQLStatement property. From my experimentation, I came up with a limit of 32767 characters. The interesting thing is that the restriction only seems to be on the designer. If you set the SourceType to "Variable" and use a variable that contains more than 32767 characters, the task will execute. Also, if you use the "Direct Input" SourceType and modify the package XML to set the SQLStatement longer than 32767 characters,
10 comments
Read more

Reporting Services 2008 Configuration Mistake

To start working with the management side of SQL Server Reporting Services 2008, I decided to set up a report server and report manager. Unfortunately, I made a mistake while setting up my configuration that left me a little perplexed. Here are the steps I took to cause, track down, and solve the issue. Problem: I began by opening the Reporting Services Configuration Manager from the Start Menu. I clicked through each of the menu options and accepted the defaults for any question with a warning symbol, since warning symbol typically designate an action item. After two minutes, all of the warning symbols had disappeared, and I was ready to begin managing my report server. Unfortunately, opening up a browser and trying to open up the report manager resulted in the dreaded " The report server has encountered a configuration error. (rsServerConfigurationError) " message. Sherlock-ing it: I put on my sleuthing hat and went to the log file directory: C:\Program Files\Microsoft
47 comments
Read more