Open Source PowerShell Database Software

PowerUpSQL is a PowerShell toolkit focused on auditing, discovering, and post-exploitation activities for Microsoft SQL Server environments. It bundles a wide range of functions that help enumerate SQL Server instances, configuration settings, and potentially risky features so operators and testers can quickly understand an instance's security posture. The project is aimed at internal penetration testers and red-teamers but is also useful for database administrators and defenders who want to inventory SQL Server attack surface and hunt for misconfigurations. PowerUpSQL can surface things like weak configuration flags, dangerous surface (for example, features that may enable code execution from SQL), credential material exposed in configuration, and cross-instance trust relationships such as linked servers. The codebase is implemented primarily in PowerShell, organized as a module with many discrete functions, and includes helper scripts and documentation for usage scenarios.

- Suitable for engineering, ERP, research tasks. - Can be easily used as a local database in C# application. - Can be run as "listening" service on a local machine or a server. - Nested data structures supported. - PowerShell interface. See project Wiki for more.

Este proyecto es un sistema de respaldo de Bases de datos SQL. Por ahora solo se ha desarrollado para MySQL, se espera ajustar para más bases de datos relacionales

Instance migrations and best practice implementations have never been safer, faster or freer. dbatools is PowerShell module that you may think of like a command-line SQL Server Management Studio. The project initially started out as just Start-SqlMigration.ps1, but has now grown into a collection of over 500 commands that help automate SQL Server tasks and encourage best practices. dbatools now works on PowerShell Core (aka PowerShell 6+). This means that you can run a large majority of our commands on Linux and macOS. In addition to the simple things you can do in SSMS (e.g. starting a job, backing up a database), we've also read a whole bunch of docs and came up with commands that do nifty things quickly. By default, all SQL-based commands will login to SQL Server using Trusted/Windows Authentication.