[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Database file checkin

From: Gurpreet Singh (SCM)
Subject: RE: Database file checkin
Date: Tue, 11 Mar 2003 11:16:10 +0530


well, for SQL server - the way (safe) is to be besides the normal way (.BAK
/ .DAT) of the DB itself is to export the SP's or other Data objects of a DB
as a simple sql / txt format -  The best method to then checkin to a CVS

Gurpreet S

-----Original Message-----
From: Daniel Hurtubise [mailto:address@hidden
Sent: Monday, March 10, 2003 11:38 PM
To: Sherzod Ruzmetov; 'CVS-II Discussion Mailing List'
Subject: Re: Database file checkin

Hi. The replies I received to date have been very helpful, thanks.
I have a follow up question.

What do people typically do with stored procedures?

Or rephrased, do you save the stored procedures to a file and then check it
into CVS, or do you simply do a backup as I described in my previous email?

Basically, I'm hunting for best practice, having no previous experience in
this area.

Thanks in advance for your valued wisdom.

On 3/10/03 11:21, "Sherzod Ruzmetov" <address@hidden> wrote:

>   : Has anybody checked in a database backup into CVS? I know
>   : this may sound
>   : odd, but I was thinking of taking a snapshot of my SQL
>   : Server database in a
>   : empty data state and then checking it into CVS.
> I do a similar thing, but I keep ONLY table schemas, since I never
> felt need to Version-Control the whole database. But if you
> have a reason for doing so, and if you think CVS can help you
> with it, give it a shot, and let the list know.
>   : Will there be any issues with checking that backup out of
>   : CVS and restoring
>   : a new database from it?
> No, there will not be, as long as your database backup is a text/plain
> file (similar to the output of "mysqldump" utility), which makes more
> sense.
> sherzod

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]