SQL Timestamp Incremental Load Issue
An incremental load is implemented based on timestamp, using a view to update a fact table. • The fact table contains multiple KPIs coming from different source tables. • Two main KPI tables are included directly in the view and drive the incremental logic (their timestamps change). • Additional KPIs come from other source tables, which are LEFT JOINed to the view. During an incremental run: • Main source tables are updated → timestamp changes • Other source tables are NOT updated → timestamp unchanged • Because of the LEFT JOIN, missing values from these tables are returned as NULL • These NULLs overwrite existing values in the fact table Example Fact table (before load) id app_number score 1 333 5 Source tables • source1, source2 → timestamps updated (drive incremental load) • source3 → timestamp unchanged Stored procedure logic MERGE fact_table tgt USING ( SELECT app_number, ISNULL(score, 0) AS score FROM vw_main_kpis v LEFT JOIN source3 s3 ON v.app_number = s3.app_number ) src ON tgt.app_number = src.app_number WHEN MATCHED THEN UPDATE SET tgt.score = src.score; Result (incorrect) id app_number score 1 333 0 Existing data is lost.
Integration Services service "Computer Name" failed with error: "Class not registered"
Hi All, See below error when trying to login to intergration service. Does anyone know how to resolve? Connecting to the Integration Services service on the computer "Computer Name" failed with the following error: "Class not registered". This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance. RegardsSQL Server 2017 – CLR was loaded in an unsupported manner (All SSIS jobs failed)
Hi, We are facing a critical issue in our SQL Server 2017 instance. When trying to use a built-in CLR function or running SSIS-related jobs, we are getting the below error: The Common Language Runtime (CLR) was loaded in an unsupported manner. This can occur if an extended stored procedure or OLE Automation object running in SQL Server calls into managed code before the CLR integration runtime host loads the CLR. You need to restart SQL Server to use CLR integration features. Steps tried so far: Restarted SQL Server service Restarted the entire Windows Server Verified .NET Framework version (4.7.03062 installed) Confirmed CLR integration is enabled (sp_configure 'clr enabled', 1) All SSIS jobs are failing due to this issue. Any suggestions, please?Transaction was deadlocked on lock resources with another process ??
Hi, We have a cognos datastage job that updates a table. It fails with an error that the table is locked., see below ini_PerformanceManagement_tblEmployees,0: ODBC function "SQLExecute" reported: SQLSTATE = 40001: Native Error Code = 1,205: Msg = [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 67) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. (CC_OdbcDBStatement::executeUpdate, file CC_OdbcDBStatement.cpp, line 1,058) Anyone any ideas about how to resolve this? Thanks for your time, Ollie
Linked Server Selection Query Fails with "MS DTC has stopped this transaction"
Hi everyone, I’m currently setting up a Linked Server from our head office (server A) SQL Server to a subsidiary unit (Server B) SQL Server. The Linked Server connection tests successfully, and I can log into server A from server B and can using query. However, when I try to execute a query using a 4-part name through Linked server, I encounter the following error: Msg 8522, Level 16, State 3, Line 1 Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction. Environment Details: Head Office (server A) SQL Server: SQL Server 2008 R2 (already upgraded pack SP3) Windows Server 2012 TLS 1.2 enabled MS DTC service is turned on Subsidiary (server B) SQL Server: SQL Server 2016 Windows Server 2016 Standard (64-bit) TLS 1.2 enabled MS DTC service is turned on Networking: The B server connects via VPN to be on the same network as server A Ping and Telnet tests (IP and port) from both sides work fine SQL login from server A to server B(via IP and port) is successful USING PROVIDER: i have try to using SQLNCLI11 and MSOLEDBSQL, but both till error DTC. Linked Server test connection: Success Update, insert query: it's ok, but when i try selection query, i got error DTC has stop this transaction. example: SELECT * FROM [LinkedServerName].[DatabaseName].[dbo].table Has anyone faced a similar issue? Could this be a MS DTC configuration mismatch or network security/firewall/DTC port range issue? Any guidance on how to properly configure MS DTC across different servers/domains/VPNs would be highly appreciated. Thanks in advance!
Pet project on SQL Server 2022 platform
Hello, world! I would like to share my pet project on SQL Server 2022 platform. I have created a DWH solution that includes many MS's best practices and interesting features such us: ETL process with data cleansing and MDM that easy expand Documentation CI/CD Functional ETL test Ready analytical templates Time intelligence New & returning customers Cluster customers based on spending volume Product ABC classification Basket analysis Events in progress https://dev.azure.com/zinykov/NorthwindBI Unfortunately in SQL Server 2025 will be no DQS & MDS...
SSIS Debug Spawns 2 DtsDebugHost.exe and Freezes
Operating System: Windows 10 Enterprise Visual Studio: 2022 Enterprise (x64) Target SQL Server: SQL Server 2019 On many packages, running the package in debug mode (x64, ??) locks up the UI (windows message "Visual Studio is Busy"). Task Manager shows 2 instances of DtsDebugHost star C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn each with different -regas {guid} command lines. For packages where this doesn't happen only 1 is spawned. Killing the DtsDebugHost.exe packages frees up the Visual Studio GUI but ends the debug session. These packages do not use any 3rd party components.SSIS Packages (Randomly) Freeze on Breakpoint
TLDR: using Visual Studio 2022 and (latest) SSIS, packages freeze on breakpoint (if set) Since upgrading to VS 2022, many of my packages (including those w/out Scripting or any 3rd Party Components) freeze when they reach a debug breakpoint. I can't interact with the GUI, and the only solution is to kill VS in Task Explorer. The same package runs without issue without a breakpoint.
Error 0x80004005 during SSIS package execution with SSAS source
Hi. I've created a SSIS package utilizing a SSAS source (VS 2022 Developer Edition, SSAS 2019 15.0.35.48). I can confirm that I can connect to my SSAS source through OLE DB connector and run MDX queries: When I run the package, "Connection Test" step passes (it runs a simple MDX query against the SSAS source to ensure we can connect to source): But data flow task fails on OLE DB Source as follows: My problem is that there is nothing in error message which can help me where is the exact problem. I've seen many posts on this problem, but none of them has worked for me as each focus on a part of error message following the above message, which doesn't exist in my case (e.g. "Communication link failure" or "TCP Provider: The specified network name is no longer available"). Please help. Thanks in advance.
SSIS Odata source problem - No object exists with the ID 11.
Hey guys, I am currently facing a problem on my SSIS package and all your help would be very helpfull. Here is the scenario,I have a data flow with a Odata Source inside, here is the image bellow. I can confirm that the connection is working and the filter options are also working because I can view the data: Unfortunately when I run the package I get the following error: [SSIS.Pipeline] Erro: No object exists with the ID 11. [Fonte de Dados OData 1 [2]] Erro: The Fonte de Dados OData 1 was unable to process the data. Excepção de HRESULT: 0xC0047072 [SSIS.Pipeline] Erro: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Fonte de Dados OData 1 returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. There is nothing else on the data flow, I just cant understand what is going on. Appreciate all the help.
