pricerc wrote:At first, I thought it was stuck on restoring the bacpac file, but I was just being impatient.
Yeah - I'm yet to drill into why it takes so long to either export to bacpac or import from BACPAC, but it's slow everywhere when compared to the traditional backup and restore operations. In previous versions of Jiwa 6 we went to insane efforts to package demo and new databases into our own format (a .zip containing SQL queries and bulk data copy aka
BCP) and there was literally several thousand lines of code which used to perform the restore of a database. All replaced now with about 10 lines of code in version 7 which now uses SMO to operate on BACPAC files instead.
Apologies for the increased time in creating a new demo database or a blank one, but it made sense to hand off to an official Microsoft SQL library (SMO) to handle those operations for us instead of our awesomely fast custom one, which would have been prone to failure in future versions of SQL and probably have not handled odd edge cases, or a wider range of supported SQL Server versions.
pricerc wrote:SBarnes wrote:I suppose you could test it under docker
there's a whole ecosystem I've yet to try.
I've yet to try docker, but then I almost never do the same thing twice when it comes to system deployments, so I'm not sure I'm the target market.
Docker is great, but like you I'm yet to find myself a problem where I would find it useful. One thing which I did see a use for - I did try dockerising Jiwa + SQL Server in various combinations of Jiwa and SQL server at one point to allow our support dept. to rapidly create environments for testing, but the user experience back then (and it's likely much the same now) was all CLI and it wasn't well received. If I had the time I would have layered a gui or web interface over it to make it more palatable - but... well - you probably know how it is.