Excel as DB limitations and issues

Help Studio
1

Hello all,

We are planning to use excel as db for couple of bot’s having below requirements:

  1. Excel has around 70k rows/transactions. We will read them into dt and process them on the necessary apps. Write back status and comments of each row to excel. Overall 2-3 interactions with excel per row.
  2. Excel has 500 rows/transactions. Read each row process them on the apps. Along with status, we need to write back each stage status to excel regularly for each item. Excel interaction is very frequent in this case.

Are there are any known issues or limitations using excel as db? Has anyone tried update excel queries on huge volume of excel rows or for frequent updates to excel?

Any inputs are appreciated. Thanks.

2

Hi @murali.yk

For 70k you might not see any issues and also why do you want to write the status for each row?

Rather you can write the status to datatable and paste it once and for all. Or if that feels likes you might miss if the bot fails in between then…if you are processing each row write the status to queue and at the end you can get the status as write to exce as well

Interacting multiple times might not be an issue but it slows the processes a bit… and also make sure you dont leave any instance without closing

And with db you cannot do a insert and if you have any merged columns you might face few issues

Cheers