Jiwa

Yes I know the copy is quick, the export is painfully slow on a certain big database we both know hence why it's easier to go to blob storage first as grabbing the bacpac from there is reasonably quick and does hold up use of SSMS.

Going back to Ryan's original question of running under Linux(cheaper database), have you considered MySQL, or is it you'd prefer not go near supporting two database platforms?

SBarnes wrote:Going back to Ryan's original question of running under Linux(cheaper database), have you considered MySQL, or is it you'd prefer not go near supporting two database platforms?

The licencing cost of SQL Server for Linux I believe is the same as on Windows. The difference is only you no longer need the Windows licence (which really isn't that much). The are other benefits for certain organisations to use SQL Server for Linux, mainly those already with a well establish Linux environment and skills.

SBarnes wrote:have you considered MySQL, or is it you'd prefer not go near supporting two database platforms?

Yes, we have considered it, and it's a very big deal for us to make the application work with MySQL (not hard, just a lot of grunt work), and it would add another dimension to our support and testing matrix.

Any effort put into supporting MySQL (or MariaDB which is the same thing, but that's what many distros are giving first class support to - such as Debian) I'd rather be part of a next generation SaaS product offering.

SBarnes wrote:have you considered MySQL

go stand in the corner and count the spiders.

pricerc wrote:

SBarnes wrote:have you considered MySQL

go stand in the corner and count the spiders.

more seriously. MySQL is owned by Oracle. I trust them less than Microsoft.

PostgreSQL might be a better fit. It has a more complete SQL implementation.

Actually the SaaS as the licensing model and an API seems to be the new norm in most cases these days.

pricerc wrote:PostgreSQL might be a better fit. It has a more complete SQL implementation.

PostgreSQL, MariaDB and SQL Server are the 3 I'd like to support.

And if anyone mentions a NoSQL like MongoDB you're gonna be slapped!

Mike.Sheen wrote:

pricerc wrote:PostgreSQL might be a better fit. It has a more complete SQL implementation.

PostgreSQL, MariaDB and SQL Server are the 3 I'd like to support.

And if anyone mentions a NoSQL like MongoDB you're gonna be slapped!

at my last 'real' job, there was a CouchDB (also a JSON document store) for holding in-bound orders from a web site. For that purpose, it wasn't bad, although maintenance was a right PITA. It's advantage was a really simple replication between the web host and a server in our DMZ, from where we loaded the orders into a real database.

For any other purpose, I'm with Mike.

pricerc wrote:at my last 'real' job, there was a CouchDB (also a JSON document store) for holding in-bound orders from a web site. For that purpose, it wasn't bad

And for that, CouchDB would have been perfectly appropriate to use.

But I wouldn't use something like CouchDB as the data store for Jiwa or anything like Jiwa - not that you suggested we should - but you still mentioned it....

/me slaps Ryan