These days we just call them "bosses". 🙂

Great question!

Now, that just makes me curious 😀

Steve Jones - Editor (9/20/2010)

---

The deployment thing is an excuse. You could easily forget to deploy anything, and code hidden in packages is hard to find. It's also not reusable...

Doug Lane (9/20/2010)

---

When someone decides a column needs renaming, the risk of forgetting to deploy a sproc will seem minimal compared to having to open all the affected packages, edit...

In our environment they are against using stored procedures, for the simple reason that if you deploy your SSIS packages, you could forget to deploy your stored procedures. And then...

Just for curiosity: what was the issue? (and how did you solve it?)

Good question. Keep 'em coming!

Allright, it is time to dive into the details.

How did you set-up your packages? What tasks/components did you use? What connectors did you use? What are the expressions/variables/package configurations that...

You have two options:

* read everything as string, replace the NULL strings and then convert everything to the appropriate datatype.

* use a script task to read the file and replace...

If you write the data to a table, what are the actual values that you get?

CirquedeSQLeil (9/16/2010)

---

Jeff's response should help you fix that. You can use the convert function in TSQL to change the int data type to a varchar or char (string) datatype...

Are you running in 32-bit or in 64-bit mode?

Good question, but a real easy one since all the rounding questions of Hugo Kornelis. 🙂

It would've been more a challenge if you used 3.2 or 3.0, as someone already...

tgarber (9/16/2010)

---

Has anyone resolved this problem OTHER than switching away from the SQL Server Destination? I've seen lots of posts about this and the "solution" seems to be to...