Adding a "DB Version" Table: Suggestions?

[(Pete Cresswell)]

I'm putting a little table in my DB that I'll call zstblVersion.

("..stbl" for System Table, "z" so it sinks to the bottom of the list and
doesn't look like something to do with the app)

The purpose is to let somebody look at the DB and divine which version they're
seeing.

So far, I've got 3 columns:

- VersionID
- VersionDescription (freeform text description of the changes in this version
of the DB)
- AppVersionRequired (numeric field, containing the lowest version of the front
end that will work with this version of the DB)

Opinions? Suggestions?
--
PeteCresswell

[John Bell]

Hi

I have seen several application that use this sort of thing, and they can be
useful for support.

You may want to add entries for the release date, date upgraded/installed,
the username who upgraded, previous version number, OS (at time of
install!), possibly SQL Server versions (at time of install) etc

These could be put in a readonly filegroup, although you would need to do a
little more when doing the upgrades.
John

"(Pete Cresswell)" <x@y.z> wrote in message
news:hk********************************@4ax.com...

I'm putting a little table in my DB that I'll call zstblVersion.

("..stbl" for System Table, "z" so it sinks to the bottom of the list and
doesn't look like something to do with the app)

The purpose is to let somebody look at the DB and divine which version they're seeing.

So far, I've got 3 columns:

- VersionID
- VersionDescription (freeform text description of the changes in this version of the DB)
- AppVersionRequired (numeric field, containing the lowest version of the front end that will work with this version of the DB)

Opinions? Suggestions?
--
PeteCresswell