Forum Discussion

wsssq's avatar
wsssq
New Member
2 years ago

Import Mode Refreshing Problem

I have a question for refreshing. I'm using Direct Query mode and I can't do many things on Direct Query mode. I can switch it to import mode. But my data set is around 50GB. But while I was refreshing my data with dual or import mode,refreshing data on this modes every time dowloading data again and again. My disc storage like empty 240 GB. First time refreshing my storage up to the 50GB it is okay. But When I refreshed my data start to dowload again to first after that its up to the 100GB. Is there any solution for this? Or am I doing something wrong?

3 Replies

  • Hello! Is your model in a star schema format? What is your data source? If it can support query folding (i.e. Synapse, AWS, BigQuery, etc) then you can implement incremental refresh. Also, what P or F SKU do you have?

  • Problema con la puerta de enlace

    Buenas si alguien me pudiera ayudar con este inconveniente que tengo cuando quiero actualizar los datos desde el servicio de PowerBI , e intentado varias cosas pero ninguna me ha funcionado , como reinstalar la puerta de enlace , actualizar el Net Framework , actualizar PowerBI y sigo con el mismo error.

     

    Error del origen de datos: {"error":{"code":"DM_GWPipeline_Gateway_SignatureNotMatchCredentialError","pbi.error":{"code":"DM_GWPipeline_Gateway_SignatureNotMatchCredentialError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"InvalidCredentialFormat - Signature does not match"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2146233033"}}],"exceptionCulprit":1}}} Table: Articulos.
    URI de clúster: WABI-PAAS-1-SCUS-redirect.analysis.windows.net
    Identificador de actividad: 905e2efc-ae72-4b38-8cd5-0fbadc0c4b28
    Identificador de la solicitud: a30d4412-11c2-451c-1914-c3975a63e94d
    Hora: 2024-08-08 13:32:02Z

    • audreygerred's avatar
      audreygerred
      Super User

      In the past when I have seen this error it has been related to permissions not being set properly on the source side. Make sure to check that your credentials are correct for teh Articulos table and that the service account or whatever you are using to credentialize on teh gateway has the necessary permissions on the table.