Because of how rdl builds I've found adding notes when you commit helps a ton.

I use it with SSRS every day.

I would exclude the following types of files though (not check them in)

.data

.suo

.user

Since these are user specific they can cause problems if you have...

Have you tried just setting the top static? Seeing if it works...and then slowing adding frozen rows?

I haven't played a ton with dtsx files. I do know that rdl files it's a huge pain. Since files are appended from the top, merging is a...

All those files except the suo and user files

I wouldn't do the access database, but the rest I would put in SVN

We have had issues if multiple people are working on the same dtsx package, otherwise SVN handles changes really well.

We check in the entire project since this allows you to easily open the project and run it.

I'd keep using SVN. We do and it works great. Any concerns?

Very cool table. One I didn't know about. In my testing tonight, it's the original create date of the package.

You can search for previous versions through SVN, but SQL server doesn't store previous versions as far as I am aware.

It's basically file based, so you check in the solution that your working with and then commit changes to the dtsx files as they occur. It's worked well for...

We're using TortoiseSVN and it works like a charm. Searching for previous versions is great and the software is free.

Matt H.