Hi,
I have a customer who wants to send a fixed width file with 1400 characters per row.
Before I tell the 'OK', I was wondering if there is any limit to the length of rows when using a DTS .txt source.
Anyone know?
Thanks!You have a sql row limit of 8060
Why not bcp the data in?
Does the process have to be repeated?|||My "personal best" was a smidgeon over 20 Kb per row of text. 2000 ten digit integers with a space between them per row.
-PatP|||OK, so 1400 characters is pretty puny.
This will be a weekly feed that begins with an FTP'd file and ends only after updating all of that company's organization structure, employees, employee contacts, etc. and then emailing a summary of the results and any errors to our DBA. Currently we run a bunch of these as DTS as it is easy to have some tasks be custom to the specific customer and others be based on stock scripts.
We're not looking forward to moving to Yukon. I hear that you can't upgrade DTS.
Thanks for the info guys!|||That's not true about upgrading DTS. The problem is HOW you have to upgrade. You basically take the whole VBScript it produces and plop it in there to run. It will run, but you lose all the graphical interface. I'm hoping they've changed that. I haven't really spent time looking at IS since the early notes on it. Too busy looking at all the other kewl features.|||Sounds like this will not go off without some triage and repair, particularly in our more sophisticated, looping DTS where we enable and disable tasks based on the data.|||If you mean data driven tasks, oh boy will you be excited.
There are some features that just plain won't be portable (the VBA/Active X and UDL in particular), others will require significant "triage", but most features ought to be relatively portable. I won't take any bets until I see RC, because there are so many things that aren't "final" yet.
-PatP|||I agree that we won't know until we've started to move our own stuff over.
But I'm betting it will be seriously annoying!
No comments:
Post a Comment