See my code on page 4 of this thread - and it's Mike 😉

I can't go through the details of CLR with you- but basically it's c# that you publish...

I'd try the CLR approach.

Also it sounds like you could match directly rather than via fuzzy, and perhaps only run jaro winkler on an unmatched subset?

When I use this in...

I'm a fan of the flexibility of tablixes (tablices?) but one thing I find really awkward/annoying about them is when saving as XLS, you inevitably end up with merged cells...

Thanks, yes, there are those obvious problems- if a report hangs for some reason (something I haven't seen in 4 years, fortunately), it would be a manual-cleanup job. We've...

Well thanks for the hints!

"Powershell for a better pie!"

Ok, some further reading has left me a bit confused here. Basically running a batch, which can be done by a user, just involves running the single stored procedure...

Okay, that's interesting. So literally instead of using a cmdshell, initiate a powershell, even for running an executable off the command line? I have used powershell for a few...

Once you've gone through the trouble of securing xp_cmdshell, setting up a proxy etc, in my view, one of its biggest benefits, is plain old simplicity.

In our case, we use...

I got jaro-winkler functionality working by exposing a C# class via CLR- any thoughts on how this might compare speed/efficiency wise? I figured C# would be a more efficient /...

Some similar powershell scripts I cobbled together.

Script jobs and some other server objects I'm interested in:

Note that there should be as many "paths" as there are "output paths" if you...

Scrub that, just realised the foibles of using NOT in an FTS query hence the strange production rules in the original article. I will post my working version when...

I love this bit of code.

One thing, I found the exclude operator worked a bit inconsistently for me. For example, searching for words that contained hyphens didn't work correctly,...

Looks like your trigger captures more than just table changes, which is cool - presumably all sorts of alter/create statements include sprocs would find their way into that audit trail....

I've not come across DDL triggers before- they look quite interesting and a relatively sensible place to capture changes.

I can see these being helpful for evaluating roll-out accuracy....

Makes sense.

Of course, I will add that meeting that level assurance is more important in our environment where there are only 3 IT professionals running the databases, none strictly speaking...