Hi

Hope this is the correct newsgroup for this questions.

I'm developing a small database solution, where the db is a sql database,
and the application is a vb.net frontend to the database. Currently I use
SQL server Express as dbms.
What is the best way to store this in sourcesafe? Should I put the entire
application and the db in sourcesafe, and then check it all out on the
development workstation I'm currently using (I have to rotate between
several machines)?
I've had problems attaching the database to the development machines at
times after I've done a checkout, so I'm not quite sure how to do this.
I'm sorry if this is an issues that belongs to a sql server newsgoup or
sourcesafe. But please help, or at least point me in the right direction :-)

Regards

A.

"Andy.I" <(E-Mail Removed)> wrote in
news:FFD4EA08-1158-4C8E-AC95-(E-Mail Removed):

> What is the best way to store this in sourcesafe? Should I put the
> entire application and the db in sourcesafe, and then check it all out
> on the development workstation I'm currently using (I have to rotate
> between several machines)?

Database souce control is troublesome because I don't think MS provides any
out of the box tools.

I would have a development database on a central server which all users
would connect to. When changes are made to the DB, generate a SQL script
and place it into source control.

Perhaps others have better ideas :-)

> Database souce control is troublesome because I don't think MS provides any
> out of the box tools.

Actually, they do now. It's not cheap but...

check out Visual Studio Team Edition for Database Professionals (I
think this is the right name). It allows you to approach database
design with the same tools you would use for software design and
development. Among the tools are reverse engineering existing db's,
support for multiple targets (I can deploy to a test db, a design db,
production db, etc), and some nice visual tools as well. MS really
did a fantastic job on this product. It's new, so I'm sure it has
some gotchas, but what I saw was very impressive. Hope this helps.

I would reccomend moving away from the MS camp.
they don't have the foresight to keep VB successful; so I would move
to Linux and PHP; maybe source forge has some strong source control
applications




On Feb 19, 9:38 am, "BK" <bkunn...@hotmail.com> wrote:
> > Database souce control is troublesome because I don't think MS provides any
> > out of the box tools.
>
> Actually, they do now. It's not cheap but...
>
> check out Visual Studio Team Edition for Database Professionals (I
> think this is the right name). It allows you to approach database
> design with the same tools you would use for software design and
> development. Among the tools are reverse engineering existing db's,
> support for multiple targets (I can deploy to a test db, a design db,
> production db, etc), and some nice visual tools as well. MS really
> did a fantastic job on this product. It's new, so I'm sure it has
> some gotchas, but what I saw was very impressive. Hope this helps.