I am evaluating TXe, currently using v1.5 and I would like to know how the product deals with granting permissions to an object. For example in VS2010 I create a new table object, generate a deploy script and apply to my database. There appears to be manual steps involved in assigning permissions to the new table object before it can be accessed.
Roles seem to be completely missing from this product, which is a bit of an oversight as there seems to be little point in creating objects if you cannot permission them with the same application.
You are right about the permission and roles. Because of limited resources, we had to pick and choose which features to implement. Most of the development scenarios that we encountered in our research involve passing the deployment script off to a DBA who would take care of all the permission. It is possible to set your permission using the pre- and post- deployment scripts, though.
You can find the pre- and post- deployment scripts in the Scripts folder of you project. This is where many users add their GRANT statements.
I'm very interested in your development scenario. Do you deploy directly to a production server? Can you tell me more about your need to roles and privs?
I am in the process of developing a deployment process using TFS as source control and MSBUILD scripting as the delivery mechanism. This is working sucessfully for application code and I am now trying to get the Database schemas fully under source control.
The vision is that developers will develop using Visual Studio against a model imported using TEx. A build will then be created by TFS which will include a .dbschema and .deploymanifest file, which I can then compare against the target database and create a delta script of changes. The process will then execute this delta script against the database and apply the changes.
I have a working proof of concept developed for the scenario above, but obviously the delta only contains scripts for the object types that can be imported by TEx. So if I create a new table object and then need to grant access to an existing role, I need to do this manually using the PostDeploymentScript.sql file. My concern is that things could get missed if this is the approach taken, as the Roles are not exposed within the Visual Studio project.