I have a scenario where I start multiple SSIS-packages simultaniously. This is done from SQL-code by, for each package first prepare using[SSISDB].[catalog].[create_execution], [SSISDB].[catalog].[set_execution_parameter_value], [SSISDB].[catalog].[set_object_parameter_value] and[SSISDB].[catalog].[set_execution_property_override_value]. After that [SSISDB].[catalog].[start_execution]

Problem I have is frequent deadlocks. I have then found there to be a known issue i MSSQL2014 and MSSQL2016 which are supposedly fixed in CU's. https://support.microsoft.com/en-gb/help/4016804/fix-deadlocks-occur-in-ssisdb-when-you-run-multiple-ssis-packages-in-s

For myself I also made a workaround by putting in delays in the code. Parctically making sure to avoid exact simultanious start of the packages.

Now moving forward by upgrading to MSSQL2017, more specifically 14.0.2002.14, I had hope that this problem should have been resolved but I find the problem to still be there.

Looking closer at the deadlock I can pinpoint the problem to [SSISDB].[catalog].[set_object_parameter_value]and the update...

UPDATE [internal].[object_parameters]
SET [default_value] = @parameter_value,
[sensitive_default_value] = NULL,
[base_data_type] = @parameter_type,
[value_type] = @value_type,
[value_set] = 1,
[referenced_variable_name] = NULL
WHERE parameter_id = @parameter_i

I have checked the later CU's for MSSQL 2017 but not found anything exactly targeting the above, althogh KB4466491 CU13 also seems to be about parallell SSISpackages. Also Im not sure that the problem I have is exactly the same as the ones fixed in 2014/216. I have compared procedure [SSISDB].[catalog].[set_object_parameter_value] and table [SSISDB].[internal].[object_parameters] and found no differences between 2016 and 2017 so if this was the same problem as in 2014/216 I dont understand what should have been fixed. So question is if this is known and perhaps any recomended workaround.

Hi,

First im gonna explain what i am trying to do.

I have stored procedure to get database information and store it in a table. As i need to collect all server information implementing SSIS package to read all instance info. In the procedure i have dynamic query(in @command variable) and i have 'exec sp_MSForEachDb @Command'.

I dont know how to implement this in SSIS. I created variable (evaluate expression as true and gave query into expression). I tried to use that variable in OLEDB source,

how to achieve this?

thank you

Built a new server with SQL Server 2014 Standard edition a while back and recently have ran into an issue that has led me down a path to question if Integration Services is installed or not on this server.

Looking at Windows Services, I don't see an entry for "SQL Server Integration Services 12.0", either running or not. So, I look in the SQL 2014 Configuration Manager and again, don't see an entry for any Integration Services.  So I pop the install disc in and start the process to add a feature, but at the Installation Type screen, I see "IS" listed as an installed Shared Component.  I click NEXT and I see a gray checkmark next to "Integration Services". I can't uncheck it. If I try to back out of the install a bit, and add it as a new Shared Component, I see the same issue, it is already checked with a gray checkmark and I can't uncheck or do anything else to it.  How do I fix this so Integration Services is installed and running properly?  Thanks!

Hello all,

A newbie with SSIS here, so apologies if I am not describing my question correctly. So I have a table named abcTbl, the data in there is populated from other tables from a different database. Every time I am loading data to abcTbl I am doing a delete all to it and loading the buffer data into it. This package runs daily. My question is how do I avoid losing data from the abcTbl if we fail to load the data into it. So my first step is deleting all the data in the abcTbl and then selecting the data from various sources into a buffer and then loading the buffer data into the abcTbl. Since we can encounter issues like failed connections, package stopping prematurely, supernatural forces trying to stop/break my package from running smoothly, etc which will end up with the package losing all the data in the buffer after I have already deleted the data from abcTbl.  My first intuition was to save the data from the abcTbl into a backup table and then deleting the data in the abcTbl but my dbas wouldn't be too thrilled about creating a backup table for in every environment for the purpose of this package, and giving me juice to create backup tables on the fly and then deleting it again is out of the question too. This data is not business critical and can be repopulated again if lost. But what is the best approach here? What are the best practices for this issue? Any help is very appreciated. Thanks.

I have flat file with space Delimited and space is not constant between the columns or there is no space in some of them. when i am trying to import using import/export wizard everything shows up in one column as ' column 0'. 

How i can put data in different columns?

i tried to use blank space in column delimiter, i can see different columns but data gets scatter un evenly. 

sample data 

841452  01Anne  L  parser   804 Mappple St  san diego       65845 

11000   06Paul  A   Roush   188  Florida Ave       san diego       68475 

Thank you very much for your time and effort to answer this post. Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach Best -Ankit

We just installed SQL Server 2016 and a new server.  I created a very simple package (nothing in it) and was able to deploy from my VS 2017 to the new server. It ran.

I then created a simple dataflow and deployed it, but it failed.  I got this error message.  I created simple dataflow from old 2008 SQL Server to the new 2016 SQL Server.

Package:Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Client unable to establish connection". An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm. ".

