It is also worthwhile to check the environment at the same time, I have a
flag for development test and production, you do not want to run tests
against your production database!
On Fri, May 7, 2010 at 3:06 PM, David Richards ausdot...@davidsuniverse.com
wrote:
I have a Version table that has
Hi Folks,
We have a product comprised of desktop apps (.NET and native) that talk to
SQL Server 2008.
The database and apps get installed at client sites that we have no ongoing
control over. We use a table in the database to track schema versions and
our database creation / upgrade script uses
Matt, I like to put two magic numbers in a special database table: The
change number, The compatibility number.
The first increments whenever the schema changes. The second increments only
when a breaking change is made.
The app startup code can use these numbers to determine if it can run
As soon as I read 'compatibility number' in your email I remembered we
discussed this internally long ago.
Just recently I was thinking of tracking the required version for each app
that connects to the database but after thinking about it I don't think
we'll need that level of granularity. A
I have a Version table that has a single column, single row with a
version number in the form A.B.C.D. I started doing this to follow
the same version standard as my apps. So the number would be:
A - Breaking change
B - Non breaking change (eg additional table, additional column with default)
C
