IsQueryStoredProcedure property won't stay set

Hot Topic

C# CLR best practice example
Error 0xc0202009 for importing access97 into sql
Push pdf to Report Manager from vb script
Balancing scalability with availability
Charts
Intersecting Drillthrough results - an MDX challenge
Return the data from a table ordered by its hierarchy
SSIS - Excel Destination Formatting
Maintaining Security
Live Streaming Requirements?

SQL Server

cannot install integration services
PivotTable Total from Database
How to Get Error Output from and OLE DB Command Destination
SQL Server 2005 with 2000
difference between dbo user and another user
Is anyone using C# and the SSIS Objects to Develop/Modify Packages?
Export problem
Multiselect list box width and other things
Unspecified error: "Could not find server"
Sql server Express edition installation (OS Windows Home XP)

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

Answer this question

IsQueryStoredProcedure property won't stay set

  • Keith Thomson

    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.



  • folwelld

    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.
  • IsQueryStoredProcedure property won't stay set
Answer this question