How does one develop against SQL ETL in RavenDB 4?

[Michael Third]

My company has been using RavenDB since 1.0 and are looking forward to RavenDB 4.  One of the challenges I've run into is that I cannot develop SQL ETL on my local machine using the Community license.

In prior versions, we could just run a development install and get full functionality.  How will this work moving forward?

Thanks,

Michael

[Oren Eini (Ayende Rahien)]

That is a good question, and I would like to have some feedback on that from the community at large.

In general, the expectation is that you can carve a single core from a license you have if you need to do such things on a regular basis on a separate server. 

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew Davey]

I'm also looking forward to v4, but hadn't noticed that limitation either. SQL replication is a key part of my application. Not being able to develop locally or run a test environment would be a real problem for me.

I'm very happy to buy licenses for production of course. What's the thinking behind limiting dev environments?

[Oren Eini (Ayende Rahien)]

Andrew,

The thinking is that these aren't dev environment, these are full blown instances that you can use for production

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--

[Michael Third]

We have 5 developers and we run the full stack on each development environment, so carving out a license won't work for us.  Absent a reasonable developer story, we'd probably look to another solution for handling these integrations scenarios which would make RavenDB a little less sticky.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

[Oren Eini (Ayende Rahien)]

Michael (and everyone else),

We tiered the licensing toward the most common usage patterns, with the professional and enterprise editions having features that are usually used in larger organizations.

I think we'll need to also introduce a developer edition, which will handle this development scenario.

As you can imagine, this is made somewhat complicate by the fact that we want to avoid people using the developer edition for production, so that require some thinking.

I would really appreciate any feedback you have on the matter

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Bruno Lopes]

Adding another data point: we also use SQL ETL in 3.5, and have some automated tests on CI agents running to check that it's working properly, since entities changing might cause it to break.

Would a batch limit work as a limitation? On dev it wouldn't be much of an issue, but limiting throughput on prod might not be acceptable.

[Michael Third]

Perhaps only allow it to run for a short time or record count, then require manual intervention?

[Oren Eini (Ayende Rahien)]

We'll have a developer edition that will allow full access to the feature set, specifically for these scenarios.

I don't like adding spokes in wheels for people, so we won't be adding stuff that will annoy you like these limits.

But these will not be production licenses.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Michael Third]

Thanks, Oren!

[Morten Kristensen]

Any update on developer licenses (allowing ETL etc.)?

[Oren Eini (Ayende Rahien)]

Should be available this week or early next.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Oren Eini (Ayende Rahien)]

In the meantime, we sent it to you directly

[Morten Kristensen]

Thanks! :D