DSXchange

I concur with Arnd.

Yes.

This is the post I referred to earlier. There are others if you search.

viewtopic.php?t=150112

Create a file --Not selected hence options disabled to chosse hash method. Or to choose a starting size. So you start off with the smallest possible hashed file and then proceed to write 814 million records to it. It spends the majority of your 13 hours basically resizing and expanding the hashed f...

It replaces the Sequential File stage as the target of the job.

Clarify something. If you are in 'Insert then Update' mode then the insert must fail for the update to be attempted. And it will only fail if it violates a unique constraint. However, which part of this is your issue - the fact that new records are not getting inserted or that you are having an upda...

So we're not discussing 'importing' Excel data but rather reading a .csv flat file that happened to come from Excel. OK, fine... but as noted you'll need to provide specific details about your requirements - examples of both your input data and what you need your output to look like would be an exce...

Let's start with what you've tried and what issue(s) you are having.

I would think you would be firmly in your official support provider's hands for help with this one. If it is truly a known problem then there could very well be a patch for it.

Well... they are a little tricky to use. Check the Server Job Developer's Guide manual for the official description and do an exact search here for 'folder stage' to see what has been discussed here. Seem to recall one such conversation just last month...

I checked the documentation before using it and I understood what you said but did not work. I will try again but the problem is not this. Sorry, I should have made my response more clear. I wasn't trying to solve your problem directly, just pointing out an error in your expression with the use of ...

Basically yes as long as your field is a string. Depending on your version a third parameter is optionally available to tell it the format of the string, if appropriate to the data type. This is all documented, best to check there if you are unsure.

mmanes wrote:I tested it on other jobs and it works perfectly

That doesn't make it correct. Learn how the functions work and leverage them correctly to minimize unintended problems.

mmanes wrote:I tested it on other jobs and it works perfectly

That doesn't make it correct. Learn how the functions work and leverage them correctly to minimize unintended problems.

mmanes wrote:IsValid("timestamp", StringToTimestamp(<field>, "%yyyy%mm%dd%hh%nn%ss"))

IsValid() checks a string to see if it can be successfully converted to the target data type. If it is valid, then you convert it - you do not do it inside the validity check.

... and be very careful with your edits. All it takes is a small mistake in the change to corrupt your project - been there, done that, got the t-shirt.