Navision 4.0 deployment to Windows Azure
-
Mittwoch, 7. März 2012 04:07
I am new using Windows AZURE,
I would like to use the hosting service of windows AZURE for Microsoft Navision 4.0 SP1 and Navision 4.0 SP3.
In Navision the complete codes and data get stored to the backend that is database layer and business logic layer exists to backend only. If the database is secure then both the code as well data are secured.
Navision client uses the SQL Server database to perform its Application functionality.
So we have planned to store the Navision database to Windows Azure.
As our client Navision Application is using MS SQL2000 and MS SQL2005. Please let me know below points
- If I take the backup of MS SQL Database, how can I restore it to AZURE?
- AM I needed to convert the MS SQL Data to SQL Azure, if yes please let me know the process of that?
- If it gets converted how will it be converted back to SQL server database as Navision client can only understand SQL server database not SQL Azure Database
- Can we directly store or import the SQL database to windows Azure?
- If we can store SQL Data directly than what server name we need to mention to our Navision Client, Navision client is not web based.
- Bearbeitet Sam1208 Mittwoch, 7. März 2012 05:47
Alle Antworten
-
Mittwoch, 7. März 2012 06:20
Hello.
1) If I take the backup of MS SQL Database, how can I restore it to AZURE?
No way of doing so. Refer to answer to your second question below.
2) AM I needed to convert the MS SQL Data to SQL Azure, if yes please let me know the process of that?
Yes, you need. Check this link: http://msdn.microsoft.com/en-us/library/windowsazure/ee730904.aspx Simply you need to use SQL Server Management Studio 2008 R2 and use its built-in functionality Import/Export or Generate Script (don't forget to check compatibility with Azure if you will use this method). Be aware - there are some differences between SQL Server and SQL Azure. You can use SQL Azure Migration Wizard - it can detect functionality in your local db that is not supported by SQL Azure and say you about it.
3) If it gets converted how will it be converted back to SQL server database as Navision client can only understand SQL server database not SQL Azure Database
As i say above, you can use SSMS. If you will export your db to sql azure you will have the _same_ db and it will be fully supported by Navision (because SQL Azure is, roughly, just a cloud SQL Server).
4) Can we directly store or import the SQL database to windows Azure?
SSMS or you can connect to your SQL Server and run an TSQL query for restore your db scheme/data.
5) If we can store SQL Data directly than what server name we need to mention to our Navision Client, Navision client is not web based.
In this situation please check materials about Windows Azure Connect.
- Bearbeitet Alexander BelotserkovskiyMVP Mittwoch, 7. März 2012 06:21
- Als Antwort vorgeschlagen Alexander BelotserkovskiyMVP Mittwoch, 7. März 2012 07:36
-
Mittwoch, 7. März 2012 07:31
The response is very satisfactory.Iwill try all the above.
Thanks
Thanks Anju Sardana
-
Mittwoch, 7. März 2012 07:37Please ask if you will have any questions or problems.
-
Mittwoch, 7. März 2012 07:37
Honestly I am worried about the last step , 5) If we can store SQL Data directly than what server name we need to mention to our Navision Client, Navision client is not web based.
Reason Navision only accept SQL SERVER DTABASE NAME.
Thanks Anju Sardana
-
Mittwoch, 7. März 2012 10:10Moderator
Hi,
Perhaps your can use SQL Azure database, the no web based client can also access the SQL database normally.
http://www.windowsazure.com/en-us/develop/net/how-to-guides/sql-azure/
Hope it can help you.
Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework
- Als Antwort markiert Arwind - MSFTModerator Mittwoch, 14. März 2012 03:11
-
Mittwoch, 7. März 2012 10:30
Hello.
As Arwind said, yes, you can use SQL Azure as SQL Server. SQL Azure server has canonical name that you can use in your connection strings. Nothing is changed logically - you still use some server name, but instead of SQL Server you use cloud server.
- Als Antwort markiert Arwind - MSFTModerator Mittwoch, 14. März 2012 03:11

