Re: updating database
From: Aaron Bertrand - MVP (aaron_at_TRASHaspfaq.com)
Date: 05/03/04
- Next message: kman: "JDBC driver for MSDE 2000 Release A"
- Previous message: Tibor Karaszi: "Re: Is it MSDE or SQLServer"
- In reply to: dev: "Re: updating database"
- Next in thread: dev: "Re: updating database"
- Reply: dev: "Re: updating database"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 3 May 2004 16:34:41 -0400
> Now, based on your code sample, does it mean that we will have to code
seperately for each version (in the script) we have ever released to bring
the database up to date on the client's machine.. seems like a nightmare
situation.
>
> What are your views about that...
Having major upgrades, and not upgrading 80 times?
Or having atomic scripts so you can do far less conditionals, e.g.
IF COL_LENGTH('table.col') IS NULL
ALTER TABLE table ADD col INT
ELSE
-- column already exists
> Also you mentioned that this kind of versioning system is not widely used.
I am sure many people must have our kind of software scenario.
Yes, but I doubt you will find a specific document that will walk you
through exactly what you want to do.
> what do you think is the best way to keep the database up to date on
client's machines.
I thought I went through that already?
- Next message: kman: "JDBC driver for MSDE 2000 Release A"
- Previous message: Tibor Karaszi: "Re: Is it MSDE or SQLServer"
- In reply to: dev: "Re: updating database"
- Next in thread: dev: "Re: updating database"
- Reply: dev: "Re: updating database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|