| Author |
Topic |
|
rav3n0u5
Yak Posting Veteran
88 Posts |
 Posted - 2006-04-25 : 15:36:42
|
| I am looking for some insight into setting up a good development environment that I can use to track changes, and obviously use for development. Any thoughts or ideas? I currently save changes to a SQL file and label it with the date and change number for that date. This seems inefficient to me. It is difficult to know which scripts were applied to the production db, and often the changes have to be made very quickly to the production environment. I am the sole database programmer, but I want a system that could scale up to include many programmers.Anything?Thanks! |
|
|
rav3n0u5
Yak Posting Veteran
88 Posts |
Posted - 2006-04-25 : 18:15:17
|
| I read Graz's article found here: http://www.sqlteam.com/item.asp?ItemID=17320It is fairly close to what I am looking for, although it does defer to a third party utility for version control. I have access to Visual Source Safe, but in my limited experience with it, I have found it to be clunky. Another article in the SQLTeam repository addresses using VSS keywords (lost the URL). This coupled with Graz's method seems interesting. I think I am still looking though... |
 |
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
|
|
rav3n0u5
Yak Posting Veteran
88 Posts |
Posted - 2006-04-25 : 18:40:59
|
| Cool - thanks for the link.I actually do use that generate scripts feature and I have a way of versioning those scripts (date, by sequence of creation, by object seems to be a good naming convention). But the problem with that method is I believe it involves too much human intervention. I have forgotten to generate scripts before and then wondered why I couldn't get a later sproc working because a table didn't exist. Of course that example has an easy fix. Others however, are more complicated.It seems that there are two approaches; a snapshot approach, and a more constant flow approach (a la replication types?). I guess I am looking for a good snapshot approach, or flow approach that will catch events rather than having someone log them. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-04-25 : 20:59:44
|
| if you're a developer you may want to create an interface like QA or EM, I did one before but only caters to sprocs, udfs and views (because those were the only objects I allow developers to create or modify directly)i use windows authentication plus and approle with sa privilegethere's a lot of parsing and validations aside from the fact that every change is logged onto another database within the serverIt took me a couple of man-hours to complete the utility but it was worth itHTH--------------------keeping it simple... |
|
|
|
rav3n0u5
Yak Posting Veteran
88 Posts |
Posted - 2006-04-26 : 04:51:50
|
| Unfortunately I am not proficient enough in anything to make an interface like that. I ended up installing VSS directly on the sql server and intend to use the plug-in feature. Anyone have experience with it? Is it decent? |
|
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
|
|
rav3n0u5
Yak Posting Veteran
88 Posts |
Posted - 2006-04-26 : 14:17:20
|
| That's what I'm talking about! Thanks! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-04-26 : 14:49:38
|
quote:
I ended up installing VSS directly on the sql server and intend to use the plug-in feature.
That is not a good idea. VSS should be installed on the client machines and not directly on the database server.Tara Kizeraka tduggan |
|
|
|
rav3n0u5
Yak Posting Veteran
88 Posts |
Posted - 2006-04-26 : 16:30:37
|
| Correction: I installed the vss client software. The server software is on another machine on another network. I don't know if this is any better. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-04-26 : 16:33:14
|
| No it's not. It isn't needed on the database server. It is only needed on the client machines.Tara Kizeraka tduggan |
|
|
|
|
Version control/setting up development server??