It's time again for SQL Saturday Washington DC! With last year's event being such a huge success, this year's event will be even better! We are expecting over 250 attendees to show up for a full day of training from some of the best speakers in the SQL Server community.

This is one event you don't want to miss! Everyone who attends will get a SQL Saturday T-Shirt and lots of swag! Free breakfast and lunch will be provided. We will have several SQL Server vendors that will be presenting the latest upgrades and solutions. And at the end of the day, we will be raffling off some awesome door prizes provided by our many sponsors!

SQL Saturday is a FREE one day training events for SQL Server professionals. SQL Saturday was initially the idea of three DBAs that wanted a Code Camp style event just for SQL Server professionals. It began with the first SQL Saturday in Tampa, Florida. The event was such a huge success, more events followed. After over 40 successful events, The Professional Association for SQL Server took over the administration of SQL Saturday events.

SQL Saturday events are usually divided into three tracks consisting of BI, Database Development, and Database Administration. Typically there will be five sessions per track. SQL Saturday tries to recruit local SQL Server professionals to present at the event, but occasionally, more nationally known speakers may also present.

SQL Saturday is all about sharing issues and solutions, and gaining knowledge that will make you a better SQL Server professional.

We’ll see you there!!!

Register at: http://www.sqlsaturday.com/96/eventhome.aspx

FOLLOW US!

SQL Server: An error occurred while executing batch. Error message is: The directory name is invalid.

I logged onto the server this morning to delete some files because the disk had run out of free space. After deleting some files, I went to run some maintenance scripts in SSMS and received the following error:

An error occurred while executing batch. Error message is: The directory name is invalid.

After doing some online research, I found out that the reason for this error is because SQL Server cannot find the temp folder in which to store the query results. To correct this, try logging off and back on to the machine that you are running SSMS on. If the error persists, reboot the machine.

Cannot edit job steps in SSMS 2008 R2

When attempting edit the job step, or view the job step details, I received the following error:

Creating an instance of the COM component with CLSID {AA40D1D6-CAEF-4A56-B9BB-D0D3DC976BA2} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)

You may also get this error when attempting to create a new job step.

I did a search and found several old post requesting help with the same problem. Microsoft corrected the problem with the last Hotfix; Cumulative Update package 7 for SQL Server 2008 R2.

For more information on Cumulative Update package 7 for SQL Server 2008 R2 and how to download it, go here; http://support.microsoft.com/kb/2507770