Debugging Parent / Child Packages

Hi there,

I have a Business Intelligence project containing 4 packages. One of the packages is a parent package that just runs the other 3 packages sequentially (passing in variables via Package Configurations).

When I set the properties of the Execute Package tasks in the parent package, it seems that I can only select SQL Server or File System locations for the child packages.

What I want to do is for the parent to run the packages in the Visual Studio Project so that I can debug the whole process. I don't want to be bothered deploying the child packages so that I can run them from the parent, at least not while I am debugging the whole process.

How do I get the children to run within Visual Studio as well as the parent? I can't for the life of me find anything on the MSDN about this.

Many thanks in advance.

Richard F

I am not sure what your problem is. If I execute the parent package in BIDS; all children packages are open and execute in debug mode as well. At least that is the behavior I get when storing the packages in .dtsx files; I don't know if the behavior is diffrent when storing them in the DB.

|||Hi there,

Thanks for your reply.

Can I ask what you do when you create the parent package?

I did the following:
- Added an "Execute Package" task to the parent
- Edited properties of the task
- Set the location to File System
- Added a new connection manager of type File Connection and pointed this to the location of the child package in the development folder (i.e. the folder used by the VS.NET package project)
- Set the connection of the parent package equal to this connection manager

Then when running the parent package in VS.NET, it did not step into the child package as you described, and to be honest I'm not really surprised since at no point when specifying the child package from the parent did I tell it to run in VS.NET.

How did you reference the child package from the parent?

Many thanks in advance.

Richard F|||It's real simple. In the parent package, use an Execute Package task to call your child package. Double click on the Execute Package task, and select the package you want to run.

Then, when you are in the parent package, you can run the debug (start button, or F5, I think) which will start the child package accordingly.

Debugging Parent / Child Packages

Hi there,

I have a Business Intelligence project containing 4 packages. One of the packages is a parent package that just runs the other 3 packages sequentially (passing in variables via Package Configurations).

When I set the properties of the Execute Package tasks in the parent package, it seems that I can only select SQL Server or File System locations for the child packages.

What I want to do is for the parent to run the packages in the Visual Studio Project so that I can debug the whole process. I don't want to be bothered deploying the child packages so that I can run them from the parent, at least not while I am debugging the whole process.

How do I get the children to run within Visual Studio as well as the parent? I can't for the life of me find anything on the MSDN about this.

Many thanks in advance.

Richard F

I am not sure what your problem is. If I execute the parent package in BIDS; all children packages are open and execute in debug mode as well. At least that is the behavior I get when storing the packages in .dtsx files; I don't know if the behavior is diffrent when storing them in the DB.

|||Hi there,

Thanks for your reply.

Can I ask what you do when you create the parent package?

I did the following:
- Added an "Execute Package" task to the parent
- Edited properties of the task
- Set the location to File System
- Added a new connection manager of type File Connection and pointed this to the location of the child package in the development folder (i.e. the folder used by the VS.NET package project)
- Set the connection of the parent package equal to this connection manager

Then when running the parent package in VS.NET, it did not step into the child package as you described, and to be honest I'm not really surprised since at no point when specifying the child package from the parent did I tell it to run in VS.NET.

How did you reference the child package from the parent?

Many thanks in advance.

Richard F|||It's real simple. In the parent package, use an Execute Package task to call your child package. Double click on the Execute Package task, and select the package you want to run.

Then, when you are in the parent package, you can run the debug (start button, or F5, I think) which will start the child package accordingly.

Debugging In Business Intelligence Studio

I've been trying to get debugging working in BIS, but I can't seem to do it. If I am using the full blown version of Visual Studio I don't have any problems. I have read that TSQL debugging is limited to Visual Studio Professional or higher, however, there is no indication where Business Intelligence Studio is in the Visual Studio continuum. I don't know if it is considered lower or higher than Professional.

Anyway, if it is possible to use BIS for debuggin TSQL, then how does one go about doing it? I've have been competely unsuccessful to date. I have attempted to install and use the Remote Debugger, but that hasn't worked for me. So, I'm left to conclude that BIS doesn't support TSQL debugging.

Microsoft, Can you please give the final word here? This would be very nice to know one way or another.

Thanks,

DCB99

Hi dcb99,

The 'official' word (but not final) is the material you read with respect to TSQL debugging being limited to VS Professional (or higher) is correct. BI or No BI plays no part in the equation. A debugger (not the TSQL debugger of years passed) ships with VS Pro and above.

The final word is; we have it on our plate, for the next shipping version of SQL Server to get a robust debugging experience baked into the DBA - BIS experience.

Terrence Nevins

SQL Server Program Manager

|||

Terrance,

Thanks for your response. However, it doesn't quite answer my question I don't think. If I do not install a version of Visual Studio apart from installing SQL Server 2005, does BIS support debugging? I guess I'm reading that your email says it does not support debugging.

Thanks in advance.

dcb99

Debugging In Business Intelligence Studio

