Can't Delete Job

Hello:
I've got an old job I am trying to delete from my SQL Server 2005.
Everytime I try to delete this, i get the following error:
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occred in the database "msdb", table
"dbo.sysmainplan_subplans", column 'job_id'.
I know what an FK is, and why the job can't be deleted, but how do I
resolve this? How can I delete this job?Greg wrote:
> Hello:
> I've got an old job I am trying to delete from my SQL Server 2005.
> Everytime I try to delete this, i get the following error:
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occred in the database "msdb", table
> "dbo.sysmainplan_subplans", column 'job_id'.
> I know what an FK is, and why the job can't be deleted, but how do I
> resolve this? How can I delete this job?
>
Was the job created by a maintenance plan? Looks like it might have
been, judging from the FK reference. You'll probably have to go through
the maintenance plan to delete the job.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Guess I believe it was -- I was using some sort of Wizard for my first
few jobs until I got my feet wet w/adding jobs w/o using a Wizard....
I'll let you know what I find out.
-Greg
Tracy McKibben wrote:
> Greg wrote:
> > Hello:
> >
> > I've got an old job I am trying to delete from my SQL Server 2005.
> > Everytime I try to delete this, i get the following error:
> >
> > The DELETE statement conflicted with the REFERENCE constraint
> > "FK_subplan_job_id". The conflict occred in the database "msdb", table
> > "dbo.sysmainplan_subplans", column 'job_id'.
> >
> > I know what an FK is, and why the job can't be deleted, but how do I
> > resolve this? How can I delete this job?
> >
> Was the job created by a maintenance plan? Looks like it might have
> been, judging from the FK reference. You'll probably have to go through
> the maintenance plan to delete the job.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Greg wrote:
> Guess I believe it was -- I was using some sort of Wizard for my first
> few jobs until I got my feet wet w/adding jobs w/o using a Wizard....
> I'll let you know what I find out.
Good man!! Leave dem wizards alone...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||It was a stupid wizard thing -- geez...I think Microsoft should leave
the wizarding to Harry Potter...
Thanks for your quick and professional answer!
-Greg
Tracy McKibben wrote:
> Greg wrote:
> > Guess I believe it was -- I was using some sort of Wizard for my first
> > few jobs until I got my feet wet w/adding jobs w/o using a Wizard....
> >
> > I'll let you know what I find out.
> Good man!! Leave dem wizards alone...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Can't Delete Job

Hello:
I've got an old job I am trying to delete from my SQL Server 2005.
Everytime I try to delete this, i get the following error:
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occred in the database "msdb", table
"dbo.sysmainplan_subplans", column 'job_id'.
I know what an FK is, and why the job can't be deleted, but how do I
resolve this? How can I delete this job?Greg wrote:
> Hello:
> I've got an old job I am trying to delete from my SQL Server 2005.
> Everytime I try to delete this, i get the following error:
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occred in the database "msdb", table
> "dbo.sysmainplan_subplans", column 'job_id'.
> I know what an FK is, and why the job can't be deleted, but how do I
> resolve this? How can I delete this job?
>
Was the job created by a maintenance plan? Looks like it might have
been, judging from the FK reference. You'll probably have to go through
the maintenance plan to delete the job.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Guess I believe it was -- I was using some sort of Wizard for my first
few jobs until I got my feet wet w/adding jobs w/o using a Wizard....
I'll let you know what I find out.
-Greg
Tracy McKibben wrote:
> Greg wrote:
> Was the job created by a maintenance plan? Looks like it might have
> been, judging from the FK reference. You'll probably have to go through
> the maintenance plan to delete the job.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Greg wrote:
> Guess I believe it was -- I was using some sort of Wizard for my first
> few jobs until I got my feet wet w/adding jobs w/o using a Wizard....
> I'll let you know what I find out.
Good man!! Leave dem wizards alone...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||It was a stupid wizard thing -- geez...I think Microsoft should leave
the wizarding to Harry Potter...
Thanks for your quick and professional answer!
-Greg
Tracy McKibben wrote:
> Greg wrote:
> Good man!! Leave dem wizards alone...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Can't debug Script tasks

After upgrading to CTP16 (Sept.), I can't seem to debug my script tasks. Everytime I run the package with a breakpoint in script task I get following error: "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience. "

If I remove the breakpoint the scrip task runs successfully. So my question is how do I debug a script task with CTP 16?
As per my knowledge, there was no debugging support for script component.
So, you are left with few options like MessageBox.Show or rowcount etc.

Don't know if debugging support is there in sept/nov versions.

hth,
Nitesh|||No he said script task not script component and the script task does indeed support debugging.

As for the problem, do you get any error information in the error pane or progress pane. Do you get a minidump in 90\shared\ErrorDumps?

Thanks,
Matt|||Thank you for you reply Matt. No. I do not get any error info in error pane, output windows, or errordumps folder. I just get a dialog box with the error message listed above.

