Adam Anderson

Data warehouse developer for the Microsoft data platform. DevOps engineer for databases and whiskey lover extraordinaire

[The Late Show @colbertlateshow]

20 years later, and ‘The Lord of The Rings’ is still the greatest trilogy ever! @StephenAtHome, @JonBatiste and some very special guests recorded a rap song to celebrate 20 years of this iconic movie! 🧙‍♂️#LSSC

[Adam Anderson @SQLPioneer]

#GitHubCopilot is an interesting experiment that makes suggestions of complete functions based on what the developer is typing. This is a really good article discussing the Quality of Auto-Generated Code https://t.co/iJVtKlPONr via @oreillymedia

[Adam Anderson @SQLPioneer]

I have been a fan of this series for 20 years and have listened to all 14 books multiple times each. I am so excited that The Wheel of Time - Season 1 is finally going to be a "TV" series! https://t.co/18p7vfAhTo

[Adam Anderson @SQLPioneer]

@SQLEspresso @SqlrUs Nice I’d like to try that one someday.

[Adam Anderson @SQLPioneer]

@SQLSwimmer What training or documentation material did you use? I would love to read more on how to do it.

[Adam Anderson @SQLPioneer]

Very interesting article on tech worker burnout and what can be done about it. https://t.co/HKZYiSJv40 via @ZDNet & @OwenRDHughes

[Adam Anderson @SQLPioneer]

@GroupByConf Thank you @GroupByConf for giving me the opportunity. Please feel free to reach out and ask me questions, I’m happy to help.

[Adam Anderson @SQLPioneer]

@abhi2434 You can never say always, but I believe that GROUP BY is more efficient than DISTINCT in almost all situations.

[Adam Anderson @SQLPioneer]

@SqlrUs That sounds like a demo for the next conference right there

[Everyday Astronaut @Erdayastronaut]

This is one of the coolest shots of a Falcon 9 landing I’ve ever seen!!! I love how the engine violently reorients the stage on ignition and how they plan that into the landing trajectory. Such impressive engineering. B1060-8 just became B1060-9! 🙌

[Adam Anderson @SQLPioneer]

@_AlexYates_ I know it is annoying to create a separate build.yml for each DB, but it is worth it an easier to maintain.
trigger:
branches:
include:
- master
paths:
exclude:
- folderName
stages:
- template: template.yml
parameters:
database: dbname

[Adam Anderson @SQLPioneer]

@_AlexYates_ Sorry, phone edit got me. Create template.yml. Then create build.yml for each DB calling the templatate.yml. The advantage is build artifacts created for each build are in their own pipeline.
Control builds with trigger: paths: exclude: folder

[Adam Anderson @SQLPioneer]

@_AlexYates_ This is an interesting situation Alex. When we ran into this we ended up creating a centralized template.unless. E then created individual builds for each database. Then we called the centralize template from each build.

[Elon Musk @elonmusk]

This is not CGI https://t.co/VOivE97vPR

[Adam Anderson @SQLPioneer]

Christmas Morning - SNL https://t.co/PlB7SfADkU via @YouTube

[Rob He/Him - Not here @sqldbawithbeard]

Without PASS, I would not be where I am today. From joining my local User Group and attending their SQL Saturday to my last SQL Saturday as a speaker.

Knowledge, guidance, friendship, support, employment have all come my way due to the community.

It being gone will be sad

1/

[Adam Anderson @SQLPioneer]

Advanced Development Pipelines https://t.co/obVEahHzaq #PASSsummit
Please join my session at #PassSummit2020 #PASSSummit on Azure DevOps Pipelines.

[Adam Anderson @SQLPioneer]

@IrishSQL Wow, just wow. Like that's not going to cause problems to adjudicate.