I found one article regarding TLS 1.2, but it was hard for me to understand and I wasn't sure if I needed to update the old 2008 server or the new 2016 Server.

Any help, links or comments appreciated.

Thanks,

Mike

Hoping this is the right forum...

We've been running a one-database SQL Server since converting from Access in 2010. The database backup type is Full. A Maintenance Plan was created at the outset consisting of 3 sub plans: Daily, Differential and Log Backups. The Daily runs overnight and performs these tasks: 1) Rebuild Index, 2) Update Statistics, 3) Check Database Integrity, 4) Maintenance Cleanup, 5) History Cleanup, and 6) Database Backup. Tasks 1 & 2 run against our one database named ALIS. The other tasks include the system databases. The Differential runs every 2 hours and the Log Backups every 15 minutes during business hours from 8 am to 9 pm, 7 days a week.

The database size is currently 21.5 GB. The log size has been growing in step with the database and lately crossed the 13 GB mark. With the company closed on Dec 26th, I used the opportunity to shrink the log down to its minimum, roughly 300 MB, then I resized it to 5 GB. This morning, after the Daily ran, the log size is back up to 13 GB with 98.7% log space used. After a Log Backup the log space used is 0.31%. I assume this is because the Full backup type is logging the Daily's Index work.

I'm asking for suggestions about how to avoid the Transaction Log bloat. My strategy would be to update the Daily sub plan by switching the database type from Full to Simple before Task 1 then switching it back from Simple to Full after Task 2. If anything happened during those tasks we could recover from the previous night's Full and the day's last Differential.

I'm not sure how I would accomplish this switching as I didn't author the original Maintenance Plan nor do I have any experience with these. I'm guessing that I would add an Execute T-SQL Statement task along the lines of:

ALTER DATABASE ALIS SET RECOVERY SIMPLE;
GO

and place it first in the list of Tasks. Then insert another of these between Tasks 2 and 3:

ALTER DATABASE ALIS SET RECOVERY FULL;
GO

Is this what you would do? Any other suggestions?

Thanks!

