![]() ![]() Tracks the extended event session xel file and offset so it can avoid processing the same data twice next time it kicks off.Spits out a more friendly json file with a list of long wait events, what resource the lock was on, what workstation/app/SP caused the lock, same data for what was effected by the lock.Strings together some ad-hoc queries to enrich the data with things like database names and stored procedure names, with additional logic to standardize the various ways SQL reports a lock context.Queries their extended event session for sql wait events.If you get really proficient in powershell, you can automate things that wouldn't have even been feasible to do manually in the first place.įor example, I have a powershell script that kicks off every two minutes. Knowing Python is good, but I would strongly recommend you try out something else as well to see if you like languages with more strict type rules. I do everything I can now in TS, and have started learning Rust as well. Going back to using Python after TS was awful, and while Python supports some aspects of typing, I was running into more issues trying to make the type checker happy than with my actual code. Found out I loved TypeScript, and the benefits of more strict typing. I started out with PowerShell as a sysadmin, moved into Python as I did more cloud/devops work, and then started with TypeScript. Regarding python, it's fine and all and a lot of people use it for a lot of things, but it's not my preference. It's often a component of most devops roles, but there can be distinctions. Something Google came up with, they have free resources available about it including books: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |