| Author |
Topic |
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
 Posted - 2009-01-19 : 19:52:00
|
| GreetingsI am trying to design my SSIS package properly, this is my first one in SQL 2005.I have my ssis package running every 15 minutes doing upserts. Would a design approach of having one ssis package calling one jumbo sproc that calls other sprocs that call other functions be a good idea?if the whole fails I want it to fail...but I can see where I can break this jumbo sproc and push out the other sprocs into T-SQL tasks on their but I do not see why...would appreciate your input.Thanks |
|
|
evmisu
Starting Member
17 Posts |
Posted - 2009-01-19 : 23:21:38
|
| Hi YosiaszI am sorry to say that I cannot solve ur problem but i am really curious about that how to set the package run every 15 minutes. where is the function?Thank you very much for telling me the informaion. I am really new to SSIS. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2009-01-20 : 00:31:30
|
quote:
Originally posted by yosiasz
GreetingsI am trying to design my SSIS package properly, this is my first one in SQL 2005.I have my ssis package running every 15 minutes doing upserts. Would a design approach of having one ssis package calling one jumbo sproc that calls other sprocs that call other functions be a good idea?if the whole fails I want it to fail...but I can see where I can break this jumbo sproc and push out the other sprocs into T-SQL tasks on their but I do not see why...would appreciate your input.Thanks
It is very hard to answer this question with the information that you have provided.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2009-01-22 : 11:14:41
|
| oops sorry here it what I meanI have an SSIS packake with 1 and only SQL Task which calls one store procedureusp_InsertCommodityDefinitions (which does the following INSERTs) INSERT [dbo].[VCommodityDefinitions] EXEC dbo.usp_GetPlatesCutArea INSERT [dbo].[VCommodityDefinitions] EXEC dbo.usp_GetPlatesEPT ..... ....Is this a good design approach?Thanks |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-22 : 11:27:57
|
| why are trying to wrap all inside same procedure. you could simply use separate sql tasks for each table insertion. this way you will be able to isolate which part is having problems easily while debugging. for failing them together you could keep all the tasks inside a sequence container and set transaction property to required for container in which case it will undo all changes in case of any intermediate failure and at the same time you can clearly identify which part failed by looking into details of task alone which failed. |
|
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2009-01-22 : 12:05:03
|
| true true...the insert is in the same table just different values for different commodity types and even for each commodity type there are many different definitions types..but I agree it would make more sense to do each insert in different SQL Tasks.that way i will not have one lonely SQL task all cold by itself. it needs other SQL task friends. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-22 : 12:12:47
|
| yup. but is that a problem? using seperate sql tasks for each? i think that should be an approach that you should seriously consider |
|
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2009-01-22 : 12:43:22
|
| no sir no problem! I have done as yu suggest and it cleaner and easier to manage.shukran, merci, dangShaun |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-22 : 12:45:52
|
ok...cheers  |
|
|
|
|
ssis design question?