I develop SSIS package for SQL 2016 SP1 and using theSSIS CDC tools (CDC Control Task, CDC Source, CDC Splitter) from VS 2015. I was under the impression that these tools are generic VS tools , but running program in debug mode, I noticed that they are part of the Attunity namespace  (when looking in component/task properties in VS ex:Attunity.SqlServer.CDCControlTask.CdcControlTask). Source server runs 2016 SP1standard edition and has CDC enabled source database and destination server has ETL and SQL 2016 SP1 standand edition instances and therefore the Attunity tools for Integration Services on the destination ETL/DB server look like are not supported (https://docs.microsoft.com/en-us/sql/integration-services/integration-services-features-supported-by-the-editions-of-sql-server?view=sql-server-2016#ISAT) since not running enterprise

My question is related to the Integration services not the database server, I know that database server supporting CDC starting with 2016 SP1.

Are there no CDC Control Task, CDC Source, CDC Splitter tasks in VS 2015 which are supported by the 2016 SP1 Integration Services, all these 3 are Attunity tasks actually under VS 2015? or if there are VS tools that are not Attunity what is the recommended tools to use for CDC enabled database on Integration services 2016 SP1 standard edition? CDC functions?

I very much appreciate your input.

I submitted previously another question inhttps://social.msdn.microsoft.com/Forums/sqlserver/en-US/70d527f3-a179-4296-a699-c19cd4774edf/are-ssis-cdc-tools-supported-in-ssis-2016-sp1-standard-edition?forum=sqlsetupandupgrade#5f4898f7-d46c-4888-b4fb-d0fe00115cd6

Thank you,

Hello

I have set up an SSIS package on Windows to download a CSV file from an FTP run some transforms and download images from a list of URLs which works fine.

I then want to deploy this onto an Ubuntu server running SQL Server 2017 with SSIS installed.

As the SSISDB Catalog is not supported on Linux it seems the only way to run this is as a cron job as per the instructions here:

https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-schedule-ssis-packages?view=sql-server-2017

However as I must develop the package on Windows I cannot enter Linux compatible paths as this raises an error and I cannot save the connection in Visual Studio. As a workaround I open the .dtsx package with VS Code and edit the paths in the XML to /home/...

I then execute the package using:

/opt/ssis/bin/dtexec /Decrypt PASSWORD /F /home/WEBSITE/stocklist/RefreshAutoTraderStocklist.dtsx

But whatever I do this always fails and says the paths are not valid. I have tried running as SU and also chmodding the files and folders being accessed to 777 yet it makes no difference. I cannot find any documentation on this specifically relating to Linux so am not sure how I can get this working.

Errors are:

Error: 2018-10-20 14:00:24.28
   Code: 0xC001401E
   Source: RefreshAutoTraderStocklist Connection manager "FILE.csv"
   Description: The file name "/home/WEBSITE/stocklist/FILE.csv" specified in the connection was not valid.
End Error
Error: 2018-10-20 14:00:24.29
   Code: 0xC001401D
   Source: RefreshAutoTraderStocklist
   Description: Connection "FILE.csv" failed validation.
End Error
Error: 2018-10-20 14:00:24.29
   Code: 0xC001401E
   Source: RefreshAutoTraderStocklist Connection manager "FILE.csv (from FTP)"
   Description: The file name "/home/WEBSITE/stocklist/" specified in the connection was not valid.
End Error
Error: 2018-10-20 14:00:24.29
   Code: 0xC001401D
   Source: RefreshAutoTraderStocklist
   Description: Connection "FILE.csv (from FTP)" failed validation.
End Error
Progress: 2018-10-20 14:00:24.40
   Source: Save Data to Database
   Validating: 0% complete
End Progress
Error: 2018-10-20 14:00:24.40
   Code: 0xC001401E
   Source: RefreshAutoTraderStocklist Connection manager "FILE.csv"
   Description: The file name "/home/WEBSITE/stocklist/FILE.csv" specified in the connection was not valid.
End Error
Error: 2018-10-20 14:00:24.40
   Code: 0xC0202070
   Source: RefreshAutoTraderStocklist Connection manager "FILE.csv"
   Description: The file name property is not valid. The file name is a device or contains invalid characters.
End Error

The files and folders do exist in the locations mentioned but all I can guess is that when the SSIS package is trying to validate itself it is seeing these paths as invalid as they would not be valid on Windows but I am not sure how I can bypass this.

Thanks

Robin

Robin Wilson

Hi there,

I am working in a SQL Server 2012 RC0 environment.  I am looking to create Package Configurations for my SSIS solution in SQL Server Data Tools (SSDT).  The option for Package Configurations is not in the SSIS menu nor in the menu when I right click on the Control Flow designer page.   The other menu options are there: Logging, Digital Signining, Variables, etc.  All the searching I have done shows that this should still be available for 2012. 

Can anyone tell me how to get this menu option visible in SSDT? 

Thanks,

Martina

For web or windows apps building the code makes it harder to decrypt the code. I need to be able to send the SSIS 2016 package code for deployment (project type package to deploy to SSISDB). If I send ispac file this can be easily imported in VS, is there any way to build SSIS code in order to upload to catalog by DBA (other than password protected of course).

Thank you,

Hi,

if we set file group auto growth to unlimited what are the problems will raise,what happen my scenario means I got critical alert from SCOM ,it's says that Could not allocate space for object in database because the File group is full.

  When i went DB see that DB auto growth options max size of file 371 MB they restricted , after that i changed toUNLIMITED.Now it's working fine but my doubt is is there any problem will occur moving forward?I hope will 

Regards,

Niranjan B

Hello,

I have Sql Server 2016 (13.0.4001.0) installed on my machine and I downloaded SSDT for VS2017 (15.1.61810). 

While SSDT was on setup step, I have choosen all features for Sql Server Analysis Services, Reporting Services and Integration Services. So after the installation, I tried to Create a new project under Business Intelligence > Integration Services > Integration Services Project, but as soon as I give a name to the new project and clicked on OK, I got the  following error: 

Could not load file or assembly 'Microsoft.SqlServer.ManagedDTS, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

Then I tried to create a Reporting Service Project, it is created successfully. 

So please help me understand the main problem and kindly suggest me a solution. 

Thanks,

Hi All,

We are migrating an SSIS project from SQL 2012 to SQL 2016. The project upgraded successfully without any issues and able to run few packages without any errors. But there are few packages which has got the script task and they are failing. The error message is as below: -

Error: There was an exception while loading Script Task from XML: System.Exception: The Script Task "ST_bb19096e98ab45d2a2d6132b995cd509" uses version 15.0 script that is not supported in this release
of Integration Services. To run the package, use the Script Task to create a new VSTA script. In most cases, scripts
are converted automatically to use a supported version, when you open a SQL Server Integration Services package
in %SQL_PRODUCT_SHORT_NAME% Integration Services. at
Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.Load
FromXML(XmlElement elemProj, IDTSInfoEvents events)

This runs fine when run from BIDS (VS2015). It also runs fine if the project is deployed from BIDS and run through agent job. But when the deployment happens through .ispac (deployment) file, this error occurs. Can somebody suggest how to get past this error?

Is it any known issues with migration or with SSIS 2016?

Thanks.

Hi,

I'd like to know if it is possible to implement the UPDATE operation for a table by using a data flow task,

not using an Execute SQL task.

I already use Execute SQL task to implement a such operation.

Thanks

Hi,

I have created an SSIS package , that collects the data from Oracle  and load it into SQL SERVER . The package runs fine , when I run it through Microsoft BIDS. It gets failed only when I schedule it through Jobs scheduler (SQL Agent) .  I am using attunity drivers for oracle connector.

the error is:  data flow task: oracle source failed validation and returned error code 0x80004005

please advice me

thanks

Raja

I have created a SSIS package which connects to an Oracle database. My code runs multiple SQL statements, how do I seperate the statements so that it run in 1 Execute SQL task (the ones I have tried do not work)?

Any help much appreciated.

Chris

Hi,

I have the query below returns 2 rows, I would like to concatenate it into one row.

select seq, textnumber, textvalue from mytbl where textnumber =1234

Current Results

I would like the results show as below.

Thanks