>To the best of my knowledge, there's nothing within the SEM to integrate with VSS. Maybe the Visual Database Tools that ship with Visual Studio have that feature.
>
>Would you let me know when you figure it out. I'm curious.

I did figure it out, but it isn't pretty! :) The integration is done using Visual Interdev. Why? I have no good answer.

The trick is to add a database connection to a project in VI 6.0. Right click on the db connection and choose Add to Source Control.
You'll have to create a new project in VSS. This will create one entry in VSS project for each stored procedure. Which seems
good enough... but only at the first sight. :(

VSS: You cannot check-out, check-in, get the latest version, etc using VSS.
Or, better said, you can do it, but it will not act on the SQL database, but on .sql files created on disk. WHich is next
to useless.

SEM: There's absolutely no source control awareness. So, even if a stored procedure is checked out in VSS,
anybody can modify it directly in SEM.

VI: Here's better. You can add to VSS, check-out, check-in at procedure level. So, if everybody's using VI (and VI only)
to modify stored procedures, everything seems ok. The bad thing is that there's no GetTheLatestVersion or
ViewDifferences option. The only way to see differences is to try to check-out a procedure. If there are differences,
VI will pop-up a dialog asking which version you want to use (the one in VSS or the one in the database).
This dialog also gives the chance to check the difference. And this is what really bugged me. Since the functionality
is already there... why they didn't put it as a separate option?

Anyway, it seems that the scenario would be like this:
Use VI to modify stored procedures.
Use VSS to generate .sql files for each and every procedure. Write a small program to update the database using the
generated .sql files.

So, it's more than nothing, but less than acceptable. At least IMHO.

Hum... I think I'll write an article about it. Or write a small program to manage this. :)

Vlad