SSIS can't handle files like these. You'll need a script component to parse it.

A function has a fixed output in the sense that the metadata of the columns returned is known upfront. Functions are thus meant to return data.

Stored procedures however can do...

AndrewSQLDBA (9/9/2013)

---

I think that what you have on your website is not really what I need. I am looking for a command line for pulling the package from a SQL...

Nice question, thanks.

bob_balok (9/9/2013)

---

I have founds hundreds of answers to my questions or dilema of the moment and never had to post a question. The information is probably already there if...

You need to open the file and take a look yourself.

Typically the analysis (if there is any) of your import should contain these details.

You could also do it with some .net coding in an asynchronous script component.

You read the value from number and use it in a for loop.

In each iteration of the...

Wouldn't it be faster to transfer everything to SQL Server and then delete everything you don't need?

What a weird question 🙂

Personally, I'd go for the 2012 certificates.

They are a bit harder to get than the 2008 exams (you now have to do three exams), but you get to know the...

TheSQLGuru (9/6/2013)

---

Personally I would not use INTERSECT. It is a relatively new operator in SQL Server and thus could be exposed to some bugs and/or not have all the...

Mr. Kapsicum (9/6/2013)

---

Thanks for acknowledging my problem.

In a nutshell, i want a Script for my script task that delete all files...

What problems are you running into?

You can create a string variable in SSIS containing your SQL statement. Just add the IDs you extracted to this variable using an expression.

In the OLE DB Source, use the...

MarkusB (9/6/2013)

---

I hope I get it right now.

Create your package with two "file system tasks" connect them with an "on success" connection.

Then define a variable "sourcepath" and change the sourceconnection...