Protect the Excel files generated by SSIS package-Part I
It is not only the data within the database that requires protection but any report generated using SQL Server needs to be protected before being mailed
2010-10-28
12,266 reads
Integration Services (SSIS)
SSIS Events and Handlers
Explore how SQL Server 2008 Integration Services' events are triggered during package execution and the ability to react to their outcome through event handlers.
2010-09-30
2,337 reads
2010-09-20
3,068 reads
2010-09-13
2,984 reads
Top 10 SQL Server Integration Services Best Practices
Learn the top 10 best practices for large scale SSIS packages from a real world DBA.
2010-09-13
13,631 reads
2010-09-07
3,220 reads
Automatic Restart of SSIS packages after Failover or Failure
SSIS makes it possible to minimize work lost by starting after the last successfully executed control flow task upon restarting a failed package. From there, one challenge many seek to overcome is automatically restarting that package at that point without any manual intervention. This would make it possible for your SSIS packages to be running, your cluster to failover, and your SSIS packages to restart and complete without you having to respond to the failover and restart them.
2010-09-03
2,181 reads
Parsing an ADO result set into a comma separated string in SSIS
This article describes a way to parse a result set in SSIS using For each loop container, variables and SQL task.
2010-09-01
9,391 reads
2010-08-30
2,934 reads
A deadlock was detected while trying to lock variables in SSIS
Error: 0xC001405C at SQL Log Status: A deadlock was detected while trying to lock variables "User::RowCount" for read/write access. A lock cannot be acquired after 16 attempts. The locks timed out. Have you ever considered variable locking when building your SSIS packages? I expect many people haven’t just because most of the time you never see an error like the one above. I’ll try and explain a few key concepts about variable locking and hopefully you never will see that error
2010-08-26
3,320 reads
Blogs
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Advice I Like: In 100 Years
By Steve Jones
In 100 years a lot of what we take to be true now will...
dataMinds Saturday 2026 – Slides
At Saturday the 21st of February I’m presenting an introduction to dimensional modelling at...
Forums
is it true we cant debug c# scripts in ssis anymore under vs
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
Missing the Jaro Winkler Distance
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
Question of the Day
Missing the Jaro Winkler Distance
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers