Having problems using Breakpoint in Script Task.

I am still pretty new to SSIS, SQL, and DOT NET. I came from the UNIX world. I have a SSIS package. On the Control Flow one of the Items I have is a Script Task. I was able to successfully set breakpoints in the Script Task and they worked fine.I could step through the script and check values in variables.Life was good.

Now something happened.I set the breakpoint, from the menu I select “start with debugging” and I get the following window:

-- -

Visual Studio Just-In-Time Debugger

An unhandled exception (‘System.Runtime.InteropServices.COMException’) occurred in DTAttach.exe [3380].

Possible Debuggers:

New instance of Microsoft CLR Debugger 2003

New instance of Visual Studio .NET 2003

New instance of Visual Studio 2005

[_] set the currently selected debugger as the default

[_] Manually choose the debugging engines

Do you want to debug using the selected debugger?

--

I have tried selecting Yes, but that doesn’t work.If I delete all breakpoints the package runs fine.I greatly appreciate your help.

You are not alone.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1846879&SiteID=1|||Thanks Phil. I found a work around for my problems and posted it on the thread you provided the link to above.

Hardware Configuration

I'm currently rebuilding an IBM server that I'd like to use as a SQL 7.0
database server. Two items I'd like some feedback on: when creating a new
volume (it's Windows 2000 Server) to host the databases, how important is
cluster (i.e. allocation unit) size? The volume I've created is 25 Gb.
Second, I'm using a RAID controller with hard drives which support
write-caching, with the two options being write-through and write-back. I
understand write-caching isn't the most desirable thing with SQL? Any and
all input on this is much appreciated.
steve.Steve,
In general, if the hard disk of the computer has a write-caching disk
controller, disable it. Unless a write-caching disk controller is designed
specifically for a database (basically battery-backed), it can seriously
threaten SQL Server data integrity.
hth
Quentin
"molsonexpert" <imdrunk@.work.ca> wrote in message
news:uKwLOyisEHA.2788@.TK2MSFTNGP09.phx.gbl...
> I'm currently rebuilding an IBM server that I'd like to use as a SQL 7.0
> database server. Two items I'd like some feedback on: when creating a new
> volume (it's Windows 2000 Server) to host the databases, how important is
> cluster (i.e. allocation unit) size? The volume I've created is 25 Gb.
> Second, I'm using a RAID controller with hard drives which support
> write-caching, with the two options being write-through and write-back. I
> understand write-caching isn't the most desirable thing with SQL? Any and
> all input on this is much appreciated.
> steve.
>

Hardware Configuration

I'm currently rebuilding an IBM server that I'd like to use as a SQL 7.0
database server. Two items I'd like some feedback on: when creating a new
volume (it's Windows 2000 Server) to host the databases, how important is
cluster (i.e. allocation unit) size? The volume I've created is 25 Gb.
Second, I'm using a RAID controller with hard drives which support
write-caching, with the two options being write-through and write-back. I
understand write-caching isn't the most desirable thing with SQL? Any and
all input on this is much appreciated.
steve.
Steve,
In general, if the hard disk of the computer has a write-caching disk
controller, disable it. Unless a write-caching disk controller is designed
specifically for a database (basically battery-backed), it can seriously
threaten SQL Server data integrity.
hth
Quentin
"molsonexpert" <imdrunk@.work.ca> wrote in message
news:uKwLOyisEHA.2788@.TK2MSFTNGP09.phx.gbl...
> I'm currently rebuilding an IBM server that I'd like to use as a SQL 7.0
> database server. Two items I'd like some feedback on: when creating a new
> volume (it's Windows 2000 Server) to host the databases, how important is
> cluster (i.e. allocation unit) size? The volume I've created is 25 Gb.
> Second, I'm using a RAID controller with hard drives which support
> write-caching, with the two options being write-through and write-back. I
> understand write-caching isn't the most desirable thing with SQL? Any and
> all input on this is much appreciated.
> steve.
>

Hardware Configuration

I'm currently rebuilding an IBM server that I'd like to use as a SQL 7.0
database server. Two items I'd like some feedback on: when creating a new
volume (it's Windows 2000 Server) to host the databases, how important is
cluster (i.e. allocation unit) size? The volume I've created is 25 Gb.
Second, I'm using a RAID controller with hard drives which support
write-caching, with the two options being write-through and write-back. I
understand write-caching isn't the most desirable thing with SQL? Any and
all input on this is much appreciated.
steve.Steve,
In general, if the hard disk of the computer has a write-caching disk
controller, disable it. Unless a write-caching disk controller is designed
specifically for a database (basically battery-backed), it can seriously
threaten SQL Server data integrity.
hth
Quentin
"molsonexpert" <imdrunk@.work.ca> wrote in message
news:uKwLOyisEHA.2788@.TK2MSFTNGP09.phx.gbl...
> I'm currently rebuilding an IBM server that I'd like to use as a SQL 7.0
> database server. Two items I'd like some feedback on: when creating a new
> volume (it's Windows 2000 Server) to host the databases, how important is
> cluster (i.e. allocation unit) size? The volume I've created is 25 Gb.
> Second, I'm using a RAID controller with hard drives which support
> write-caching, with the two options being write-through and write-back. I
> understand write-caching isn't the most desirable thing with SQL? Any and
> all input on this is much appreciated.
> steve.
>

Handling nulls in calculated rport items

Hello,
How do I block null values from displaying "#Error" when I format a
datetime.
dbuchananWould an IIF statement not work in the expression
for example:
=IIF (Fields!Date.Value = "NULL", "",Fields!Date.Value)
This would bring up a blank space (or whatever you want it the output to be)
if the value is NULL, otherwise it just brings out the value.
Im fairly new to all of this so its just a thought.
"dbuchanan" wrote:
> Hello,
> How do I block null values from displaying "#Error" when I format a
> datetime.
> dbuchanan
>|||Theoretically yes that would work but in practice it doesn't as you have to
write
=iif(Fields!Date.Value is system.dbnull.Value, "", Fields!Date.Value)
otherwise deal with it in the initial query.
Greg
"Robert Seal" <RobertSeal@.discussions.microsoft.com> wrote in message
news:AB5060A6-88AE-4FB4-A224-C1C548418EFB@.microsoft.com...
> Would an IIF statement not work in the expression
> for example:
> =IIF (Fields!Date.Value = "NULL", "",Fields!Date.Value)
> This would bring up a blank space (or whatever you want it the output to
> be)
> if the value is NULL, otherwise it just brings out the value.
> Im fairly new to all of this so its just a thought.
> "dbuchanan" wrote:
>> Hello,
>> How do I block null values from displaying "#Error" when I format a
>> datetime.
>> dbuchanan
>>