 | |
SSIS: How to run tasks within a package outside of package transaction?
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#41
 
| |||
| |||
|
Re: SSIS: How to run tasks within a package outside of package tra -
06-12-2008
, 10:19 AM
#42
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
#43
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
#44
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
#45
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
#46
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
#47
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
#48
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
#49
| |||
| |||
|
|
OK, I see it now. Your quandry is that you want tasks 1,3,5, and 7 to be viewable while the loading of and processing of 2,4 and 6 are happening, all inside a transaction. You might be able to resolve this OUTSIDE of SSIS! In the application that queries the log table, what Transaction Isolation Level are you using? the default? I am guessing so. The default TIL is "Read Committed", meaning that if you query the log table and it has un-commited transactions, you son't see them. Check BOL for other TIL, namely "Read Uncommitted". While this is NOT NORMALLY RECOMMENDED because you can get results that are not repeatable, it might work in your case. The rows that are not yet commited can be read using this TIL. Take this advice with caution because I'm no expert on Transaction Isolation Levels! Read up and understand before applying changes, and for heaven's sake, test, test, and TEST AGAIN! -- Todd C |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.