I've been trying to get debugging working in BIS, but I can't seem to do it. If I am using the full blown version of Visual Studio I don't have any problems. I have read that TSQL debugging is limited to Visual Studio Professional or higher, however, there is no indication where Business Intelligence Studio is in the Visual Studio continuum. I don't know if it is considered lower or higher than Professional.

Anyway, if it is possible to use BIS for debuggin TSQL, then how does one go about doing it? I've have been competely unsuccessful to date. I have attempted to install and use the Remote Debugger, but that hasn't worked for me. So, I'm left to conclude that BIS doesn't support TSQL debugging.

Microsoft, Can you please give the final word here? This would be very nice to know one way or another.

Thanks,

DCB99

Hi dcb99,

The 'official' word (but not final) is the material you read with respect to TSQL debugging being limited to VS Professional (or higher) is correct. BI or No BI plays no part in the equation. A debugger (not the TSQL debugger of years passed) ships with VS Pro and above.

The final word is; we have it on our plate, for the next shipping version of SQL Server to get a robust debugging experience baked into the DBA - BIS experience.

Terrence Nevins

SQL Server Program Manager

|||

Terrance,

Thanks for your response. However, it doesn't quite answer my question I don't think. If I do not install a version of Visual Studio apart from installing SQL Server 2005, does BIS support debugging? I guess I'm reading that your email says it does not support debugging.

Thanks in advance.

dcb99

Debug sp from Business Intelligence Dev Studio?

