Monday, February 20, 2012

IsQueryStoredProcedure property won't stay set

I'm using an ExecuteSQL task to fire a stored procedure. There is a property in the editor called IsQueryStoredProcedure that is disabled. However, in the properties window there is a property call IsStoredProcedure that is enabled and can be set. Problem is that it doesn't stay set. Is this a bug?

From BOL

IsQueryStoredProcedure

Indicates whether the specified SQL statement to be run is a stored procedure. This property is read/write only if the task uses the ADO connection manager. Otherwise the property is read-only and its value is false.

|||I just went thru this...if you're using an OLE DB provider, don't worry about it. Just put the SP call as your sql statement and it will work. You don't need to set that property.

No comments:

Post a Comment