I need to be able to filter on the Commit Changes tab, eg filter by Changed By to only show my changes, change type etc

Having ability to filter out changes to users and user permissions (and preferably select object types as in sql compare) from inclusion in source control will make SQL source control a far more usable tool for me

I'd love to be able to skip users, permissions, and built in roles.

We have a LOT of dynamically generated objects (8k+) with a very few user written ones, as such a filter is essential to us as at present the tool cannot cope in a reasonable amount of time and waiting a couple of hours to check something in is not going to work. As we use Schemas to detemine dynamically vs manually generated code filtering by schema would work for us.

We have some dynamic generated tables that there is no point having in source controle.

Filtering objects and schema-options in the style of SQL Compare would be ideal in order to ignore collations, defaults, statistics, etc. would be a great addition. In fact, it would be rather mandatory, since use of SQL Compare and DataCompare more or less made me expect it'ld be in.

Manual sorting and selecting should not be considered a work around, as the process of committing is a common one, and should not be dependent on manual selection each time by each developer for items that should never be in. The risk is too big for items to be added which would break deployments.

FYI - You can sort on the column headings in the Commit/Get Latest tabs. This will not filter the list, but will group objects by type or schema. You can use your mouse + ctrl or shift keys to highlight multiple objects in the Commit or Get List. Then click on the checkbox for one of the objects to select/unselect all the highlighted objects.

You can also right click on the stored procedures directory and click commit/get if you know you only want to commit/get changes to stored procedures. This will only select the stored procedures in the commit/get list and not select any of your other objects.

Hi is it possible to get the same filtering system as in sql compare

Same for me, We do not store any users in svn because of multiple location roll-out

Stephanie - I've actually voted for both. The difference is important, and I think it's important to have to option to either just filter from a client perspective and also be able to use svn:ignore.

Filtering objects on the commit list is different from "ignoring" objects. I think "ignoring" objects mean that these objects would never appear in your commit list. If this is the feature you are looking for, there is a seperate topic for this at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/458708-exclude-objects-from-versioning-svn-ignore-.

This would also be useful for filtering out things like logins and roles, which we do NOT maintain in version control.

It would be even more useful if our selections were persistent, or if we could choose what types of objects we wanted to maintain in version control. For instance, we would only want version control support for tables, procs, views, and functions. We do not version control roles, schemas, users, etc.. Having to uncheck the things we don't want on every commit becomes very tedious.

I cannot emphasize enough how important this is. I do development on subset of the entire db (I need = reference some of those other tables but their development isn't my responsibility)