Through the process on my output file I get several errors like:
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_cmsPropertyData_umbracoNode". The conflict occurred in database "xxx", table "dbo.umbracoNode", column 'id'. The statement has been terminated. Msg 547, Level 16, State 1, Server xxx, Line 49 The INSERT statement conflicted with the FOREIGN KEY constraint "FK_cmsDocument_cmsContent". The conflict occurred in database "xxx", table "dbo.cmsContent", column 'nodeId'. The statement has been terminated.
Msg 547, Level 16, State 1, Server xxx, Line 20 The INSERT statement conflicted with the FOREIGN KEY constraint "FK_cmsPropertyData_cmsPropertyType". The conflict occurred in database "xxx", table "dbo.cmsPropertyType", column 'id'.
When the data is 'partially' imported accessing the backoffice, or any page of the site I got this SQL exception:
Invalid object name 'cmsPropertyTypeGroup'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'cmsPropertyTypeGroup'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
How are you creating your data.sql script? If you are using the Generate Scripts option then make sure you change the database engine type to SQL Azure and that you script both schema and data. If you have SSMS 2012, I prefer to use bacpac files for transferring databases to SQL Azure via the Export Data-Tier Application option. This blog post might help you.
Also, does the table cmsPropertyTypeGroup exist within your script or SQL Azure database? Your exception above usually occurs when the table doesn't exist. I believe the table is new for version 6.
Thanks for the input! It was valuable, but I'm still getting the SQL exception. I've re-runned the generated script for data couple of times, because when created, SQL doesn't really know the dependencies on the umbraco schema.
I don't seem to find the table cmsPropertyTypeGroup which is rather strange. I think this website was upgraded in the past from a 4.7.x version. Oh boy... this is going to be painfull :(
The generate scripts task should output your schema in a way that dependencies will be handled correctly.
It sounds to me like your database hasn't been upgraded from v4 to v6. Have you got the source of the original v4 site? If so, I'd see if it works against that.
Sorry for the late reply... That was actually the problem, the v6 database was hidden behind a not very discoverable name and I was still generating scripts on the v4 database.
Thanks for the help Dan. #H5YR
I will still today edit that wiki with more information.
Umbraco 6.1.6 migration to SQL Azure
I'm migrating an SQL Database (Umbraco 6.1.6) to SQL Azure and facing several problems when importing the data. It's felling a bit like this.
Following the current wiki, with the difference that I have to execute sqlcmd to run the data script, because the file as approximately 500MB.
Through the process on my output file I get several errors like:
When the data is 'partially' imported accessing the backoffice, or any page of the site I got this SQL exception:
Also tried to use the Red Gate Data Compare tool, they don't output me errors, but my end result is the same.
Any ideas to make this process less painfull and actually working A ok?
How are you creating your data.sql script? If you are using the Generate Scripts option then make sure you change the database engine type to SQL Azure and that you script both schema and data. If you have SSMS 2012, I prefer to use bacpac files for transferring databases to SQL Azure via the Export Data-Tier Application option. This blog post might help you.
Also, does the table cmsPropertyTypeGroup exist within your script or SQL Azure database? Your exception above usually occurs when the table doesn't exist. I believe the table is new for version 6.
Hey Dan,
Thanks for the input! It was valuable, but I'm still getting the SQL exception. I've re-runned the generated script for data couple of times, because when created, SQL doesn't really know the dependencies on the umbraco schema.
I don't seem to find the table cmsPropertyTypeGroup which is rather strange. I think this website was upgraded in the past from a 4.7.x version. Oh boy... this is going to be painfull :(
The generate scripts task should output your schema in a way that dependencies will be handled correctly.
It sounds to me like your database hasn't been upgraded from v4 to v6. Have you got the source of the original v4 site? If so, I'd see if it works against that.
Sorry for the late reply... That was actually the problem, the v6 database was hidden behind a not very discoverable name and I was still generating scripts on the v4 database.
Thanks for the help Dan. #H5YR
I will still today edit that wiki with more information.
is working on a reply...