search

ironmansoftware / powershell-universal

Issue tracker for PowerShell Universal
https://powershelluniversal.com
35 stars 2 forks source link

SQL Support #555

Closed adamdriscoll closed 2 years ago

adamdriscoll commented 2 years ago

We currently use LiteDB for persistence. This doesn't work well for several scenarios; including HA.

rstolpe commented 2 years ago

What's the play here? Separated SQL DB on its own server and then the PSU on the other

adamdriscoll commented 2 years ago

That's would be the recommended setup. It would allow for redundancy of the PSU instance as well as clustering of the SQL server as well.

rstolpe commented 2 years ago

That's would be the recommended setup. It would allow for redundancy of the PSU instance as well as clustering of the SQL server as well.

Perfect :) then cache are not needed as much anymore. I'm currently setting up SQL to minimize the cache use.

Entech-Ramon commented 2 years ago

Would it be possible to make sure there is support for Azure SQL? I know there are some small limitations between on prem and Azure SQL.

Entech-Ramon commented 2 years ago

This might be more trouble than it's worth, I'm wondering if certain things that are currently managed in ps1 files can be moved over to SQL. I'm specifically thinking of Script schedules. With our current workflow in order to adjust any schedules we'll have to update code and make pull requests etc.

adamdriscoll commented 2 years ago

RE schedules in the database: It's possible but something I'm not targeting for this first iteration. I understand the appeal of that though. The idea with the code-base configuration is the ability to validate and verify changes so that's why PSU is setup like this so I would say that it is by design that you would need to update code and make PRs to change schedules.

In terms of Azure SQL support, this should also work with that. We are implementing an EF 6 database layer that can will talk to SQL server on-premises and within cloud services. Once we have that base, we should be able to add additional SQL providers pretty easily.

Entech-Ramon commented 2 years ago

Thanks for the insights @adamdriscoll, much appreciated.