Tim Cartwright

@jmezach here are the changes made to a normal SSDT project to enable the analysis: Turned on, all rules enabled: ` True` Enabled, some rules disabled: ` True -Microsoft.Rules.Data.SR0011;-Microsoft.Rules.Data.SR0012;-Microsoft.Rules.Data.SR0016` Enabled,...

OR.... create two piplines. Ones to lint / build. The other to build and package release manual.

Matt, could use your help with this. Or I could muddle through it. :)

Even worse, other users cannot even see other users job run details. So each admin has to check on the results of their own jobs... AGAIN, This is for Azure...

I am experiencing this issue as well. Actually found this by googling powershellgallery 301 redirect. My vote goes to using a 302 like @dahlbyk suggested. Is there a valid reason...

Thanks guys, I have been away for a while, I will get right on it.

NICE, I will do it as soon as I can. We have been doing a major conversion at work from one type of system to another, and I have been...

I did something like this for AppInsights (talked about it on this [SO post](https://stackoverflow.com/a/78550020/1988507): ```c# using System.Data.Common; using System.Diagnostics; using Microsoft.ApplicationInsights; using Microsoft.ApplicationInsights.DataContracts; using Microsoft.EntityFrameworkCore.Diagnostics; namespace SvApi.AppInsights; public class EFCommandInterceptor...

@roji It actually isn't that slow, I understand there is a performance cost. Yes, it can be brittle. I go into that a bit [here](https://gist.github.com/tcartwright/30cd6673c53954c2493d9f7ca55350dc?permalink_comment_id=5072562#gistcomment-5072562)

Running this even against small (10mb) XEL files is painfully slow.