Skip to main content

SQLSaturday Richmond 2010

Do you have a neat T-SQL trick that you'd like to show off? Is your idea of a good time figuring out Analysis Services hierarchies? Have you solved world peace using SQL Server? If so, you should submit an abstract to speak at SQLSaturday Richmond!

We are currently accepting speaker submissions. You can submit an abstract by going to the website: http://www.sqlsaturday.com/30/callforspeakers.aspx! Please submit by 12/12/2009.

If you're not interested in wowing people with your extensive SQL ninja skills, we hope you will consider attending this amazing SQLSaturday event first time ever in Richmond, VA. Obligatory marketing blurb with further information below:

Join the Richmond developer community for a free, one-day training for SQL Server professionals, developers, DBAs, and even people who don't know how to spell SQL.

When: January 30, 2010
Where: ECPI College of Technology
4305 Cox Rd
Glen Allen, VA

Admittance to this event is free; all costs are covered by donations and sponsorships. Please Register soon as seating is limited, and let friends and colleagues know about the event. For more information, visit http://www.sqlsaturday.com/ and select “SQLSaturday #30 - Richmond 2010”

I won't be speaking this time around, but I will be there to help things run smoothly! I hope to see all of you there :)

Comments

Rusty said…
Bearer of bad news here! Looks like it has been postponed until April 10, due to global warming. SQLSaturday is now SnowQLSaturday. Check back in March/April.
Anonymous said…
Keep on posting such themes. I like to read blogs like this. BTW add more pics :)
PatrickJoy
Unknown said…
Hello all of you who access Jessica M.Moss Blog. I invite and always will invite everyone to attend any Jessica M. Moss SQL conference. I am sure you guys won´t regreat about it.( I wish I could be one of you guys who attend her sql conferences...anyway SQL Server is passion and I love it just like her, but the only difference between I and her is... She is the Master and I am a slave comparing to her sql experience...... in fact I think it would be nice to her real slave.

Talles Roberto

Jessica M. Moss´s eternal slave

robertdba@hotmail.com
Anonymous said…
Great story you got here. I'd like to read something more about that theme. Thanx for posting this data.
Joan Stepsen
Indian escort London

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