etl

I have a Time Value stored as string with the format HH:mm I used the following code to parse it as date with Today Date DateTime.ParseExact("09:00","HH:mm",New System.Globalization.CultureInfi("En-GB")) The Result Is 2017-03-15 09:00:00 When Running this Code From another machine i get the following Result: 1899-12-31 09:00:00 I replaced my code to the following DateTime.ParseExact(DateTime.Now.ToString("yyyy-MM-dd") & " 09:00","yyyy-MM-dd HH:mm",New System.Globalization.CultureInfi("En-GB")) And it works Fine, But i still want to Know why every system parsed the date to a different Value???

Based on my earlier questions , how can I pivot data using Informatica PowerCenter Designer when I have variable amount of Addresses in my data. I would like to Pivot e.g four addresses from my data. This is the structure of the source data file: +---------+--------------+-----------------+ | ADDR_ID | NAME | ADDRESS | +---------+--------------+-----------------+ | 1 | John Smith | JohnsAddress1 | | 1 | John Smith | JohnsAddress2 | | 1 | John Smith | JohnsAddress3 | | 2 | Adrian Smith | AdriansAddress1 | | 2 | Adrian Smith | AdriansAddress2 | | 3 | Ivar Smith | IvarAddress1 | +---------+------

I have problems with SSIS process(acctually the same problem occurs for two different processes). So, we are doing some ETL work using SSIS. We have Business Intelligence project that executes without errors from Visual Studio. However when its deployed on the server and scheduled as a job it fails with errors like: INTRASTAT_Towar:Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Union All 3" (876) failed with error code 0xC0047020 while processing input "Union All Input 2" (916). The identified component returned an error from the ProcessInput method. The

I'm aware of Microsoft's inclusion of Python in their Machine Learning Services for SQL server, however this is only available for SQL Server 2017 and up, which is a requirement my servers do not currently meet. With that being the case, I wanted to deploy my generate-predictions-with-trained-model pipeline entirely within SSIS, I.E: Grab data from my DB Pass it to a Python Script Data Flow Task which imports the trained model, generates the predictions and passes them on to the next Data Flow Task Write the predictions to the DB Is there a way to do that entirely within SSIS, or will it be

How to call .dtsx package file which has input parameters from a stored procedure? Stored Procedure # 1 -> Will pass the list of files to be exported to excel as a Comma Separated value in a variable. Input variable will be passed to the SSIS Package to export the data to excel. How to handle the SSIS Package which has Input parameters from a Stored Procedure call? Using DtExec and xp_cmdshell One way to do that is to run DtExec utility from file system using xp_cmdshell utility inside sql server. First you have to enable the xp_cmdshell utility: -- To allow advanced options to be changed.

SSMS and SSRS to Excel enable for more than 255 columns when copy-pasting. SSIS does not allow for more than 255 columns to be exported to Excel 2007. Is there a way to override this? Problem There are a lot of Limitations when exporting to an Excel Files using Sql server data tools Workarounds You can do some workaround to achieve this: Create a dataflowtask that export your data into a FlatFile ( csv ) Store your Destination FileName in a Variable Create another Dataflowtask that convert your csv file to an Excel File using a script task with a similar Function Note: you have to add