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

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 Db 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:

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 Db 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:

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 Db 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:

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 Db 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:

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 Db 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:

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 Db 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:

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 Db 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:

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 Db 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: