December 29, 2009 at 2:54 pm
:alien:
Hello,
For background purposes, I am a 20+ year IT vet from the mainframe world migrating to and transferring to the Darkside (as my mainframer friends scold me!!). I am on a contract to hire into a SQL Server/.NET environment while I run and clean up their COBOL side (MF Net Express) as the lone Developer and administrator for their COBOL system. Perk is I get to learn the .NET side of the shop as well and I am starting to get my feet wet.
I am quite efficient in SQL Code/Application calls from 20 years of DB2 and other relational DB's over the years, but not the administering/DBA aspect of SQL Server and of course fun new concepts like SSIS, thus I am here to ask advice on just that.
I have my first bigger project where they want me to take some audit files dumped from a production machine in CSV double quote separated fields format and load them into a SQL table. I have the basics of SSIS identified to do the pulling of the files, looping through the folder, and then loading the fields to the SQL table I designed, that was not too bad and fun setting up and playing with! I also found how to remove the double quotes separator using Flat File Connection Manager Editor. But when it comes to moving the files after processed, and then deleting them after a 30 day retention period, it gets a little less obvious and more complicated to get my mind around!
I have looked at the File System Tasks and think that may be part of the solution. I also have looked at the Scripting and know that it too will most likely have to be in the mix as well to get creation dates in order to pull this off.
So I think my most pressing question is the best way to get the files in the processed folder examined and then deleted after 30 days beyond their creation date (IE. a 30 day retention period).
I have seen bits and pieces of things close to what I need on other postings in other forums, but not really the pieces together in a package as an overall all inclusive solution.
So any advice on moving files after each is processed (assuming using of File Sytem Task as an Event??) and then getting the file creation date and checking for 30 day retention would be much appreciated. I think I have found bits and pieces that will do what I need, but not necesarily how to put them together in the overall scheme of the package/project and have them play nicely togther, or even if they can all work together?? :unsure:
Sorry so long but wanted to set the stage as best I could. Thanx in Advance for any insight and expertise that can be given!!
December 30, 2009 at 4:21 am
This was removed by the editor as SPAM
December 30, 2009 at 8:51 am
Thanx for the feedback. But unfortunately I was unable to open the package receving:
TITLE: Microsoft Visual Studio
------------------------------
The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
------------------------------
ADDITIONAL INFORMATION:
The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
They are on SQL Verver 2005 and VS 2008, if that makes any difference??
December 30, 2009 at 11:15 pm
This was removed by the editor as SPAM
December 31, 2009 at 10:12 am
Thanx for your patience! But this is the type of MS environment stuff that causes me confusion! I was able to figure out using the "Open with" to use the VS Selector option you mentioned (had never heard of it before then) and I got the XML version loaded. But from there, I did not understand what the next step was?
I saved it as a new package name. Then I opened up 2005 SQL Server BID and created a new package and tried to import in using the SSIS Package import when right clicking, but got confused with the Import Wizard which seemed to be more data orientated rather then getting a package imported?? I then tried to add the package I saved, but got same results.
I am obviously misunderstanding something or missing a step or doing something incorrect!!
Again, A BIG Thanx for your patience! The maneuvering around in the MS world still is not first nature and the different levels of packages vs. projects etc. are still confusing. I am supposed to get training soon which will be a big help!!!! But for now, am stumbling around in the dark on the specific details!!!!
Thanx!!
December 31, 2009 at 11:22 am
You don't import the package - you add it as an existing item to the new project. To do that, right-click on the Projects folder and select Add Existing Item. Since the item is a file, change the option (defaults to SQL Server), navigate to the file and select the .dtsx file.
Once it has been added, you can then view it as a regular SSIS package.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
December 31, 2009 at 12:06 pm
Thanx Jeffrey,
I tried that and got errors again. The one in the Main window is the same as before, but also go an error list this time (see attached) stating that the "Version number in the package is not valid" and other errors in same manner.
I am not sure what the versions it is talking about?? Is it the SQL Server or VS?? The package itself?? Or something else??
I am learning a lot! But still confused on some regards as to what is going on!!
Thanx Again Guys for your patience and insight! Much appreciated!!
December 31, 2009 at 12:34 pm
Okay - that is going to happen when the package was created using a version that is at a higher patch level than your system. So, your system is probably RTM version and the system that created the package was patched to SP1 (or some other greater version).
There are two updates that you need to perform - you need to update the SQL Server client tools to the latest service pack (SP3), and you need to apply the latest service pack for Visual Studio.
If that doesn't work - then I would suspect that the package was created using 2008.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 3, 2010 at 10:39 pm
This was removed by the editor as SPAM
January 4, 2010 at 7:02 am
stewartc-708166 (1/3/2010)
Yes, the package was created using SSIS 2008.given that this is a SQL Server 2008 forum....
Really? I read through the posts and see that the OP stated it was created in 2005 BIDS, even though it was posted in the 2008 forum. Either way, there is a version mismatch that needs to be corrected.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 4, 2010 at 7:28 am
This was removed by the editor as SPAM
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply