Best practice on local database Schema update

[RS]

Hello All,

Does anyone know what the best practice is for updating database
schema? We are designing a smart client application where the .Net
application is used online and offline. If the computer is connected
the application communicates directly with the main database and if it
is disconnected it communicates with the local database. When the
machine is connected again, data gets syncronized. Now, if we want to
update/modify the database schema in the local data base of each
machine, should that be done during the database syncronization or can
we use the Updater Application Block or clickonce to do that job? Most
likely we will be using SQL Server Express as our local database and
SQL server 2000 or 2005 as the main database.

Cheers,

Tom

 

[Ken Tucker [MVP]]

Hi,

http://msdn.microsoft.com/library/d...ry/en-us/dndotnet/html/northwindunplugged.asp

Ken

 

[RS]

Thanks Ken

That website talks about database syncronization but it did not mention
anything about updating the database schema. Any info about that?

Thanks

 

[Cor Ligthert [MVP]]

RS,

What in my opinion is not clear in your message is what you mean with
udating the database Schema.

Your text talks about updating the databases on local and central side.

It is very strange to update the database Schema, because that would mean
that every user has another Schema and data will be lost.

Just my thought,

Cor

 

[Hari]

Tom,

I am not sure whether this will be best practice or note, but updating
database schema can be done by implementing replication, and
configuring client databases (Express 2005) as subscribers to central
database (SQL Server 2000/2005). Please go thru the SQL Server Books
online for details on replication.

-
Hari Sharma