I have existing code that moves data from LNDB-generated tables into a SQL Server data warehouse. When table definitions change and LNDB archives the old table, LNDB renames the old table, thus breaking my code.
Can LNDB be configured to leave the archived table name the same, but assign a new name to the new table? If not, can you suggest a workaround for my situation?
Thank you.
Hi,
I'm using LNDB too and I'm curious why you would want this behavior. If LNDB created a new name for the new table, and your script kept reading the old table, wouldn't your script just read the same data over and over?
Yes, but that assumes that I'll never have to reload the table into my data warehouse.