April 23, 2010 at 8:55 am
Any suggestions on a good CVS solution for VS/BIDS.
My primary concern is the source control of packages.
_____________________________________________________________________________MCITP: Business Intelligence Developer (2005)
April 27, 2010 at 3:22 am
At my current project we use TortoiseSVN. It gets the job done, but there are some quirks/irritations.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 27, 2010 at 3:35 am
what sort of quirks/irritations?
at the moment it will be predominately me doing all changes, but I still want to set up a proper change control, for any ETL packages.
Thanks
_____________________________________________________________________________MCITP: Business Intelligence Developer (2005)
April 27, 2010 at 3:59 am
I won't speak generally, but these are some things I ran into at my current project:
* you must know the URL to go to the repository. Sure, you can keep them all in an Excel file or something like that, but then you just add something else that needs maintenance.
* it happens that the SVN directory at your local machine gets corrupt. (for example, when you and someone else changed some code, and you forget to update your local SVN directory first. It happens). When you try to commit, TortoiseSVN gives errors, but not really a way to fix it. It happened on several occasions that I had to delete my entire local SVN directory and re-create it, just to get rid of the errors and so that I could commit again.
* when you change some filenames and move them to other directories, it can happen that TortoiseSVN is still looking for the old file. Even when I deleted the old file on the SVN repository, it still gave issues. It took me a while to get rid of that.
* a colleague of mine couldn't commit changes to a project for some reason, while I could. Maybe something wrong in the set-up, possibly...
I have to say that most of the time, TortoiseSVN works just fine, but sometimes ... 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 27, 2010 at 7:19 am
Funny, while definitely *not* my favourite source control system, CVS hasn't given us any of the issues you outlined, ever. I find it a bit of a pain (when compared to TFS) but otherwise very stable. Can't remember what our version of the server is but I use Tortoise CVS as the front end, with Windows integration (ie right click context menus in win explorer etc). The later (maybe 6 months old) releases had none of the issues of needing to remember 'anything' - you got a graphical nav tree of your source file structure, so finding projects you hadn't worked on previously but now needed is very easy (ie navigate the folder structure til you see it then bring it down).
In general, the SSIS files shouldn't cause you any issues, after all, they're just XML/text docs. If the concurrency of changes really does cause you problems in CVS, try checking out the file/s with locks, so only you can change them until you re-commit.
Steve.
April 27, 2010 at 7:29 am
I did some more research on the Tortoise SVN we are using, and it's possible that we just can't browse the repo-browser graphically because of security restrictions.
So the limitations I posted here can be somewhat biased :-).
The issues with commit however, I ran into them multiple times and so did my colleagues. (it's also possible that we just suck :-))
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 27, 2010 at 10:50 am
Doubt that y'all suck, it's just worrying that when a products primary purpose in life is to allow multiple users to edit documents, and then either auto-merge or allow for manual merge of conflicting changes - and it fails at this - the product would seem to have some serious issues :S
Steve.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply