Comments
Sort by recent activity
Can someone help me? / comments
Can someone help me?
Hi Andrew, Thank you! It is working, now I know what these options are and how to use it helps me a lot. / comments
Hi Andrew,Thank you! It is working, now I know what these options are and how to use it helps me a lot.
Hi Sam,
I do not want to exclude my schema entirely, I want the schema to be there, just not with this authorization change. Is there a way to filter this in sql source control?
Tim / comments
Hi Sam,
I do not want to exclude my schema entirely, I want the schema to be there, just not with this authorization change. Is there a way to filter this in sql source control?
Tim
Meeh.. I actually need to do another query to validate that the insert statement is valid. Because Permission and Action are also static data, I need to check if the "newly" added row inside the Action and Permission table is being added. This also means I need to run the deploy twice for my production env, which is not really recommended..
Is there any other way to do this? Instead of this "hack"? [image]
I would love to see this "fix" on the roadmap! I got like 3 manual steps now in my deployment process because of this. It really slows down our automation process.
Cheers / comments
Meeh.. I actually need to do another query to validate that the insert statement is valid. Because Permission and Action are also static data, I need to check if the "newly" added row inside the Ac...
Deploying in 2 seperate deployments works.. Sadly when I'm going to production the 2 changes are combined into 1 "big" deploy, which creates an error again..
I have the following tables as static data:
dbo.Permission
dbo.Action
My migration script is as followed:
INSERT INTO dbo.RoleAction
( FK_RoleId ,
FK_ActionId ,
FK_PermissionId ,
Enabled
)
VALUES ( 1000 , -- FK_RoleId - int
2028 , -- FK_ActionId - int
3340 , -- FK_PermissionId - int
1 -- Enabled - bit
)
This fails in production because the static data is not yet deployed and the migration script already runs..
Anyway to solve this? / comments
Deploying in 2 seperate deployments works.. Sadly when I'm going to production the 2 changes are combined into 1 "big" deploy, which creates an error again..
I have the following tables as static d...