Is there a way to debug SQL Server 2005 stored procedures from within BI
Studio? I don't see any way to do it, but may be missing something.
I can do it from a VS 2005, but some systems don't have that installed.
Thanks,
TomHi ,
I don't think you can debug .NET sp without VS 2005 Pro or Team suite. You
should be able to debug a TSQL sp without VS (but I haven't checked) as it
was there as a feature in SQL 2000
kind regards
Greg O
--
Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
AGS SQL 2005 Utilities, over 20+ functions
http://www.ag-software.com/?tabid=38
"TomT" <tomt@.newsgroup.nospam> wrote in message
news:B633E6CF-F829-4A63-A2AA-8C5C219E75A0@.microsoft.com...
> Is there a way to debug SQL Server 2005 stored procedures from within BI
> Studio? I don't see any way to do it, but may be missing something.
> I can do it from a VS 2005, but some systems don't have that installed.
> Thanks,
> Tom|||I don't think the T-SQL debugger is also there in SSMS.
--
HTH,
SriSamp
Email: srisamp@.gmail.com
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
"GregO" <grego@.community.nospam> wrote in message
news:ebLSm2y7FHA.3976@.TK2MSFTNGP15.phx.gbl...
> Hi ,
> I don't think you can debug .NET sp without VS 2005 Pro or Team suite.
> You should be able to debug a TSQL sp without VS (but I haven't checked)
> as it was there as a feature in SQL 2000
> kind regards
> Greg O
> --
> Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
> AGS SQL 2005 Utilities, over 20+ functions
> http://www.ag-software.com/?tabid=38
> "TomT" <tomt@.newsgroup.nospam> wrote in message
> news:B633E6CF-F829-4A63-A2AA-8C5C219E75A0@.microsoft.com...
>|||Hello,
I think you need to use Visual Studio 2005 to debug.
You may refer to the following information:
http://www.microsoft.com/technet/co...SQL_101204.mspx
*Q: What kind of debugging options do we have with managed code? Do we have
to attach a debugger to the SQL Server process?
A: Visual Studio 2005 would provide support for debugging Transact SQL and
CLR routines that are registered / running in SQL Server. The debugging in
SQL Server follows per connection model. You can either debug the objects
directly using Visual Studio Server Explorer or attach a client process and
see / debug activities on the connections that client process makes. The
debug engine inside sql server would provide an integrated t-sql / clr
debugging experience.*
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Waht about TSQL debugging?
Greg
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:ywy6NV07FHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hello,
> I think you need to use Visual Studio 2005 to debug.
> You may refer to the following information:
> http://www.microsoft.com/technet/co...SQL_101204.mspx
> *Q: What kind of debugging options do we have with managed code? Do we
> have
> to attach a debugger to the SQL Server process?
> A: Visual Studio 2005 would provide support for debugging Transact SQL and
> CLR routines that are registered / running in SQL Server. The debugging in
> SQL Server follows per connection model. You can either debug the objects
> directly using Visual Studio Server Explorer or attach a client process
> and
> see / debug activities on the connections that client process makes. The
> debug engine inside sql server would provide an integrated t-sql / clr
> debugging experience.*
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||That's what I was afraid of. It seems then that a customer buying SQL Server
2000 can debug sp's via Query Analyzer at no additional cost, but a customer
buying SQL 2005 will have to buy VS2005 to be able to do this.
Hopefully this functionality will be added back in to the product....
"Sophie Guo [MSFT]" wrote:

> Hello,
> I think you need to use Visual Studio 2005 to debug.
> You may refer to the following information:
> http://www.microsoft.com/technet/co...SQL_101204.mspx
> *Q: What kind of debugging options do we have with managed code? Do we hav
e
> to attach a debugger to the SQL Server process?
> A: Visual Studio 2005 would provide support for debugging Transact SQL and
> CLR routines that are registered / running in SQL Server. The debugging in
> SQL Server follows per connection model. You can either debug the objects
> directly using Visual Studio Server Explorer or attach a client process an
d
> see / debug activities on the connections that client process makes. The
> debug engine inside sql server would provide an integrated t-sql / clr
> debugging experience.*
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hello,
I understand your concerns. However, this is how SQL server 2005 is
designed. I suggest that you access the following web site which provide
good information about Debugging in SQL Server 2005:
Demystifying Debugging in SQL Server 2005
http://www.windowsitpro.com/SQLServ.../SQLServer_4775
4.html
How to: Debug a SQL CLR Stored Procedure
http://msdn2.microsoft.com/en-us/library/ms165051.aspx
How to: Enable SQL Server 2005 Debugging
http://msdn2.microsoft.com/en-us/library/s0fk6z6e.aspx
Creating SQL Server 2005 Objects in Managed Code
http://msdn2.microsoft.com/en-us/library/6s0s2at1.aspx
SQL Server 2005 Debugging
http://www.sqljunkies.com/WebLog/ni...08/04/3758.aspx
Note: This response contains a reference to a third party World Wide Web
site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Not labour a point but we are talking about TSQL debugging in this part. We
understand CLR debugging is a different matter.
What about TSQL debugging?
kind regards
Greg O
Need to document your databases. Use the first and still the best AGS SQL
Scribe
http://www.ag-software.com
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:0P6LLOB8FHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hello,
> I understand your concerns. However, this is how SQL server 2005 is
> designed. I suggest that you access the following web site which provide
> good information about Debugging in SQL Server 2005:
> Demystifying Debugging in SQL Server 2005
> http://www.windowsitpro.com/SQLServ...y/ms165051.aspx
> How to: Enable SQL Server 2005 Debugging
> http://msdn2.microsoft.com/en-us/library/s0fk6z6e.aspx
> Creating SQL Server 2005 Objects in Managed Code
> http://msdn2.microsoft.com/en-us/library/6s0s2at1.aspx
> SQL Server 2005 Debugging
> http://www.sqljunkies.com/WebLog/ni...08/04/3758.aspx
> Note: This response contains a reference to a third party World Wide Web
> site. Microsoft is providing this information as a convenience to you.
> Microsoft does not control these sites and has not tested any software or
> information found on these sites; therefore, Microsoft cannot make any
> representations regarding the quality, safety, or suitability of any
> software or information found there. There are inherent dangers in the use
> of any software found on the Internet, and Microsoft cautions you to make
> sure that you completely understand the risk before retrieving any
> software
> from the Internet.
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>|||Hello,
Based on my research, I didn't find the debug button in the Server
Management Studio. You can refer to the information on the following
article:
Demystifying Debugging in SQL Server 2005
http://www.windowsitpro.com/SQLServ.../SQLServer_4775
4.html
*To debug a T-SQL stored procedure in SQL Server 2000, you use the Query
Analyzer. You simply right-click the stored procedure and choose Debug. In
SQL Server 2005, SQL Server Management Studio replaces the Query Analyzer.
It's logical to assume that to debug a T-SQL stored procedure in SQL Server
2005, you simply right-click a stored procedure and select Management
Studio's debug feature. Unfortunately, it's not that straightforward. A
debug option is nowhere to be found.
To debug T-SQL stored procedures in SQL Server 2005, you use the Visual
Studio 2005 development environment.*
I suggest that you refer to the information I posted before.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||v-sguo@.online.microsoft.com (Sophie Guo [MSFT]) wrote in
news:eFNPe0B8FHA.832@.TK2MSFTNGXA02.phx.gbl:

> Hello,
> Based on my research, I didn't find the debug button in the Server
> Management Studio. You can refer to the information on the following
> article:
> Demystifying Debugging in SQL Server 2005
> http://www.windowsitpro.com/SQLServ.../47754/SQLServe
r
> _4775 4.html
> *To debug a T-SQL stored procedure in SQL Server 2000, you use the
> Query Analyzer. You simply right-click the stored procedure and choose
> Debug. In SQL Server 2005, SQL Server Management Studio replaces the
> Query Analyzer. It's logical to assume that to debug a T-SQL stored
> procedure in SQL Server 2005, you simply right-click a stored
> procedure and select Management Studio's debug feature. Unfortunately,
> it's not that straightforward. A debug option is nowhere to be found.
> To debug T-SQL stored procedures in SQL Server 2005, you use the
> Visual Studio 2005 development environment.*
>
Yup, regardless if you want to debug sp's based on CLR code or sp's
based on "pure" T-SQL you use Visual Studio 2005. Personally I think it
wasn't the best decision MS has done, but that's the way it is.
Oh BTW, there will be a follow-up article to the one mentioned above. In
this I'll discuss CLR debugging inside SQL Server.
Niels
****************************************
**********
* Niels Berglund
* http://staff.develop.com/nielsb
* nielsb@.no-spam.develop.com
* "A First Look at SQL Server 2005 for Developers"
* http://www.awprofessional.com/title/0321180593
****************************************
**********