21/02/2024

13 thoughts on ““How-to” use the restored Business Central SaaS database on On-premise environment – Part II

  1. do you need to use client license to be able to run this on prem ? I try to restore my client backup to on-prem using partner license and I got an error when trying to connect using web client. The error is “You don’t have a paid license to run Production companies”

    1. yes, you need partner license or dual right license.
      in this case i used the partner license.

  2. Hi, What about encrypted data?
    You can’t export a certificate from the cloud (Data Encryption Management page).
    So encrypted data won’t be readable/usable, right?

    Which also means that whatever we put to into isolated storage with encryption in our app, is safe even though with the restored backup you can browse [Isolated Storage] table from SQL.

    1. yes, you are right!
      the same thing applies to On-premise if I encrypt the data and do not provide the certificate, try.

  3. Hi Guys …
    this post generated incredible traffic … I don’t understand why.

    SOME NOTES
    the example was made to be able to use a database locally (read data from BC and perform tests on standard features) as indicated on the Microsoft website (“you can use restored database also on On-premise …”)

    SQL Script insted of Powershell Script
    I know that it is also possible to do it from SQL as someone pointed out to me (I did it last year but I don’t provide the script), this blog for Business Central.

    Cloud Certificate
    If encryption has been activated, obviously we do not have the certificate installed on the Cloud, your apps are safe!

  4. Hi, Thanks for your technical article. I am trying to restore the database of SaaS to On-Pre.
    I have a problem soon. About the step “CHANGE THE SQL SERVER COLLACTION ON Demo Database BC like the SaaS DB”.
    I can’t change COLLACTION, As long as I change it, I will get the following error message.
    If I run export directly, it will remind me that the two database versions are inconsistent.
    Did I miss a key step?
    Very thanks.

    Change COLLACTION Error:
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ——————————

    The object ‘CRONUS International Ltd_$Cost Entry$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key9’ is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    The object ‘CRONUS International Ltd_$Issued Reminder Line$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key2’ is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    The object ‘CRONUS International Ltd_$Action Message Entry$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key3’ is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    The object ‘CRONUS International Ltd_$Issued Reminder Line$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key3’ is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    The object ‘CRONUS International Ltd_$Issued Reminder Line$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key4’ is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    The object ‘CRONUS International Ltd_$Requisition Line$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key8’ is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.

    Export Error:
    Export-NAVApplication : The source and destination databases have different collations. Either change the collation of destination dat
    abase manually to match the source database or, instead of using Export-NAVApplication, use the Export-NAVData cmdlet on the source da
    tabase and Import-NAVData cmdlet on the destination database (this will change the collation of the data to match the destination data
    base automatically).
    Source database (Demo Database BC (153)): Latin1_General_100_CS_AS
    Destination database (SaaSProduction): Japanese_XJIS_100_CI_AS
    At line:1 char:1
    + Export-NAVApplication -DatabaseServer Test -DatabaseInstance BCDEMO – …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (0:Int32) [Export-NAVApplication], NavCommandException
    + FullyQualifiedErrorId : Test,Microsoft.Dynamics.Nav.Management.Cmdlets.ExportNavApplication

  5. I’m using partner license but I get this message: Your trial period expires in 9 days. Ready to subscribe, or do you need more time?

    Any idea about how to solve this problem?

    Thanks in advance

  6. i imported the .bacpac file on SQL Server with option ‘Import data-tier application’, but when I try to start the instance of my Businees Central On-Premise, event viewer telling me that the System table $ndo$dbproperty is missing.

  7. Hy Snehanshu Mandal,
    have you solved Collation problem? If yes, can you give same suggestions?
    Thanks.

Comments are closed.