ssis

问题 I am writing an SSIS package that has required me to use the Microsoft.Exchange.WebServices DLL. I have imported it into the VB Script Task where it is referenced from the following location: C:\Program Files\Microsoft\Exchange\Web Services\2.0\Microsoft.Exchange.WebService.dll The script task seems to 'like' it in so much that I have imported the Namespace and am able to declare the ExchangeService as an object. However, when it comes to running the package (both compiled and in debug) I get

问题 I’m importing a SQL view to SSIS using the Flat File Connection Manager. One of my columns in SQL has comma(s) in it. (123 Main St, Boston, MA) . When I import the data to SSIS, the commas within the column are being treated as delimiters, and my column is being broken into several columns. I have done a lot of research online, and have followed some workarounds which aren't working for me. In SQL Server, I added double quotes around the values that have comma(s) in it. ' "'+CAST(a.Address as

问题 Not too familiar with dtsx packages - can they be created/run outisde Visual Studio? Is BIDS (Business Intelligence Development Studio) just required to do all the above (in Visual Studio) or is it an independent development enviroment for dtsx packages? Please shed some light if you can (and get some eazy rep)! 回答1: Absolutely! Just double click on it (launches dtexecui.exe ) or use the dtexec command. See how all the ways stack up here. Answering some of the other questions: BIDS is the

问题 Not too familiar with dtsx packages - can they be created/run outisde Visual Studio? Is BIDS (Business Intelligence Development Studio) just required to do all the above (in Visual Studio) or is it an independent development enviroment for dtsx packages? Please shed some light if you can (and get some eazy rep)! 回答1: Absolutely! Just double click on it (launches dtexecui.exe ) or use the dtexec command. See how all the ways stack up here. Answering some of the other questions: BIDS is the

问题 I have a requirement where I'm pulling large amounts of data from SQL Server and will have to insert this data into Excel files. Now, each excel file must not have more than 1000 rows. These excel files will have to created on the fly. Please help 回答1: I suggest you wrap your logic in a loop container. Logically, it would look like this: Count the number of rows ready to export to excel. Divide by 1000, round up and set as a variable. (EX. 5049 rows -> 6) Have a loop container loop on the new

问题 I have created 2 variables in SSIS, namely ProductValue and SQLQuery. The SQLQuery contain the sql statement as below "SELECT * FROM Products Where ProductID > " + @[user::ProductValue] When I pass the SQLQuery variable to Ole db source via data access mode = sql command from variable, system return an error messages as below Error at Data Flow Task [OLE DB Source [1]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available.

问题 I've created an SSIS package with a dataflow. The oledb source uses a variable with a sql statement. Following the oledb source, there is a derived column transformation that converts the data. If that breaks, it is redirected to a log table, if it doesnt break it goes to the oledb destination table. Question: Is there a way I can determine what the source and destination tables are when the conversion breaks, for logging purposes? Note: The source table is in the variable used by oledb

问题 I have set up a Package Configuration where the Configuration Type is (Indirect XML Configuration File). Where the Environment Variable is pointing to the C:\SSIS\MasterConfig\MasterConfig.dtsConfig file. This working great and allows easy migration from Test to UAT to Production. The problem is in our Development environment where each developer has their own DB. I am trying to set up an Agent Job for each developer where the Agent Job would override the Master Configuration File. The agent

问题 I'm using VS 2012 with SQL Server Data Tools installed. I have an ADO NET Source, which uses the .Net Providers\MySQL Data Provider and am trying to push some data to an OLE DB Destination, which uses a normal SQL Server Native Client 11.0 provider. Everything seems ok, I can preview data from the source and columns are mapped well - but when I run the project I get the following error: [ADO NET Source [2]] Error: ADO NET Source has failed to acquire the connection {47479EC0-98BC-4664-A8F9

问题 I need to export data from SQL Server 2012 based on a view. While testing the export for a downstream system, I was manually extracting the data out of the table that the view is based on and the BIT data type columns were reporting as 1/0. However, once I setup the view against the table, I noticed that the BIT data type columns reported as TRUE/FALSE. This happens whether I perform a select against the view or export from it. Why does this happen and how can I maintain the same results in