Hello
I've just heard that Remote Debugging should be possible in SSIS, but how ?
Some of the projects we run require a lot of memory and it's sometimes slow to debug on the local machine ?
Yes i know i can reduce the input rows, but in some cases i need all the data for testing.
Does anyone know how to remote debug ?
Do you have Visual Studio installed?
-Satya SKJ
SQL Server MVP
|||Yes|||And then ?|||cgpl,
Just to clarify, by remote debugging I assume you mean that you want to make a package execute on a remote machine whilst seeing things turn green/yellow/red on your local machine. Is that correct?
As far as I know, that isn't possible. But don't take my word for it. Where did you hear that it WAS possible?
-Jamie
|||green/yellow/red yes
We had a meeting with Kevin Cox from Microsoft who told that remote debugging was possible (the way i understood it). Don't know if you know him, but he told that he would look in to it.
|||No, I haven't heard of Kevin. if you hear anything back I'd be keen to hear it as well.
TIA
-Jamie
|||SSIS does not implement remote debugging. It was considered, but it was too costly to do. Maybe in the next version, if we'll have time.|||If possible, core be able to debug a script component task too...|||We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
|||MarcvdW wrote: We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
Marc,
If you want this then the place to ask for it is http://connect.microsoft.com/sqlserver/feedback
-Jamie
|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.|||MarcvdW wrote: Thanks Jamie, I wasn't aware of this option. I posted my feedback.
cool. Could you put the link up here? The more people that add their weight to it the more likely it is to happen. I will certainly add some comments.
|||https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262144
Here it is.
Marc
No comments:
Post a Comment