Our team successfully applied the target-state deployment approach for quite a while and never saw the need for an alternative migration script-based approach (which would not have the Windows platform limitation). The reason for the latter is the lack (so far) of cross-platform tooling for building Visual Studio database projects and deploying the resulting DACPACs. Plus, they have way more smarts built in to tell you what's been happening.In my day to day work as a consultant on customer projects the typical tech stack involves having a Microsoft SQL Server (MSSQL) for persistence with several ASP.NET Core web APIs on top, and a web-based UI, which nowadays I like writing in React.īeing in home office mode for several months now, I am developing on my personal MacBook Pro - in a Parallels Windows VM. If you need to know what's happening on your SQL Server on a regular basis, this is usually more lightweight than running Profiler. There's also a "Profiler" extension for Azure Data Studio, but.that's actually Extended Events. The Extended Events people are like vegans, crossfitters, and atheists: they can't wait to tell you about their religion.) Extended Events is the replacement for Profiler, but the thing is, if you're just getting started, you're going to want to use SSMS's excellent wizard for setting up a new XE session - meaning, you still need SSMS. (This isn't really a solution, but I know someone's going to suggest it, so might as well get it out of the way. (Disclaimer: I'm one of the sp_BlitzCache authors.) You can run it from anything app runs T-SQL, like Microsoft's new cross-platform SQL Operations Studio. Yes, right now, even as you're reading advice on a web site. SQL Server is already gathering this data for you on every supported version/edition. The open source sp_BlitzCache analyzes the most resource-intensive queries in your plan cache - without starting a heavy-overhead trace or XE session. (That's how I manage SQL Server personally - I'm a Microsoft Certified Master of SQL Server, and I've been using Macs since the mid-2000s.) After all, if you're managing SQL Server, you probably need SQL Server Management Studio anyway, and that's still Windows-only. Server-side traces can output to file or to table - I'd caution against writing the trace data into a table on the same server that you're monitoring because that'll have a performance impact. (Heck, I recommend this to folks even when they have Windows on the desktop.) SQL Server Central has a good Stairway to Server-side Tracing. You don't get the Profiler GUI, but the good news is that this kind of tracing is faster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |