|
|
|
Valued Member
 
Group: General Forum Members
Last Login: Today @ 12:52 PM
Points: 70,
Visits: 316
|
|
>>If the file is imported successfully then send email with message: The file is imported
This may help or at least give you the proper terminolgy for further research on your requirements.
http://msdn.microsoft.com/en-us/library/ms142165(SQL.90).aspx
http://www.developerdotstar.com/community/node/327
>>If there is now file to import send email with message: There isn’t any file to import
Lots of ways to do this, you could create an integer variable and increment for each loop. I would log each file into a table as I refered to earlier and then count the records.
>If the format of the file name is not as I described send email with message: Wrong file format.
>If there is a problem with data in the file send email with message: The file can not be imported
This is a difficult requirement. Saying the format is wrong for a package, well what does that mean, the package failed? Similarly its hard to say what the problem is with the data if it hasn't been imported.
You probably would have to validate the file before attempting import to see if its the 'right' format or if there is a 'problem' with the data.
I would email all error messages to get the best understanding of failure reasons. Perhaps you could categorize all possible error messages as 'bad format' or 'bad data' and email that.
|
|
|
|
|
SSC Rookie
Group: General Forum Members
Last Login: Today @ 4:58 AM
Points: 31,
Visits: 163
|
|
Thanks for your replay... I think this will give me an answer...
and... I agree with you about categorizing errors on the way as i described but... My PM want to see the result of the package, regarding the errors as I described...
Thanks to all for you help and i will investigate the links you give.
|
|
|
|
|
SSChampion
Group: General Forum Members
Last Login: Today @ 11:10 AM
Points: 18,344,
Visits: 12,357
|
|
Dr.D (11/6/2009)
It is not about a job interview nor university final exam nor homework. This is my task at work and i have 3 days to finish it. Yesterday was my firs day, so 2 days left 
Didn't say it was... was just advising you why (for other people, it has been) using the word "urgent" has become a bit of a taboo on this forum. 
As a side bar, I'm sorry they're forcing you to do this in SSIS... I do this type of stuff all in T-SQL because every time I turn around, I see someone having the same problems that you're currently having with it. I thought SSIS was supposed to make things easier and it doesn't appear to have.
--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
SSCrazy
Group: General Forum Members
Last Login: Today @ 2:07 PM
Points: 2,085,
Visits: 2,072
|
|
Jeff Moden (11/6/2009)
As a side bar, I'm sorry they're forcing you to do this in SSIS... I do this type of stuff all in T-SQL because every time I turn around, I see someone having the same problems that you're currently having with it. I thought SSIS was supposed to make things easier and it doesn't appear to have.
I agree. If one has no experience with any product as complex as SSIS, it seems a bit unfair.
If one is deeply familiar with T-SQL and bcp, it will obviously be easier and faster to develop a solution using those tools. Likewise, I could probably have a good stab at producing a solution entirely in batch files
SSIS is a very powerful tool - which is arguably also its greatest weakness. Like SSAS, SSRS, and CLR programming, SSIS is a whole separate product really. I know people that dedicate themselves to just one of those components, and make a good living at it.
So, my point is really that unless you have done extensive DTS work before, and are very famailiar with Visual Studio, and have the time to learn SSIS to a sufficiently deep level, you will probably find non-trivial tasks in SSIS an uphill struggle for a while.
That said, I have a lot of time for SSIS - it is worth learning, and is a great place to house most, if not all, or your ETL and other data transformation routines.
There are multiple valid ways to remove the epidermis of a felis domestica 
Paul
The quality of the answers is directly proportional to the quality of the question.
|
|
|
|
|
SSChampion
Group: General Forum Members
Last Login: Today @ 11:10 AM
Points: 18,344,
Visits: 12,357
|
|
Heh... I LOVE batch files. 
Point well taken, though. I've been put off of SSIS (and, previously, DTS) because of what I've seen people do with it... they can't figure out how to do something in it and write a VBS, ActiveX, Perl, or other script to accomplish the task. DTS really put me off because of the PITA when it comes to things like reconvergent multiple paths (ie. follow a side path because of conditions and rejoin the main path when complete without having to execute the other path(s)). That notwithstanding, I guess it's probably time to learn how to use SSIS the right way.
--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
