Having trouble enabling Incremental Refresh

[GuidoMS]

Hi,

I've been trying to apply incremental refresh to some of out tables with our dataset but so far, didn´t succeed. Did the following:

- Create new parameters RangeStart and RangeEnd.

- Apply parameters to new filter on one table called VW_TURNOS

- Configure Incremental Refresh setting up months to refresh, etc.

My team has been troubleshooting this for a long time searching on forums (this one and others) and trying new methods with no positive result. The problem now is that our ammount of data exceeds the 1024mb limit for the refresh. So our solution is to leave behind data from previous years, which is a limitation on potential analysis agains previous years.

I don't fully understand Query Folding concept but from what i've seen, if "View native query" is greyed out on the new step with applied parameters, then it's not folding (others say it's not 100% confirmation).

For reference we use:

- FireBird 3.0 SQL server for database.

- IBexpert as our data base Manager 

- ODBC to connect to Power BI.

- Working with Power Bi PRO (license by user)

Created View structure (VW_TURNOS)

CREATE OR ALTER VIEW VW_TURNOS(
CODIGO,
MEDICO,
ESPECIALIDAD,
FECHA_TURNO,
SOBRE_TURNO,
HORA_TURNO,
PRESENTE,
PACIENTE,
OBRA_SOCIAL,
IDPLAN,
OPERADOR,
FECHA_ALTA,
MEDICO_SOLICITANTE,
OPERADOR_2,
ASUCARGO,
HORA_ALTA,
HORAPRESENTE,
CONFIRMADO,
USUARIOCONFIRMA,
FECHACONFIRMA,
CANCELADO,
IDUSUARIOCANCELA,
ALTAMISMODIA,
ATENDIDO,
TIPOIVA,
SECTOR_TURNO,
SECTOR_PRESENTE,
HORA_ATENDIDO,
USUARIO_ATENDIDO,
CANCELADO_FECHA,
SECTOR_CANCELADO,
SECTOR_CONFIRMADO,
USUARIO_BAJAPRESENTE,
FECHA_BAJAPRESENTE,
SOBRETURNO_ESPECIAL,
IDMOTIVOBAJAPRESENTE,
IDCENTRO,
IDCONSULTORIO,
EVOLUCIONADO,
IDMEDICOEFECTOR,
IDCENTRODERIVADOR,
IDCENTROLIQUIDA,
CENTRODERIVADOR)
AS
select
MAESTRO_TURNOS.CODIGO,
MAESTRO_TURNOS.MEDICO,
MAESTRO_TURNOS.ESPECIALIDAD,
MAESTRO_TURNOS.FECHA_TURNO,
MAESTRO_TURNOS.SOBRE_TURNO,
MAESTRO_TURNOS.HORA_TURNO,
MAESTRO_TURNOS.PRESENTE,
MAESTRO_TURNOS.PACIENTE,
MAESTRO_TURNOS.OBRA_SOCIAL,
MAESTRO_TURNOS.IDPLAN,
MAESTRO_TURNOS.OPERADOR,
MAESTRO_TURNOS.FECHA_ALTA,
MAESTRO_TURNOS.MEDICO_SOLICITANTE,
MAESTRO_TURNOS.OPERADOR_2,
MAESTRO_TURNOS.ASUCARGO,
MAESTRO_TURNOS.HORA_ALTA,
MAESTRO_TURNOS.HORAPRESENTE,
MAESTRO_TURNOS.confirmado,
MAESTRO_TURNOS.confirmado_idusuario,
MAESTRO_TURNOS.confirmado_fecha,
MAESTRO_TURNOS.CANCELADO,
MAESTRO_TURNOS.IDUSUARIOCANCELA,
MAESTRO_TURNOS.ALTAMISMODIA,
MAESTRO_TURNOS.ATENDIDO,
MAESTRO_TURNOS.TIPOIVA,
MAESTRO_TURNOS.SECTOR_TURNO,
MAESTRO_TURNOS.SECTOR_PRESENTE,
MAESTRO_TURNOS.HORA_ATENDIDO,
MAESTRO_TURNOS.USUARIO_ATENDIDO,
MAESTRO_TURNOS.CANCELADO_FECHA,
MAESTRO_TURNOS.SECTOR_CANCELADO,
MAESTRO_TURNOS.SECTOR_CONFIRMADO,
MAESTRO_TURNOS.USUARIO_BAJAPRESENTE,
MAESTRO_TURNOS.FECHA_BAJAPRESENTE,
MAESTRO_TURNOS.SOBRETURNO_ESPECIAL,
MAESTRO_TURNOS.IDMOTIVOBAJAPRESENTE,
MAESTRO_TURNOS.IDCENTRO,
MAESTRO_TURNOS.IDCONSULTORIO,
MAESTRO_TURNOS.EVOLUCIONADO,
MAESTRO_TURNOS.IDMEDICOEFECTOR,
MAESTRO_TURNOS.IDCENTRODERIVADOR,
MAESTRO_TURNOS.IDCENTROLIQUIDA,
MAESTRO_TURNOS.idcentroderivador
From MAESTRO_TURNOS
where Maestro_Turnos.fecha_turno >= '2020-09-01'
And Maestro_Turnos.fecha_turno <= dateadd (3 month to current_date)
And not coalesce (Maestro_Turnos.presente, -1) = -1
And not coalesce (Maestro_Turnos.idcentro, -1) = -1
And not coalesce (Maestro_Turnos.obra_social, '') = ''
;

Please let me know if more information is needed to help us diagnose our issue. 

[amitchandak]

@GuidoMS , Usual, when we set up incremental Range, in file we set only set 1-month range RangeStart and RangeEnd. and we give long data archive range

and then load it service. But if you are a pro user, you will lose data with every republish

[GuidoMS]

Thanks for the quick answer. I'll look for those settings later today.

If we don't have a Premium account then older data is lost?

From what i understand about incremental refresh, we can update data uploading or editing data frox X past months, acumulating older unchanged data. Is this concept correct? 

Then maybe the limitation with a pr account is that we can acumulate older data if the set size is bigger than 1gb. 

Can we get to 10gb with only 1 premium user (manager of the set)?