How to update the production database?

[fedor]

We are installing an application with MSSQL database at our users place.

Now we have two instances of the same database:
- developing database, on which we are working at
- production database, which is at our user's place.

That 2 databases would have to be syncronised.

Users will of course enter some data into production database. How can we
change the production database do reflect changes we have made on the
developing database?

D.

--

[MC]

Theres a couple of ways to do it.
One would be to compare two databases and script differences. You could use
third party tools for this (RedGate for example)
Other would be to script changes during development and save script using
some version control tools.

I've got the feeling you didnt script changes during development so you'll
have to compare databeses and synch them. For next time, I would recommend
scripting....
MC
"fedor" <fe**********@hotmail.com> wrote in message
news:cm*********@sunce.iskon.hr...

We are installing an application with MSSQL database at our users place.

Now we have two instances of the same database:
- developing database, on which we are working at
- production database, which is at our user's place.

That 2 databases would have to be syncronised.

Users will of course enter some data into production database. How can we
change the production database do reflect changes we have made on the
developing database?

D.

--

[fedor]

The installation at user was today.
So you were on time.

Thanks.
D.
--

"MC" <marko_culo#@#yahoo#.#com#> wrote in message
news:cm**********@brown.net4u.hr...

Theres a couple of ways to do it.
One would be to compare two databases and script differences. You could
use third party tools for this (RedGate for example)
Other would be to script changes during development and save script using
some version control tools.

I've got the feeling you didnt script changes during development so you'll
have to compare databeses and synch them. For next time, I would recommend
scripting....
MC
"fedor" <fe**********@hotmail.com> wrote in message
news:cm*********@sunce.iskon.hr...

We are installing an application with MSSQL database at our users place.

Now we have two instances of the same database:
- developing database, on which we are working at
- production database, which is at our user's place.

That 2 databases would have to be syncronised.

Users will of course enter some data into production database. How can we
change the production database do reflect changes we have made on the
developing database?

D.

--

[David Rawheiser]

Yet another reason for using a Source Control System.
"MC" <marko_culo#@#yahoo#.#com#> wrote in message
news:cm**********@brown.net4u.hr...

Theres a couple of ways to do it.
One would be to compare two databases and script differences. You could
use third party tools for this (RedGate for example)
Other would be to script changes during development and save script using
some version control tools.

I've got the feeling you didnt script changes during development so you'll
have to compare databeses and synch them. For next time, I would recommend
scripting....
MC
"fedor" <fe**********@hotmail.com> wrote in message
news:cm*********@sunce.iskon.hr...

We are installing an application with MSSQL database at our users place.

Now we have two instances of the same database:
- developing database, on which we are working at
- production database, which is at our user's place.

That 2 databases would have to be syncronised.

Users will of course enter some data into production database. How can we
change the production database do reflect changes we have made on the
developing database?

D.

--