SQL Replication Scripts Performance

[Facundo Gauna]

We have one document that contains two arrays of subdocuments and we need it in our Azure SQL.

We are seen the occasional SQL timeout when we reset a script because the Azure database is under heavy load. We have indexes on the SQL database side. 

The data replicates to SQL eventually because it Raven suspends and retries.

What's the best strategy for setting up the SQL replication scripts for better performance?

 - One Script that replicates the document to 3 SQL tables?

 - 3 Scripts that each replicates the document to 1 table? 

[Oren Eini (Ayende Rahien)]

RavenDB will recover from errors in SQL, yes.

Please make sure that the DocumentId column is indexed.

If you are looking at reducing the load on the server, has a single task for the 3 tables, this would serialize requests.

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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Facundo Gauna]

Thanks Oren.

Just to clarify, this would reduce the load on SQL right? Raven has been performing great.

Lastly, is there a way to change the batch size that Raven replicates to SQL?

[Oren Eini (Ayende Rahien)]

You can change Raven/MaxNumberOfItemsToProcessInSingleBatch, but note that it will also impact indexing.