 |
|
|
|
Next: What was happening at time x in my db?
|
| Author |
Message |
External
Since: Mar 07, 2008
Posts: 13
|
(Msg. 1) Posted: Sun Jan 18, 2009 6:32 pm
Post subject: source control
Archived from groups: microsoft>public>sqlserver>programming (more info?)
|
|
|
I have been working on a vb.net front end, SQL Server app for some time now
and soon will be needing one or two additional programmers for the SQL part
of it. My question has to do with source control. On the vb.net side there
are many choices for a source control system, eg SourceSafe, etc but how does
one set up something similar in SQL Server. The problem is that SQL Server
source is not a separate entity from the executable code. How does one go
about setting up a system whereby developers can "checking in" and "checking
out" the "source" code, stored procedures, user functions, triggers, etc so
that one person doesn't step on someone else's edits?
--
JB |
|
| Back to top |
|
 | |
External
Since: May 30, 2004
Posts: 2060
|
(Msg. 2) Posted: Mon Jan 19, 2009 12:04 am
Post subject: Re: source control [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
JB (JB@discussions.microsoft.com) writes:
> I have been working on a vb.net front end, SQL Server app for some time
> now and soon will be needing one or two additional programmers for the
> SQL part of it. My question has to do with source control. On the
> vb.net side there are many choices for a source control system, eg
> SourceSafe, etc but how does one set up something similar in SQL Server.
> The problem is that SQL Server source is not a separate entity from the
> executable code.
It isn't what?
> How does one go about setting up a system whereby
> developers can "checking in" and "checking out" the "source" code,
> stored procedures, user functions, triggers, etc so that one person
> doesn't step on someone else's edits?
How do you prevent that developers do not overwrite each other's object
files and executables?
There really isn't much difference between SQL Server and VB .Net. The major
differences is that the binaries produced from VB .Net are difficult to
read, while the binaries in case of SQL Server are very similar to the
source. But what you have in the database is to be regarded as binaries,
and use of scripting functions in Mgmt Studion are akin to disassembling.
Once you have this mindset right, source control for SQL Server files is
just simple as any other version control.
--
Erland Sommarskog, SQL Server MVP, esquel.TakeThisOut@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx |
|
| Back to top |
|
| |
External
Since: Oct 29, 2008
Posts: 5
|
(Msg. 3) Posted: Mon Jan 19, 2009 2:26 am
Post subject: Re: source control [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
JB wrote in message
> I have been working on a vb.net front end, SQL Server app for some
> time now and soon will be needing one or two additional programmers
> for the SQL part of it. My question has to do with source control.
> On the vb.net side there are many choices for a source control
> system, eg SourceSafe, etc but how does one set up something similar
> in SQL Server. The problem is that SQL Server source is not a
> separate entity from the executable code. How does one go about
> setting up a system whereby developers can "checking in" and
> "checking out" the "source" code, stored procedures, user functions,
> triggers, etc so that one person doesn't step on someone else's
> edits?
Do everything via scripts, and then use SourceSafe (or whatever) to store
the scripts.
--
Regards
Michael Cole >> Stay informed about: source control |
|
| Back to top |
|
| |
External
Since: Jan 10, 2008
Posts: 640
|
(Msg. 4) Posted: Mon Jan 19, 2009 7:11 am
Post subject: Re: source control [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
On Jan 18, 8:32 pm, JB wrote:
> I have been working on a vb.net front end, SQL Server app for some time now
> and soon will be needing one or two additional programmers for the SQL part
> of it. My question has to do with source control. On the vb.net side there
> are many choices for a source control system, eg SourceSafe, etc but how does
> one set up something similar in SQL Server. The problem is that SQL Server
> source is not a separate entity from the executable code. How does one go
> about setting up a system whereby developers can "checking in" and "checking
> out" the "source" code, stored procedures, user functions, triggers, etc so
> that one person doesn't step on someone else's edits?
> --
> JB
In my projects all SQL and all relevant unit tests are in the same
source control system, including a single SQL script that builds a
database and all its projects from scratch. Client side solutions have
this SQL script as a dependency. Client side unit test fixtures build
a database from scratch, populate it with test data, and run the
tests. I'm using Subversion, I like it most. >> Stay informed about: source control |
|
| Back to top |
|
| |
External
Since: Mar 07, 2008
Posts: 13
|
(Msg. 5) Posted: Mon Jan 19, 2009 8:34 am
Post subject: Re: source control [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Thanks for the replies.
--
JB
"Alex Kuznetsov" wrote:
> On Jan 18, 8:32 pm, JB wrote:
> > I have been working on a vb.net front end, SQL Server app for some time now
> > and soon will be needing one or two additional programmers for the SQL part
> > of it. My question has to do with source control. On the vb.net side there
> > are many choices for a source control system, eg SourceSafe, etc but how does
> > one set up something similar in SQL Server. The problem is that SQL Server
> > source is not a separate entity from the executable code. How does one go
> > about setting up a system whereby developers can "checking in" and "checking
> > out" the "source" code, stored procedures, user functions, triggers, etc so
> > that one person doesn't step on someone else's edits?
> > --
> > JB
>
> In my projects all SQL and all relevant unit tests are in the same
> source control system, including a single SQL script that builds a
> database and all its projects from scratch. Client side solutions have
> this SQL script as a dependency. Client side unit test fixtures build
> a database from scratch, populate it with test data, and run the
> tests. I'm using Subversion, I like it most.
> >> Stay informed about: source control |
|
| Back to top |
|
| |
| Related Topics: | Red Gate Survey: Database Development (versioning/source c.. - Red Gate Software is doing some preliminary research around the area of database development processes, especially in relation to source control and versioning. If you are a SQL Server database developer, we would much appreciate your participation in ou...
How to: Use Data Source Object and Data Source View Object? - Hi, I can't possibly find any information of actually how to use a data source object or a data source view object in a package. After I've added a SQL Server data source object and a data source view object to my project I can't use any of them in..
Source Safe - Hi, We desperately need to have some Source Control for version maintaining and to enable quick replication of chenges done to development server to say staging server or QA server... or a production server Any tools, that can plug in to sql server,....
Export DB source help - Hello, i am looking to make a full scripted backup of my sql server 2000 database using various free tools, i can easily export the table structures and stored procs into my script, but i have not found anything to help with: - indexes - users/logins -..
How to find source of Error - Hi, I get this exception reported when tracing, Error: 547, Severity: 16, State: 0. How can I find what caused the error? Thanks, Lasse |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
