Tag Info

New answers tagged

0

I have run into this a few times and the issue has been a mismatch of data types in the export/import parameters. First thing to do is check those parameters by right click on source or destination, selecting Advanced Editor. Go to Input and Output Properties and check the data type for that column for all items - both External, Output, and Input. I have ...


2

An operation which is blocking must wait until all rows have been seen and handled before it can start populating buffers. An operations which is partially-blocking writes data onto new buffers, which only get handled by the next operation once each buffer (typically just under 10,000 rows) is populated. An operation which is non-blocking can have the ...


0

Put the CSV import in one data flow, then in a dependent data flow use an OLE DB Source that contains the results you need as the output of a SQL query. Feed that into an OLEDB destination. Your query would look similar to: SELECT t1.col1, CASE WHEN EXISTS (SELECT null FROM db2.dbo.table2 t2 WHERE t2.col1 = t1.col1) THEN '2' ELSE '1' END as [col2] FROM ...


2

I think you need to be clearer on your exact intended setup. That will allow for a better reading of those two linked questions. I would guess that those two links are actually irrelevant. SQL Server Express comes with a stripped down version of SSIS (or can be installed via the Tools or Advanced install), according to Link #2. But yet your question regards ...


1

Permissions to assign her are going to be based on what deployment model she is going to use within your environment. SSIS 2012/2014 added an additional model: Project and Package For Package Deployment model she has the option of deploying the packages to msdb. Granting her permissions for this type of deployment you will grant her permissions to an SSIS ...


2

The issue is caused by a clash in code pages between 1252 (i.e. Windows-1252) in SQL Server and 65001 (i.e. UTF-8) that your CSV file is expecting. I believe one solution to the issue would be to CAST your source columns to NVARCHAR in the initial SELECT from the database, or use a Data Conversion task to convert them to Unicode strings. An alternative ...


1

Pls make sure you have tried the solutions below Set DelayValidation property set to True for the Send Mail Task. Close the filestream of the log file before sending the email


5

have built my SSIS packages to check and make sure that the day isn't a holiday by comparing the date to a table that contains holidays. You can have your 1st job step as IF EXISTS (SELECT 1 FROM HolidayTable WHERE Date = GETDATE()) begin RAISERROR ('There is nothing to run as today is holiday !', 16, 1) end else print 'The job can run .. ...


2

How about making use of the OUTPUT virtual table? Set your transaction isolation level correctly (snapshot/serializable) so that you only see the rows as of the moment your process begins. Use the following for your OLE DB Source UPDATE T SET Archive = 1 OUTPUT DELETED.* FROM Table T WHERE T.Archive = 0; That updates everything in a nice atomic ...


0

The firewall wasn't set up correctly. Once I got the network admin to let port 20 through, all was working well. I ended up sticking with the "DontSaveSensitive" and using a config file to make deployment easier through multiple environments.


0

A pure SSIS solution would be to deliver the Data Flows for the Insert and Update tasks into Cache Transformations. http://msdn.microsoft.com/en-us/library/bb895264.aspx If they occur in 1 Data Flow then you might be able to send them to a single Cache, otherwise you will need 2. Then you can test against those Caches in later Data Flows using the ...


2

Since you are using SSIS and capturing the changed rows, you should have SSIS capture the PK values for the rows that are being processed. The last step of the package should be to do a targeted update on the source table, setting the [Archive] field to 1 based on those PK values. And if not already done, the update trigger needs to exclude those changes ...


1

First make sure that you are able to connect FTP server through windows explorer, and then try three things For Package: 1- Package Protection Level= EncryptSensitiveWithUserKey For FTP Connection Manager: 2-Server Port= 21 3-UsePassiveMode= False


1

Change Tracking (CT) and Change Data Capture (CDC) are built into SQL Server. CT can identify the rows which changed since you last asked. CDC can provide a complete history of all data changes since you last asked. Both are easily manipulated from SSIS. There will be no need to reset flags per row after processing. The system handles all this through ...


0

I have achieved this without any SSIS. I used a linked server instead. It took me some time, but I still believe it is the best way of backing up SSAS databases. You can see how I did it on this link. I also delete old backup files, as you can see on this link.



Top 50 recent answers are included