I have Sample "Table 1",need to be converted as "Table 2"

Table 1

 Need result set like ..

Table 2

need methodolgy to tranform like this 

in MS SQL 

GOVINDARAJ P

Hi,

Can any one help with this please?

We have the following error in the Event viewer when running a SSIS package:

Looking at the Task Manager it appears as the package executes the  memory allocation for the process increases until it reaches about 960MB and then it kills itself  with the error above. The package status is "Running" (sometimes it completed with status: unexpected Termination).

The server is running on a VM with 8GB memory. The SQLserver max memory is limited to 4GB.

The other packages in the project seem to work fine.

Kind regards

Hello, 

How can i format Column Data in SSIS, similar to MSSQL

SQL: Select FORMAT(7.326, '00.0000000') AS 'Format' 

Results: 07.3260000

As you can see, I need both leading 0 and trailing 0 with 10 Character long with 2 before decimal "."

Thank you,

M

Hi

I am reading more than one CSV files from same path for example:

\\1.10.10.1\Folder1\Folder2\File1.csv

I want to replace Path (C:\Folder1\Folder2\) with variable.

Source Path Variable

Connection Manager: I believer issue is in concatenating Variable with Filename. 

Regards

I have the ssis package to generate excel file.
There is the SQL task to create the empty excel file 
CREATE TABLE `OpenSales` (
`Order Date` date,
`Discount Amount`Double
)
I have the excel file and manually enter number into the Discount Amount field to make sure this field is number.
There is the data conversion to convert this field into "Four-Byte-Signed integer[DT-I4] 
I don't know why the final excel file has changed the data type for Discount Amount field to txt.
What should I do to not let this date change from the xcel file?

Thanks

I have installed Azure Feature Pack to my Visual studio 2017 as an extension .when I created a ssis package I do not see Azure Table Storage as source assistant .How can I get this ?

In Format tab -> Make Same Size --> Width

Same size as which box?

When I resize the top one, select it, and select the others one by one holding down the CTRL key, it does resizes to the top one.

Wonder if there is a better way....

Hi Experts,

I am building an SSIS package to do the delta load.

I am creating Select statement in source and target editors to compare the data changes. I am using HASHBYTE function in the select statement which I would use to update the records with the below code in Split Change transformation.

(ID == [ID (1)]) && ((DT_WSTR,40)HASHBYTE != (DT_WSTR,40)[HASHBYTE (1)])

However, my source table has fields with the data types BIT, Bigint, nvarchar and datetimeoffset.

Could you please advise what would be my HASHBYTE code?

Appreciate your response. Thanks in advance.

Hi ,

Can someone please suggest the best approach

I need to call the SSIS package which is on the remote server (server 2) in SSIS catalog from a Stored PROC from SERVER 1.

I need to pass few parameters as well to the SSIS package.

Thought of below 2 approaches but not sure if i can do that

1.Create a SQL job on SERVER 2 which in turn calls my SSIS package and call the SQL job from SERVER 1

     In this case i am not sure how to pass the parameters to SQL job

2. create a linked server for SERVER 2 in SERVER 1 and use EXEC [SERVER2].[SSISDB].[catalog].[create_execution] proc

The SSIS is deployed using project level deployment 

Regards,

Pavan

Hi,

I have SSIS package that reads data from Excel file and load into sql server.

The package is running successfully so far. Recently, my laptop restarted with windows updates.

Since that time I am getting error at Excel Source

Hi All,

I have a job that execute SP , that runs multiple time a day. It used to run fine for year but after few months it started skipping value from specific date.

Example I have WTD period slicer in the SP.  In one schedule pulls data from five date but in next schedule it pulls from six dates. The correct one is six date.

Is there any thing that I have to look at and check ?

Your help is highly appreciated.

Thanks

Bihon

Hello, I’m on a Windows Server 2012 R2 Standard Edition, and SQL Server 2016 SP1. I also have installed Teradata Driver 15.10, Teradata Transport Utilities 15.10, and Attunity V3.

I need to upgrade the Teradata Driver, Utilities to Teradata Version 16.2, and I may have to upgrade the SQL Server Attunity for Teradata Connector to Version 4, not sure yet on that one.