My Script task is set to Precompile and all the other properties are deafulted. I was under the impression that I would only get the error when there was syntax or logic problem, however, that's not true since I can take the breakpoint out and the script runs successfully.|||

If you set precompile to false then open and save the script does that make the breakpoints work or do you still get the same problem?

Thanks,
Matt

|||I have tried setting the precompile to false and it does break. However, it's not consistant. I guess CTP16 still has debugger issues hope they fix it in sql 2005 rel.

Can't Debug a script task

After upgrading to CTP16 (Sept.), I can't seem to debug my script task. Everytime I run the package with a breakpoint in script task I get following error: "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience. "

If I remove the breakpoint the scrip task runs successfully. So my question is how do I debug a script task with CTP 16?

This should be posted to SQL Server Integration Services. Please acknowledge and I'll move the thread to the appropriate group.

can''t connect to local user instance

Just when I think I have this stuff figured out, it bites me back everytime.

I'm

trying to deploy an mdf out to a different machine, and attached to it with local user instance. I connect without problem from my development

machine with a local user instance, which also has Express Manager resident,

and I can connect to a server instance without problem.

What I can't do is

copy the .mdf database over to another workstation, which has Sql Native

Client installed, and connect to the database using a local user

instance! I can connect to a server instance without problem from this

other workstation. Here's my connect string for local user instance

that works fine from my dev machine:

Provider=SQLNCLI.1;Persist

Security Info=False;Integrated Security=SSPI;Data

Source=.\sqlexpress;AttachDBFileName=<full path_name and mdf

filename>;User Instance=true;

The error I get upon trying to connect with other stations is:

Error -2147467259
Database not found or cound not connect to database

I've

tried this every way I know how. I've copied the database from my dev

machine both with and without having detached the database from the

local instance. I've tried detaching from a server instance and copying

the file over. Nothing works, and I've done this before! What gives with this thing?

Rick

Hi,

is SQL Server Service allowed to access the datafiles ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Jens ... How can tell this? What service should I examine? I don't see any reference to the Sql Native client, other than I know it's installed.

I thought this process consisted of:

- install the Sql Native Client on target machine
- put a local copy of the database on target machine
- connect to the mdf with a local user instance

As I said, I can connect to remote server database from the machine. The folder names differ from my development machine to the target machine, but that shouldn't make difference, should it? I will say that in Sql Express Manager on my dev machine (which works), the full path and database name (i.e..c:\_source\project\mydata.mdf) shows in the database tree.

Rick|||

Hi Rick,

SQL Express does not allow attaching database from a UNC or mapped drive. It wasn't totally clear, but it reads like that what you're trying to do. Also, you can not connect to a User Instance on a different machine as User Instances only support local named pipes connections.

Mike

|||Nevermind. I'm apparently having a mental episode and forgot the one vital requirement of installing SqlExpress on the target instead of just the Sql Native Client. Hadn't had to do this in a while since I've been hitting a server for Sql Express databases. Sorry!

Rick

can't connect to local user instance

Just when I think I have this stuff figured out, it bites me back everytime.

I'm

trying to deploy an mdf out to a different machine, and attached to it with local user instance. I connect without problem from my development

machine with a local user instance, which also has Express Manager resident,

and I can connect to a server instance without problem.

What I can't do is

copy the .mdf database over to another workstation, which has Sql Native

Client installed, and connect to the database using a local user

instance! I can connect to a server instance without problem from this

other workstation. Here's my connect string for local user instance

that works fine from my dev machine:

Provider=SQLNCLI.1;Persist

Security Info=False;Integrated Security=SSPI;Data

Source=.\sqlexpress;AttachDBFileName=<full path_name and mdf

filename>;User Instance=true;

The error I get upon trying to connect with other stations is:

Error -2147467259
Database not found or cound not connect to database

I've

tried this every way I know how. I've copied the database from my dev

machine both with and without having detached the database from the

local instance. I've tried detaching from a server instance and copying

the file over. Nothing works, and I've done this before! What gives with this thing?

Rick

Hi,

is SQL Server Service allowed to access the datafiles ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Jens ... How can tell this? What service should I examine? I don't see any reference to the Sql Native client, other than I know it's installed.

I thought this process consisted of:

- install the Sql Native Client on target machine
- put a local copy of the database on target machine
- connect to the mdf with a local user instance

As I said, I can connect to remote server database from the machine. The folder names differ from my development machine to the target machine, but that shouldn't make difference, should it? I will say that in Sql Express Manager on my dev machine (which works), the full path and database name (i.e..c:\_source\project\mydata.mdf) shows in the database tree.

Rick|||

Hi Rick,

SQL Express does not allow attaching database from a UNC or mapped drive. It wasn't totally clear, but it reads like that what you're trying to do. Also, you can not connect to a User Instance on a different machine as User Instances only support local named pipes connections.

Mike

|||Nevermind. I'm apparently having a mental episode and forgot the one vital requirement of installing SqlExpress on the target instead of just the Sql Native Client. Hadn't had to do this in a while since I've been hitting a server for Sql Express databases. Sorry!

Rick