Anyone ever program in a PVCS Tracker database?

I’m in the process of taking over support duties for our company’s PVCS Tracker and Version Control databases. One of the things I was told at the outset was that the databases are administered remotely by the software vendor and there’s no way that I can build my own reports to run against them, or even access them through an ODBC connection.

But I’ve already proven that I can log on to these databases using ODBC. So now it looks like I’ll be able to do some custom reports as well, or is there some “gotcha” that I haven’t run into yet?

Nah, we’ve done lots of it. The problem with the database is that it’s hard to reverse-engineer. Lots of tables with headers like x1,x2,x3,x4, etc. You’ve got to do some legwork to figure out how it’s put together.

But in the end, it’s just an SQL database. We pull information out of it all the time to put on our development cockpit.

I’m afraid I won’t be able to answer questions about it, though. The last time I built a query against it was about 2 years ago, and I’ve forgotten everything I knew. We have other guys doing development work against it.

Thanks for your reply.

It sounds as though if I can configure this on the desktop of someone who’s got ERWin on their desktop, I can get them to print out the table relationships.

One thing I found was that for a given schema, the PK of the main issues table seemed to be offset from the values which the users see by a constant value. Does this sort of thing remain consistant, barring unusual events like software upgrades?

Sorry, I don’t have an answer for that.