re: Deployment of client-specific database code using SSDT
Nice write-up on connect. It's exactly the situation we are in and you described it well. By the way, the connect item is picking up some steam.
View Articlere: Deployment of client-specific database code using SSDT
As promised:[SSIS] We're crying out for composite projectshttps://connect.microsoft.com/SQLServer/feedback/details/781080/ssis-were-crying-out-for-composite-projects
View Articlere: Deployment of client-specific database code using SSDT
Bruce,No, unfortunately not :(I have brought this up privately to the SSIS team, I think maybe I need to make the request more public. To Connect I go!Jamie
View Articlere: Deployment of client-specific database code using SSDT
Nice feature indeed! Does SSDT also support client-specific changes for SSIS packages or SSAS cubes? That would be icing on the cake!
View Articlere: Deployment of client-specific database code using SSDT
Hi Leo,Exactly the same applies in regard to indexes. They're still database objects, exactly the as views are, so you can still have an index per client. SSDT doesn't stipulate that you have to put an...
View Articlere: Deployment of client-specific database code using SSDT
Great explanation, nice to see that it have been implemented in an intuitive way (which was something I couldn't say a lot for the first versions of the "Data Dude"). :-)One additional question, how...
View Articlere: Deployment of client-specific database code using SSDT
Kris,Of course, you can also have "layers" of composite projects where you have an interim layer of projects that consume from _core, provide different implementations of certain objects, and are then...
View Articlere: Deployment of client-specific database code using SSDT
Hi Kris,In that example I would say that the new table can no longer be in "_core" and you would need to define the table in each separate project.Unfortunately there is no notion of override i.e. If...
View Articlere: Deployment of client-specific database code using SSDT
Hi Jamie,What would you suggest if the new project has a different structure for the same object, like additional columns to the core table object.Thanks.
View Articlere: Deployment of client-specific database code using SSDT
Hi Talal,Unfortunately I don't think you can achieve what you're trying to achieve here. There is no way to have one project override what is in another. An object is either shared across all projects...
View Articlere: Deployment of client-specific database code using SSDT
Hello, JamieI am facing a situation where I have one database project that holds objects that are general to all customers. Then I have another project that references it and holds the objects that are...
View Articlere: Deployment of client-specific database code using SSDT
I understand but it will include every object from ClientBar project as well. And if I uncheck 'Include composite Objects' option I would get dependency error...I just want script with all ClientFoo...
View Articlere: Deployment of client-specific database code using SSDT
Hi B Stanik,I think you can simply publish the ClientFoo project and choose the option to generate the script rather than generate the script and run it.This option is available when publishing either...
View Articlere: Deployment of client-specific database code using SSDT
What if I want to generate script that includes only ClientFoo objects?
View Articlere: Deployment of client-specific database code using SSDT
Is this supposed to work with schema comparisons? cause when I do that it flags everything in the core project to insert into the client-specific project.
View Articlere: Deployment of client-specific database code using SSDT
Brandon,I think this post, http://blogs.msdn.com/b/ssdt/archive/2012/06/26/composite-projects-and-schema-compare.aspx, still applies to schema comparisons even though it is 2 years old.
View Articlere: Deployment of client-specific database code using SSDT
Jamie, You have just made my day! Even though this was posted some time ago, this solution is just what I was looking for.
View Articlere: Deployment of client-specific database code using SSDT
How to deploy post deployment scripts in core to project to all clients
View Articlere: Deployment of client-specific database code using SSDT
I have the same question as Ravikumar: How can we handle post Deployment / Data deployment Scripts? By default the post Deployment script of _Core won't be executed when deploying the "clientFoo" db....
View Articlere: Deployment of client-specific database code using SSDT
Extra objects doesn't seem to be an issue, extending or overriding objects in _Core doesn't seem to have an obvious solution (other than don't do it).e.g.If the _Core Sales table had the following...
View Articlere: Deployment of client-specific database code using SSDT
By the way, I have dropped a feature request on Microsoft Connect. You can find it on...
View Articlere: Deployment of client-specific database code using SSDT
I have the same issue as Ravikumar and Markus. I would also like to combine pre and post deployment scripts of multiple dacpacs in the same database. Hope anyone has a solution for this issue.
View Articlere: Deployment of client-specific database code using SSDT
Hi Jamie,Do you know how to get rid of SQLCMD variables within SSDT, once they are added?Thanks
View Article
