Question Schema Holder database - original version bad?

Chris Hughes

ProgressTalk.com Sponsor
Hi

I'm starting to look into / read a bit more about schema holder db's with SQL Server.
One of the docs I came across states to create a new schema holder to use new features.

Soon I will be making use of Progress 11.4 (jumping from 10.2b), and the approach has been to convert this database to 11.

So question is - if the DB is converted does this tick the same box and enable all the latest features - or should I create a new one?

And generally is there a way with converted databases of telling which version they were created as, i.e. if there has been a history of conversions.

Thanks

Chris
 

Cringer

ProgressTalk.com Moderator
Staff member
We've had an issue when we moved from 10 to 11 with our schema holders that we would get loads of warnings in the log files. The only way to fix this was to recreate the schema holders in 11. It didn't stop things working but it did mean our live log file bloated by hundreds of MB per week and it was all noise, making real issues much harder to spot.
 

TheMadDBA

Active Member
You are better off making a new schema holder. I actually did run into issues (connection issues and random disconnects/errors) with a schema holder created under 10.2A while trying to use 10.2B that forced us to recreate the schema holder.
 
Top