Is it possible to create a model driven app and have the CRUD operation directly connecting to Azure SQL Server?
Related
I am doing a POC to integrate camunda with oracle database. It works well with h2 database. To integrate with oracle, I have followed this user guide (https://docs.camunda.org/manual/7.17/user-guide/spring-boot-integration/configuration/). My application programmatically creates a datasource and transaction manager so i have no control over it. I tried to create a secondary transaction manager using above user guide and it fails due to two transaction manager bean found.
Is there a way to connect with the programmatically created datasource instead of providing a configuration.
I am trying to build a mobile application that needs data from an Azure SQL DB. Best practice looks like building a web service in between.
However I am getting lost in the number of solutions.
Which specific Azure component do I need to use to have a future-proof solid solution?
How to handle security between this component and the Azure SQL DB?
How to handle security between the mobile application and the Azure Component?
The best way forward is to use an ASP.NET Web API with ADO Entity Frameworks and publish the API to an Azure website. Use REST services to call the Web Api from your mobile app.
So basically:
1) Fire up VS and build a Web Api that will handle your database using ADO Entity Framework and the controller for your API. Check this: http://www.tutorialsteacher.com/webapi/web-api-tutorials
2) Publish the Web Api to an Azure website/app through VS. Make sure you have Azure services installed on your VS.
3) Call the Web Api from your mobile app using REST services to work with the SQL database. You will need an HttpClient class to do this, you can get it from NuGet.
For security of your Web API, check this: https://www.asp.net/web-api/overview/security
We are developing a dashboard application. In the home screen it has four charts and list view. The data for these charts and list view are stored in different tables in the backend database. We are planning to create web services for fetching the data from server.
My question is, do we need to write separate web services (in this case 5 web services) for fetching the data or can we create a single web services that returns all the data in a single call?
If we write different services, then we need to invoke five services from the mobile device (iPad/Android Tablet). If we write single service, the response time will be delayed due to the joining table in the server side.
We are creating our application using Sencha touch framework. Our app is a cross platform mobile application. The web services are writing using restful wcf services and it returns JSON.
Please give ur your suggestions
I have an Azure Mobile Service running connected to a database with 3 tables, on the management portal of the database I can create Views based on them...the question is...how can I access the view through the Mobile Service? is this possible with Azure Mobile Services? or should I be using a regular web Service?
What I'm looking for is a way to access it like I would do with a table...for the table I just go to the URL and I get a JSON, that's what I would like to achieve.
you should use regular web services. Windows Azure Mobile services is meant to be very simple in simple cases rather than an all purpose tool.
Still, you could override the read operation on a table to return other results. You may want to use http://msdn.microsoft.com/en-us/library/jj631631.aspx and http://msdn.microsoft.com/en-us/library/jj613353.aspx as starting points.
If you go to the portal and just add the name of the view that you have created it seems to work.
eg.
My Mobile Web Services service is called 'PTView'
create view PTView.vwMcPeople as
select * from Person where surname like 'Mc%'
on the Data tab of your web service create a table with the same name as the view.
Use/ Download the SDK for Azure mobile service and then you can access your data using API provided.
Azure mobile service is not accessible directly from URL.
Which is the best way to synchronize a SQL Server database with its remote client databases? Web services/any other built-in features available in SQL Server?
Application details:- Wpf desktop with SQL Server 2005.
The scenario is client’s main office having stock management database. Same database structure implemented in client’s remote outlets. New stocks are adding in main office database. Whenever a new row is added to head-office database, need to inform all remote client SQL Server databases. And whenever a change happens in remote client outlet, need to send back the changes to main office database.
Thanks in advance.
After a lot of research I ended up with followings
1. Sql Server Replication
2. SymmetricDS
3. Microsoft Sync Framework
4. Customized WCF service.(An Example)
I chose customized WCF service for synchronizing DBs. The steps adopted are mentioned here.
1. Created an Index Table. This table holds the transaction history and signature of client.
2. Created a service layer (class library) which receives and returns table rows as stateless DTO objects. This service layer referencing a Data Access Layer which is responsible for communicating with database.
This service layer & Data Access Layer are referenced by WCF service and windows service.
3. Created one WCF service and hosted it in IIS of web server, This service offers:
a). Download(DTOClass dto)
b). Upload(DTOClass dto) service contracts.
4. Created one Windows service and deployed it in multiple client locations. This service consumes the WCF service hosted in Webserver IIS.
Windows services from client location communicate with WCF service at specific intervals, if a new update available in main server database(this information available in IndexTables), windows service downloads the update (using Download(DTOClass dto) contract) and update local database.
Likewise, if any changes happen in local database, windows service handover the changes to WCF service(using Upload(DTOClass dto) contract). WCF service then update master database.
Since both services accessing Database servers locally, this result in better performance.