Is DBSS actually required in a Slice worksheet?

Arc & Slice
,
1

I had a look at the documentation and hands on guide for Slice and didn’t find an answer to the question “in Slice is DBSS required to send string data?” This was a quirk of Perspectives that strings couldn’t be updated using DBSW and required DBSS which had the implication of being quite bad for performance since DBSS were not batched and got executed one-by-one. (Which seems to also be the case in Slice, I guess the reproduction of functionality was very faithful to the original.)

After doing a quick test to update string data via DBSW with Slice it would appear that this works perfectly fine and this limitation for updating strings isn’t present. So I guess fair enough that DBSS is included only for backwards compatibility with worksheets that were designed in Perspectives. However, what is missing is a clear statement that if using slice that DBSS is completely unnecessary (and should in fact be avoided) and DBSW should be used instead.

Is there in fact any use case at all where DBSS might actually be needed if using Slice?

@rcantor @Vincent

2

DBSS uses DBS to send data. In Slice, DBSW can be used for all data types.

1 Like
3

Thanks Andrey,
We figured this out for ourselves already via experimentation. However, for anyone who learned in Perspectives old habits can be hard to break and it’s natural to automatically use DBSS if you know you need to send string data. I kind of think there should both be documentation online explaining that DBSS is there only for backwards compatibility but should never be used and some warning built into Slice which even prompts the user to replace DBSS with DBSW because the performance impact of having a range of DBSS formulae is really severe.

2 Likes