Hey guys. I've started to try and evaluate the VSDB and I wasn't really impressed. I'm so used to having more control over how things are structed by using a simple "Database Project" (which comes with any version of VS Pro and above). When I attempted to put all the "Login" scripts into one file, VS just barked at me and said I didn't know what I was doing. Also, in some cases it's nice to add a Sub-folder to my Procs folder to categorize the Procedures (because we tend to have 200+ Procs). Were currently pushing Developers to use the Projects instead of going into the databases directly so that more can be controlled using VSS (yes, I don't like it either but it works). Then, once they've signed-off on the Scripts, us DBAs evaluate and deploy them.
As far as deploying it to multiple servers, that's always been easy. Just setup multiple Connections to the DB Project and depending on the User's rights (we use NT Groups here) they either can or can't script the objects on that Server.
I'm just trying to get some "Pros" of using this because I haven't seen one yet.