SSIS - SQL Task - Parse Query Button

This is a discussion on SSIS - SQL Task - Parse Query Button within the sqlserver-dts forums in Microsoft SQL Server category; I have an “Execute SQL Task” object in my SQL 2005 Integration Services Project. The relative properties are: ResultSet SingleRow ConnectionType ADO.NET Connection MYDB SQLSourceType Direct Input SQLStatement sp_determineworkingday isQueryStoredProc True sp_determineworkingday is a stored procedure in “MyDb”. When I hit Parse Query, I get the “object reference not set to an instance of an object” message. I tried fully qualifying the stored proc, but get the same message. It works when the package runs, just gives that message in design time. Its probably nothing to worry about, just could do without the message. Any idea why I get ...

Go Back   Database Forum > Microsoft SQL Server > sqlserver-dts

Database Forums

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 08-21-2008, 12:19 PM
Default SSIS - SQL Task - Parse Query Button

I have an “Execute SQL Task” object in my SQL 2005 Integration Services
Project.

The relative properties are:
ResultSet SingleRow
ConnectionType ADO.NET
Connection MYDB
SQLSourceType Direct Input
SQLStatement sp_determineworkingday
isQueryStoredProc True

sp_determineworkingday is a stored procedure in “MyDb”. When I hit Parse
Query, I get the “object reference not set to an instance of an object”
message. I tried fully qualifying the stored proc, but get the same message.
It works when the package runs, just gives that message in design time. Its
probably nothing to worry about, just could do without the message. Any idea
why I get the message or how to get rid of it?

Your help is appreciated

Reply With Quote
  #2  
Old 08-22-2008, 02:34 PM
Default RE: SSIS - SQL Task - Parse Query Button

Hello Cam:
Not sure if this is the cause; you will have to verify it for us:

For any stored procedure whose name starts with "sp_", when the system goes
to run it, regardless of the fact that you qualify that name with database
and schema, it will ALWAYS look in the Master database first, before looking
in the current Database or using the qualified name.

Try renaming the proc to something other than "sp_" and see what you get.

HTH

--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Cam" wrote:

> I have an “Execute SQL Task” object in my SQL 2005 Integration Services
> Project.
>
> The relative properties are:
> ResultSet SingleRow
> ConnectionType ADO.NET
> Connection MYDB
> SQLSourceType Direct Input
> SQLStatement sp_determineworkingday
> isQueryStoredProc True
>
> sp_determineworkingday is a stored procedure in “MyDb”. When I hit Parse
> Query, I get the “object reference not set to an instance of an object”
> message. I tried fully qualifying the stored proc, but get the same message.
> It works when the package runs, just gives that message in design time. Its
> probably nothing to worry about, just could do without the message. Any idea
> why I get the message or how to get rid of it?
>
> Your help is appreciated
>

Reply With Quote
Reply


Thread Tools
Display Modes



All times are GMT -4. The time now is 04:20 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Integrated by bbpixel2008 :: jvbPlugin R1013.368.1

Search Engine Friendly URLs by vBSEO 3.1.0
vB Ad Management by =RedTyger=
In an effort to better serve ads to our visitors, cookies are used on Mydatabasesupport.com. For more information, check out our Privacy Policy.