Skip to main content

PASS Community Summit 2009

One of my favorite times of the year is the PASS Community Summit.  It's five jam-packed days of SQL Server sessions by Microsoft employees, MVPs, and the people that you read about in technical books.  It's pre-conference and post-conference workshops on all different levels of topics of SQL Server.  It's a way to meet new people who love to do what you love to do and connect with old friends who you only see once a year.  It's a way to get a job or sell a job.  It's all of this and so much more that I can't even begin to describe.

I'm excited to attend for the third year starting tomorrow.  If you are attending the Summit, I hope you'll come and introduce yourself.  You can find me at one of these locations/times:

Monday, November 2, 2009
4:30pm-6:30pm 
Networking Pre-Con - I'm really excited to learn about the best ways to meet people and meet other people who are interested in the same thing!

Tuesday, November 3, 2009
11:45am-12:45pm

Birds of a Feather Lunch (Expo Hall 4B) - I am hosting a table during lunch on “Is Business Intelligence an Oxymoron?”.  I'm looking forward to hearing your thoughts on how we can incorporate the business into our data warehouse and delivery design.

Wednesday, November 4, 2009
11:30am-1:30pm

Women in Technology Luncheon and Panel Discussion (Room 6BC) - I am one of the panelists discussing “Energizing the Next Generation: Encouraging and Inspiring Young Women to Choose Tech Careers”.

3:00pm-4:15pm
“Adding SSRS Report Bells and Whistles” (Room 612 (165) ) – I am presenting on Reporting Services 2008 design best practices and guidance.

Thursday, November 5, 2009
12:00pm - 12:30pm

Book Signing (South Lobby, across from Summit Bookstore) – I’ll be hanging out by the bookstore as one of the authors of Microsoft SQL Server 2008 Integration Services Problem-Design-Solution.  Definitely come by if you have any question about the book!

Of course, I will also be attending sessions and some evening events, so please come and talk to me there instead.  I’m looking forward to attending the best Summit yet.

Comments

Unknown said…
If you will be willing to share information with me about ssrs.

It will be my pleasure

Jessica Moss´s eternal slave

robertdba@hotmail.com
balaji hambeere said…
I am using below query in sql command from varaible to fecth the data from two different table.

select x.*, y.col1, y.col2 from table1 as x inner join table2 as y on y.[Y ID] = x.XID

AS per my businees logic i need use the query as sql command from variable. When i am running the package after the setting DelayValidation to True, I am getting the below errors..Please help me on this..

"[OLE source table1]] Warning: The external columns for component "OLE source" (1) are out of synchronization with the data source columns. The external column "col2" (601) needs to be removed from the external columns. The external column "Col1" (598) needs to be removed from the external columns."..

[SSIS.Pipeline] Error: "component "OLE source table1 " (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".

Advanced Thanks!!..

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

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,

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