In v20.10.43, I’ve come across a bunch of auto-generated views with a _BCV suffix.
Are they used for merged (incremental?) loading in the next layer, or what’s the purpose of these views?
Why do they need to be redeployed whenever I do a managed deployment?
And why does the SQL Clean Up Wizard delete them when they’re being used?
(I haven’t tested if this could happen in a v6284.1 MDW)
Best answer by Thomas Lind
View original
+5
Hi
I searched through old tickets and found the following.
This is to handle illegal characters in table names when using ADO as transport.
I also found this explanation.
From what I can see in the code, BCV views are used when a NAV table contains a dot (.) in it's name.
That apparently can't be translated directly, so it needs to be replaced by an underscore (_) and then the view gets a postfix called _BCV.
Are you using a NAV adapter data source for this?
Hi
I’m using a CData CSV data source that scoops up a bunch of files with “.csv” (i.e. a dot) as suffix.
Converting dots to underscores (like NAV data sources) is fine … what’s strange is, however, that they always need deployment even though nothing has changed.
Also, the clean-up tool deletes the tables … and then they surely need to be redeployed 😀
Thanks, Søren
+5
Hi
What version are you in?
It only does this when you do differential deployment, not when you use the Deploy Only modified tables and views, right?
You can resolve this by removing the .csv part of the table name.
Nice, thanks
I’ve never noticed this setting … that’ll surely fix the issue.
And yes, it’s only when doing differential deployment.
+5
Hi
Good. I tried to see if it behaved the same for me, but it does not work like that.
So it will be more than just it being in version 20.10.43 and having . in the name.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