My question is, has someone else out here with the same system setup, performed this same upgrade without issues and no incompatibilities problems? Any pitfalls I need to be made aware of by chance?

Thank you

Hi,

Recently my client had to make changes to their firewall.  I have a SSIS package that communicates with an outside source that has worked without issues prior to this.  I am now getting the following error message.  Does anyone have any suggestions where to start to correct this issue?  Thanks

TITLE: Microsoft Visual Studio
------------------------------

Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSObject100'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{30E5D0EF-E33D-4945-8A7F-F5178FC64C24}' failed due to the following error: The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD)).

Because I did see only an empty ssis toolboxI tried to reinstall SSIS Version 3.4 and I got an error and following protokol:

[0A70:1AA8][2020-03-04T18:45:56]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: .\Downloads\Microsoft.DataTools.IntegrationServices.exe, cmdline: ''
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'ProductVersionVar' to value '15.0.2000.71'
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'ReleaseVersion' to value '3.4'
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'LicenseTermsUrl' to value 'https://go.microsoft.com/fwlink/?LinkID=853828&clcid='
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'PreviewStatementUrl' to value

../ some lines I had to delete because of size / ..

[27A0:0C4C][2020-03-04T18:47:31]i301: Applying execute package: SSAS_AMO2016, action: Repair, path: C:\ProgramData\Package Cache\{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14\payload\SQL_AS_AMO2016.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 47
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 24, Overall progress: 48
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 37, Overall progress: 49
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 50
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 63, Overall progress: 51
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 76, Overall progress: 52
[0A70:1AA8][2020-03-04T18:47:32]i000: MainViewModel.OnPackageActionProgress: Percent completed: 89, Overall progress: 53
[0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server 2016 Analysis Management Objects (id: SSAS_AMO2016)
[0A70:1AA8][2020-03-04T18:47:40]i319: Applied execute package: SSAS_AMO2016, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:40]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {97A881AD-5134-4CD2-A6A8-371C83E5622B}, package: SSAS_AMO2016
[27A0:0C4C][2020-03-04T18:47:40]i323: Registering package dependency provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, version: 13.1.4561.14, package: SSAS_OLEDB2016
[0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
[27A0:0C4C][2020-03-04T18:47:40]i301: Applying execute package: SSAS_OLEDB2016, action: Repair, path: C:\ProgramData\Package Cache\{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14\payload\SQL_AS_OLEDB2016.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 55
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 28, Overall progress: 56
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 41, Overall progress: 57
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 54, Overall progress: 58
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 67, Overall progress: 59
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 80, Overall progress: 60
[0A70:1AA8][2020-03-04T18:47:42]i000: MainViewModel.OnPackageActionProgress: Percent completed: 95, Overall progress: 61
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
[0A70:1AA8][2020-03-04T18:47:45]i319: Applied execute package: SSAS_OLEDB2016, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:45]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, package: SSAS_OLEDB2016
[27A0:0C4C][2020-03-04T18:47:45]i323: Registering package dependency provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, version: 14.0.3002.563, package: SSDTISSingleton140
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
[27A0:0C4C][2020-03-04T18:47:45]i301: Applying execute package: SSDTISSingleton140, action: Repair, path: C:\ProgramData\Package Cache\{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563\payload\SSDTISSingleton140.msi, arguments: ' MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 62
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 63
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 64
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 48, Overall progress: 65
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 66
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 73, Overall progress: 67
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 84, Overall progress: 68
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageActionProgress: Percent completed: 98, Overall progress: 69
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
[0A70:1AA8][2020-03-04T18:47:46]i319: Applied execute package: SSDTISSingleton140, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:46]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, package: SSDTISSingleton140
[27A0:0C4C][2020-03-04T18:47:46]i323: Registering package dependency provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, version: 15.0.2000.71, package: SSDTISSingleton
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
[27A0:0C4C][2020-03-04T18:47:46]i301: Applying execute package: SSDTISSingleton, action: Repair, path: C:\ProgramData\Package Cache\{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71\payload\SSDTISSingleton.msi, arguments: ' MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 70
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 71
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 72
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 56, Overall progress: 73
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 74
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 75, Overall progress: 75
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 88, Overall progress: 76
[0A70:1AA8][2020-03-04T18:47:51]i000: BootstrapperEngineDataModel.OnExecutePackageComplete: Package requires a restart but it has not been initiated yet.
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
[0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: SSDTISSingleton, result: 0x0, restart: Required
[27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, package: SSDTISSingleton
[27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsixPreInstall, version: 1.0.0.0, package: ISVsixPreInstall
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsixPreInstall, action: Install, path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe, arguments: '"C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe" /instanceIds:"33f63265" /log:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log"'
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 80
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 84
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: ISVsixPreInstall, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package: ISVsixPreInstall
[27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsix, version: 1.0.0.0, package: ISVsix
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
[27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsix, action: Install, path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe" /q /admin /instanceIds:"33f63265" /logFile:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_11_ISVsix.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"'
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 88
[27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Process returned error: 0x80131500
[27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
[0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to configure per-machine EXE package.
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
[0A70:1AA8][2020-03-04T18:48:10]i319: Applied execute package: ISVsix, result: 0x80131500, restart: None
[0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
[27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsix, package: ISVsix
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsix, from path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\
[27A0:0C4C][2020-03-04T18:48:10]i326: Removed dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package ISVsixPreInstall
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 92
[27A0:0C4C][2020-03-04T18:48:10]i301: Applying rollback package: ISVsixPreInstall, action: Uninstall, path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe, arguments: '"C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe" /instanceIds:"33f63265" /log:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log" /u'
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:48:10]i319: Applied rollback package: ISVsixPreInstall, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsixPreInstall, package: ISVsixPreInstall
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsixPreInstall, from path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton, from path: C:\ProgramData\Package Cache\{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton140, from path: C:\ProgramData\Package Cache\{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_OLEDB2016, from path: C:\ProgramData\Package Cache\{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2016, from path: C:\ProgramData\Package Cache\{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2014, from path: C:\ProgramData\Package Cache\{76CBDC35-0752-4B5A-83E8-49A741BD42BC}v12.2.5626.31\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2012, from path: C:\ProgramData\Package Cache\{53086A62-13F3-4FC5-AA41-211FD74340B3}v11.4.7001.0\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2016, from path: C:\ProgramData\Package Cache\{1F86F7A6-BCC6-49C4-8033-785993FA6331}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2014, from path: C:\ProgramData\Package Cache\{07001141-C74D-47ED-B03D-892C7EF00E3D}v12.2.5626.31\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2012, from path: C:\ProgramData\Package Cache\{DB97C76B-9116-42C5-8814-0041856EB9E6}v11.4.7001.0\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: VCRedist2010, from path: C:\ProgramData\Package Cache\28C54491BE70C38C97849C3D8CFBFDD0D3C515CB\
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
[0A70:1AA8][2020-03-04T18:48:10]i000: BootstrapperEngineDataModel.OnApplyComplete: Bundle requires a restart but it has not been initiated yet.
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:\Users\obresl01\AppData\Local\Temp\dd_VSIXInstaller_20200303165453_2594.log ...
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog:   last modified at 03.03.2020 15:54:53, which is too old. Skip processing.
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:\Users\obresl01\AppData\Local\Temp\dd_VSIXInstaller_20200303165453_2f54.log ...
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog:   last modified at 03.03.2020 15:57:04, which is too old. Skip processing.
[0A70:1AA8][2020-03-04T18:48:10]e000: MainViewModel.OnBundleAction: Bundle action failed: Unknown error (0x80131500) (0x80131500)
[0A70:1AA8][2020-03-04T18:48:10]i399: Apply complete, result: 0x80131500, restart: Required, ba requested restart:  No
[0A70:0C04][2020-03-04T18:48:17]i000: MainViewModel.OpenUrl: Opening url: .\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556.log

Somebody can help?

regards

Olaf

olaf870

I use the SSMS SQL Server-Import/Export-Assistant to export a table of an MSSQL Server to a local paradox bde file (.DB).

The Goal is to export the slected table columns to a bde file. I need the database in this format for a specific Software applcation that only accepts paradox databases.

I use the following Connection string acoording to my ODBC Driver Settings:

"Driver={Microsoft Paradox Driver (*.db )};driverid=538;defaultdir=c:\basytec\organisation\;dbq=c:\basytec\organisation\;collatingsequence=ASCII;readonly=false"

I simply use this SQL string to select the Input value:

"select [NumberFormatted] from dbo.TXQV_Tests where Status < 8 and ProductType = 'Cell' and LabFieldIdent = 27"

for the Export I use the create function as follows. this should create a .db file and fill in the in Import selected table:

"CREATE TABLE "Abfrage" ("NumberFormatted" AlphaNumeric(48)

The process doesn't work as expected. The created bde file is empty with existing headers but no content. This is the error Code in german: roughly translated: the operation Needs to use an updateable query.

• Es wird kopiert in ""Abfrage"" (Error) Messages Fehler 0xc020844b: 1-Datenflusstask: Ausnahme beim Einfügen von Daten. Die vom Anbieter zurückgegebene Meldung lautet: ERROR [HY000] [Microsoft][ODBC Paradox Driver] Operation muss eine aktualisierbare Abfrage verwenden. (SQL Server-Import/Export-Assistent) Fehler 0xc0047022: 1-Datenflusstask: SSIS-Fehlercode "DTS_E_PROCESSINPUTFAILED". Fehler bei der ProcessInput-Methode in der Komponente "Ziel - Abfrage" (19) mit dem Fehlercode 0xC020844B beim Verarbeiten der Eingabe "Destination Input" (22). Die identifizierte Komponente hat einen Fehler von der ProcessInput-Methode zurückgegeben. Der Fehler ist komponentenspezifisch. Es handelt sich jedoch um einen schwerwiegenden Fehler, sodass die Ausführung des Datenflusstasks unterbrochen wird. Möglicherweise wurden bereits Fehlermeldungen veröffentlicht, die weitere Fehlerinformationen beinhalten. (SQL Server-Import/Export-Assistent)

I know, that there is an index definition missing. But any Version of CONSTRAINT z PRIMARY KEY doesn't work such as:

CREATETABLE"Abfrage"("NumberFormatted" AlphaNumeric(48),PRIMARYKEY("NumerFormatted"))

This only brings up another error: the databasemodule can't find the index 'Index_6994414E_8E0F_44DF'

Fehler 0xc002f210: 1-SQL-Task "Vorbereitung": Fehler beim Ausführen der Abfrage "CREATE TABLE "Abfrage" ( "NumberFormatted" AlphaN...": "ERROR [42000] [Microsoft][ODBC Paradox Driver] Das Datenbankmodul kann 'Index_6994414E_8E0F_44DF' nicht finden. Stellen Sie sicher, dass es sich um einen gültigen Parameter oder Alias-Namen handelt, der keine ungültigen Zeichen oder falsche Zeichensetzung enthält und dessen Name nicht zu lang ist.". Mögliche Ursachen sind folgende: Probleme bei der Abfrage, nicht richtig festgelegte ResultSet-Eigenschaft, nicht richtig festgelegte Parameter oder nicht richtig hergestellte Verbindung.

Does anyone have an idea, how to deal with this problem?

Hi all, 

I am trying to get the SSIS package deployment history (not the SSIS project project deployment). Through SSISDB.internal.packages I got five rows with a project_version_lsn field, so I guess they are connected to a project deployment as the numbers of that field match with the "Project LSN" of project versions (right click an SSIS Project-> Versions)

And old post pointed to table [msdb].[dbo].[sysssispackages], which my rows are not relevant to my question.

Does anyone figure out where to find this information (If available)?

olaf870

I had installed VS 2019 Community on Windows 10 with the SQL Server Data Tools option. It worked for a month and then I got a trial period expired message (That I don't think I should have but anyway). I Tried to uninstall and now I get the error :
Setup Failed
Unknown error (0xe0434352)(0xE0434352)

If I attempt to install Microsoft.DataTools.IntegrationServices.exe I get the same error. If I install VS 2019 again, it shows the SQA Server Data Tools as installed but Integration Services project tis not available when trying to create a new SSIS package.

What do I need to do to get the SSIS 2016 component working again?

Thanks

Jeff

Jeff Webb