Viewing 15 posts - 166 through 180 (of 699 total)
Never seen that problem occur :/ Sorry
December 12, 2011 at 9:37 am
Are you sure the connection string that you're using is valid?
I have a similar package which I use to dynamically send the results of an SSIS package execution to different...
December 6, 2011 at 3:17 pm
Are you referring to the connection manager for the Flat File or for the OLE DB?
The OLE DB Connection Manager doesn't have an Advanced tab with Data Types, so I...
December 6, 2011 at 3:14 pm
Your best bet is to just use a stored procedure and run it either directly in the database or through an execute SQL task.
There's no reason to use SSIS for...
December 6, 2011 at 3:02 pm
There's lots of things you can try.
First, make sure your code is all optimised. That means, your SQL query that is loading the data only takes in the fields you...
December 2, 2011 at 11:46 am
you want to load the last 7 files which correspond to the two file names you mentioned?
take a look at this thread. it gives you the general idea that...
December 2, 2011 at 11:29 am
If you select your variable and then go to the properties window, you'll see it. Check this screenshot for more details
December 1, 2011 at 2:33 pm
I'd really strongly recommend that you instead do the processing using SSIS components. That's the whole point of using SSIS 😛 Pretty much everything you could do with the script...
December 1, 2011 at 2:29 pm
You want to change your variable to use an Expression, and then use the GETDATE() function to get the current date. As it stands you're hardcoding a variable and always...
December 1, 2011 at 2:08 pm
You're connecting to a SQL Server database? Just use the OLE DB Source as your component and follow the on-screen steps to connect, then use the SQL Command option as...
December 1, 2011 at 2:07 pm
The first set of errors aren't too important, though you usually should deal with them by putting in a data conversion task and fixing the inconsistencies.
The last one definitely should...
December 1, 2011 at 2:05 pm
The only way you can do it is to use the SQL Command option and update the rows one at a time. That's a really ugly solution though, especially if...
November 30, 2011 at 12:26 pm
The simplest solution, as far as I know, is to just not use the fixed width delimiter when doing your import.
I assume you have linebreaks as your row delimiter right?...
November 29, 2011 at 8:20 am
Try executing it like this:
DECLARE @DTExec VARCHAR(500)
SET @DTExec = 'dtexec /FILE "[file path]" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E'
-- Insert statements for procedure here
EXEC...
November 29, 2011 at 8:14 am
Directly from the .NET application?
I usually do it by having the DTEXEC command run through a stored proc so I can keep all SQL-related stuff in the database, but...
November 29, 2011 at 8:10 am
Viewing 15 posts - 166 through 180 (of 699 total)