Forum Discussion
Post ProdigyAnyone else unable to deploy a data warehouse with relationships?
Greetings, community. Is anyone else having problems deploying data warehouses that have a relationship via a deployment pipeline? I am able to deploy a data warehouse with no relationships created just fine, but as soon as I use the model view to relate tables and then attempt to deploy, the deployment fails with the message "Deployment couldn't be completed" and an Import failure: DmsImportDatabaseException error.
This issue was resolved by a Microsoft update.
28 Replies
I am also getting similar error while deploying warehouse thru Deployment pipeline. Did we get any updates from Microsoft or any solution to solve this problem?
Hi, I have tried so hard to deploy warehouse in the last weeks and I found multiples issues.
Here is a summary of my finding:
1- There use to be a problem with large table (Create table script greater than 4000 char.) : this is now resolved.
2-If a table column containt the word CONSTRAINT the deployment fail
Ex:
CREATE TABLE [dbo].[TEST_TABLE]
(
[COST_CONSTRAINT] [varchar](8000) NULL -- Renamed to COST_CONsSTRAINT WORK!
)
3-If a schema have a [-] in it's name deployment fail:
CREATE SCHEMA [service-order] -- Renamed to [service_order] WORK!
GO
CREATE TABLE [service-order].[TEST_TABLE]
(
[BLAH_bLAH] [varchar](8000) NULL
)
4-If I modify security on later stage warehouse after deployment the warehouse cannot be deployed anymore.
Ex: We block Dev and Test to normal user.. so in production i run:
-- Production Security-- create rolesCREATE ROLE [Application-user];-- AddPermissionGRANT SELECT on SCHEMA::[dbo] TO [Application-user]-- Add UsersALTER ROLE [Amilia-user] ADD MEMBER [****@***.**];
*** This make the Warehouse fail deployment... if I remove the role and user in prod... the warehouse can now be redeployed:ALTER ROLE [Application-user] DROP MEMBER [****@***.**];DROP ROLE [Application-user]***** Point 4 could also be caused by the [-] like point number 3 !
There is probably a lot more issues ... I have no log output.. only the same message everywhere!! Import failure: DmsImportDatabaseException
Hi all we are a similar issue but as SimonMusa mentioned it's not the exact issue you guys are getting. Hope this helps someone too.
Having spoken to microsoft - it's a known bug possibly raised by you fine chaps.
They have given me a reason as to this, it's when you are using datawarehouse from deployment workspace to another and the character length of the creation of the tables is greater than 8000 characters long. This causes the issue. Or if the column count is greater than 8000.
There is a workaround for this.In your dwh narrow the tables that you are using so that the create statement is less than 8000 characters long or that you do not have more than 8000 columns.
This is our error:
You can get this error if you go to your DWH and click the download SQL database project - that should surface the proper error if you can't see the error in your deployment screens.
Good luck to everyone I am also awaiting an ETA for this but this has for now unblocked us as we are able to narrow the tables from our dataverse source.I think that might be a different issue. I set up a test environment with two tables with two columns each and the failure only happens when there is a relationship between the two tables in the model. They have acknowledged the problem and it should be fixed in the May update.
OK thanks for the update. I will close this comment off as it may be different but the result is the same unable to migrate to the other workspaces.
Thanks
It would be nice if the project used a supported version of .NET
Did we get any update from Microsoft or any solution for this problem? I'm still facing this error. I do have tables with relations
On my side I have successfully deployed Warehouse using deployement Pipeline, but only really simple one.
I can create an empty simple table..add content to it, and it and it work for deploy.
But if I crate a empty table with the create table script greater than 4000 char, the pipeline comparison fails and cannot be deployed.
You might have the save issues? is your table definition big?
arpostThanks for the reply, grisensko. I've had the same issues happen with both a "production" (or, at least, needs to go to Production) data warehouse and a brand new data warehouse with tiny tables (e.g., 1-3 columns).
So as an example, I have a brand new data warehouse with two tables in two schemas:
I can deploy that data warehouse successfully. However, when I create a relationship in the DW like so:
And then I try to deploy, I get this error:
v-cboorla-msftMicrosoft Employee
Hi arpost
Apologies for the delay in response from my end.
Please reach out to our support team to gain deeper insights and explore potential solutions. It's highly recommended that you reach out to our support team. Their expertise will be invaluable in suggesting the most appropriate approach.
Please go ahead and raise a support ticket to reach our support team:
https://support.fabric.microsoft.com/support
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thank you.
- arpost
v-cboorla-msft, thanks for the reply. I reported it to Microsoft back in March, and it has been over a month of back-and-forth now. They've been unable to determine the cause of the issue and have had trouble identifying it. I was able to help them narrow the issue down to having to do with relationships, but as of right now, there is still no fix in sight.
I am hoping others in the community will chime in on this thread and report this to MS Support also as I haven't seen this bug mentioned in any of the Known Issues documentation I've found, but it is a pretty significant issue, so I'm hoping it will get on there soon.
- arpost
This issue was resolved by a Microsoft update.
FZOUHelper IV
hello, i still have this error when deploying my DWH from DEV to TEST using deployment pipeline, how did you resolve it please ?
It has not been resolved and the only way I have found around it is to use a view instead of a model. If you have VS 2022 you can create a DB project that can be promoted and many times that process highlights the underlying problem Fabric is having. It is sad that Microsoft has released somthing that works so poorly.
- uselessai_in
Helper II
Collected all the potential solutions from this community and others and written a blog on how you can fix this issue : https://uselessai.in/microsoft-fabric-warehouse-deployment-issue-s-and-potential-solution-s-9ad360411f7a
Check if it helps! If not, let me know!
Hi,
I am receiving the same error while moving the warehouse from development to production workspace using deployment pipeline.
Backend Error: Import failure: DmsImportDatabaseException
I have deployed all other items like pipelines, notebooks,lakehouses from dev to prod. but facing issue while deploying the warehouse. In my warehouse, I have many tables, stored procedures, views etc. How to identify where exactly in warehouse it is causing the issue.
Can anyone help/suggest on this issue.
- uselessai_in
Hi, thanks for the question. Find all deployment related issues with their creative solutions here. I tested and implemented all of them. Hope it helps.
