|
Dec
25 |
|
awarded | Popular Question |
|
Apr
20 |
|
comment |
SSIS 2005 - Have UPDATE *and* SELECT in OLE DB Source in Data Flow Sorry I was not clear. I want the Select/File operation and the Update operation to be part of one atomic transaction. So, if the update fails, the file is not created, and vice versa. I'm assuming one can not do that |
|
Apr
13 |
|
asked | SSIS 2005 - Have UPDATE *and* SELECT in OLE DB Source in Data Flow |
|
Apr
5 |
|
comment |
TFS 2010 - The path E:\SSIS is already mapped in workspace PC-mypc01 ah, and for SSIS2, map to E:\SSIS\SSIS2. Ok, thanks! |
|
Apr
5 |
|
comment |
TFS 2010 - The path E:\SSIS is already mapped in workspace PC-mypc01 Thank you for the swift response. I'm not sure I understand. If in TFS it *\Folder1\F2\F3\MySSIS1* I want the working directory to be *E:\SSIS\MySSIS1*. If something's in TFS as *\Folder1\F4\MySSIS_2*, I want it to be in *E:\SSIS\MySSIS_2*. |
|
Apr
5 |
|
revised |
TFS 2010 - The path E:\SSIS is already mapped in workspace PC-mypc01 added 123 characters in body |
|
Apr
5 |
|
asked | TFS 2010 - The path E:\SSIS is already mapped in workspace PC-mypc01 |
|
Mar
7 |
|
awarded | Supporter |
|
Dec
5 |
|
awarded | Scholar |
|
Dec
5 |
|
accepted | Return empty or null fields as <element /> from SQL Server 2008 R2 with FOR XML |
|
Dec
2 |
|
comment |
Return empty or null fields as <element /> from SQL Server 2008 R2 with FOR XML (Thanks for editing marc_s. Looks much better.) |
|
Dec
2 |
|
comment |
Return empty or null fields as <element /> from SQL Server 2008 R2 with FOR XML Thank you, I realize I can do that, and go back in and remove the 'xsi:nil' from my data, but that's an extra step I'd like to avoid if I could. |
|
Dec
1 |
|
awarded | Student |
|
Dec
1 |
|
asked | Return empty or null fields as <element /> from SQL Server 2008 R2 with FOR XML |
|
Jul
13 |
|
awarded | Editor |
