Recently I’ve been getting the following error message while trying to create an SSIS 2012 step in SQL Server Job Agent, and setting the Parameters or Connection Strings for that step:

The property ‘ParameterName’ contains invalid characters as an object name. Remove the invalid characters. (Microsoft.SqlServer.Management.IntegrationServices)

This error emerges after confirming the newly created step (which will run the SSIS package) in SQL Server Job Agent, and after setting the parameter.

Read more →

For some strange reason I can’t seem to find a lot of literature online about the basic behavior of the LastNonEmpty SSAS function, which is currently only available in an Enterprise Edition of Analysis Service (for some really strange reason, since you can emulate the behavior in other SSAS versions relatively painlessly), so here is a nice wee post that goes through the syntax of the LastNonEmpty function, how to override and customize it’s default behavior, what performance improvement techniques you can apply, and some of the quirks you might experience when playing around with the LastNonEmpty Analysis Service function.

Read more →

The SSIS 2012 Catalog integration with SQL Server comes with the advantage of being able to execute SSIS packages indigenously from within T-SQL, along with a host of other functionality including improved monitoring and logging, integrated security and obviously the new deployment model.

Executing SSIS packages by calling a stored procedure can be handy in many situations, but also comes with some (albeit minor) stipulations and quirks, this post tries to go through some of the basics of executing SSIS packages through stored procedures, while also touching lightly on some of the issues I encountered while having a go at this new SSIS execution method.

Read more →

Although the new SSIS 2012 Project Deployment Model is pretty cool, it is a completely new deployment architecture that is bound exhibit some bugs. To be honest SSIS 2012 in general seems to be less geared up towards enterprise level scale-out, and will work better in a non-24/7 load environment.

The error I am experiencing with SSIS 2012 is to do with deploying a project (from SQL Server Data Tools) to an SSIS Catalog DB, whenever a project is deployed, there seems to be a 50/50 chance that I will receive the following deployment error:

Failed to deploy project. For more information, query the operation_messages view for the operation identifier ’123456′. (Microsoft SQL Server, Error: 27203)

Read more →