![]() This will change soon with the OP about SQL Server on Linux. Otherwise, I'm going Azure SQL Database or SQL Server if on-prem (as in, non-cloud) is needed. I'd probably pick PostgreSQL over either of the other two today for any case where my constraint was that I had to have the application run on Linux. I actually thought it must have been a fairly complex problem until I saw JetBrains implement it for multiple variations of SQL in DataGrip. They can manage it for multiple extensible languages in visual studio, but flub it for years with the fairly static TSQL. There's also things that have been broken for years now which they've failed to address - i.e., one of the most popular add-ons for SQL Studio is SQL Prompt to get actual working intellisense. Look at SQLSentry for an idea of what I mean - I only manage one 'major' database, but without that tool I'd be hard pressed to keep up. I.e., there's no real 'overview' of how the system is performing. While SQL Server does have some great features - it's also missing a fair bit of functionality. It can also be pretty high impact on a busy system.Īgent is nice because of the surrounding infrastructure -scheduling, notifications, etc - that said, it still often ends up being a hodgepodge that every admin reinvents, just using different underlying structures (cron=scheduling, system mail=notifications, etc).Īnd yeah, the HA stuff is good - with the setup becoming gradually easier with each new version, but those license costs are definitely reflecting that. ![]() It's not usually that simple with profiler, as production queries can be highly contextual and aren't always 'replayable' unless they're interacting on the same data as the original. I've heard all the high availability stuff is really good too but I've also heard that it's a pain to setup and until recently, only available in the really expensive enterprise license. These are all GUI apps that, albeit have barely been updated in a decade, but still better than most first party (or even third party) open source DB management tools out there. ![]() To this day, as far as I can tell, doing backups for most open source databases are a hodgepodge of bash scripts, cron jobs, and *dump executables, which every admin reinvents every single time. So you could basically trace a production workload and then tune it offline.ĭoing things like backups in SQL server using the agent, and running various workflows, also works really well. You can basically say "record every query that's going through the server for the next 15 minutes" – and then rerun those queries through a planner (SQL Server Tuning Wizard) to see where you can optimize them by adding certain indexes, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |