I realize that a local SQL Server instance is not accessible to my Windows 8 app. Instead, I have a SQL Server in Azure. In SQL Server Management Studio, I just change the querystring and interact with the Azure database like any other. How can I reference that database in my Windows 8 app?
This is what the Azure Mobile Services SDK is for. Scott Guthrie did a writeup on it a while back.
Undoubtedly you're aware that both ado.net and Entity Framework are missing from WinRT... Notice the glaring absence of support for System.Data.
You can't access directly on sql databases.. Because Windows 8 Apps different from windows forms.
But you can be used web services or azure, amazon services, storage files etc.
sounds like you want to develop a web service talking to your database, deploy it to IIS on your Azure instance and then consume it from your Windows 8 application (by adding a web reference to your web service in Visual Studio).
You can also place an OData head on the database, then use various OData client-side libraries to talk to it via REST. See http://www.odata.org/libraries for both client and server libraries. SQL Server on Azure is definitely supported, as is .NET, JavaScript, and other platforms on the client side.
Related
I need to host a web application in IIS in Azure, if I take a virtual machine with Windows 2012 standard, how do I install SQL Server? Or is there any other option?
Getting most out of the Azure platform, I would suggest to use Azure Web Apps and Azure SQL Databases for that.
Using VMs only make sense, if you need control over the underlying systems (e.g. OS settings, Advanced SQL Server features like SSRS).
If you are going to use AZURE make sure you read a little about what you can and cannot do on AZURE. For example there is no SQL Server Agent or global temp tables. I like the requirement that all tables require a clustered index. You may not.
Here are two articles that list some of the differences but these are an incomplete list:
https://blogs.msdn.microsoft.com/azureedu/2016/07/15/what-features-are-not-supported-in-azure-sql-database/
http://www.sqlservercentral.com/articles/Azure+SQL+database/143076/
To install SQL Server on Azure follow this:
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision
I am planning to use azure mobile services for one of our products. I was confused about how can I use any of my existing databases (like MySQL, PostgreSQL, or Oracle instead of SQL database offered by Azure) which is available via TCP?
Kindly confirm.
Are you using the JavaScript/Node backend or the .NET backend?
If you're using JS, you'll need to create API scripts and import the Node module for your database. You can't use the default data scripts since they are only hooked to SQL Azure.
If you're using a .NET backend, there's no restriction whatsoever. You can use any database available on Azure or install your own in a VM.
I just started developing in Azure and I bump in to a lot of questions that might help others as well.
My goal is to learn more about:
azure
html5
jquery
ASP.NET MVC4
entityframework
My first steps:
subscribing to Azure. (5 minutes)
create a website, and added a database to my azure account. (5 minutes)
create a TFS environment (5 minutes)
download the publish settings file that can be used in visual studio to publish directly into azure (1 minute)
installed visual studio 2012 (2 hours) (required)
installed azure SDK for .NET (30 minutes) (required)
installed resharper (30 minutes) (optional)
installed SQL server 2012 (still downloading, 1 hour and counting) (needed?)
I started in parallel and began with this great tutorial for getting hands-on experience with website, html5, azure.
Since I deviated from the tutorial by adding my entity classes in a different project I ran into errors running enable-migrations. Here you can read the answer to that problem.
Now the "toughest" part for me until now: tha world of databases.
I am no expert on database development so I was wondering how deep do I need to dive. The goal remains the same: I want to build a webapp where I store and retrieve data from a database. So far the azure experience is quite easy going and everything integrates pretty easily.
I kinda liked the idea that I only need visual studio to work from, and that I can get addins that help me develop the things that I need.
Does that end when you get to database development?
Is SQL server 2012 the way to go?
Or are there "more easy" alternatives?
Is it a lot of work to update the database in the cloud with the stuff that I changed locally?
I do want to store stuff in the database in azure in the end.
Can you folks shed some light on the possibilities there are out there with its cons and pros?
When you work with windows azure environment in emulated environment (local development) You can use desk top version of SQL server 2012.But at the end you have to store your data schema on Azure SQL Database when you publish your cloud Application for production.
What is Windows Azure SQL Database ?
Microsoft Windows Azure SQL Database is a cloud-based relational
database service that is built on SQL Server technologies and runs in
Microsoft data centers on hardware that is owned, hosted, and
maintained by Microsoft.
Similarities and Differences
Similar to an instance of SQL Server on your premises, Windows Azure SQL Database exposes a tabular data stream (TDS) interface for Transact-SQL-based database access.
This allows your database applications to use Windows Azure SQL Database in the same way that they use SQL Server.
Because Windows Azure SQL Database is a service, administration in Windows Azure SQL Database is slightly different.
Unlike administration for an on-premise instance of SQL Server, Windows Azure SQL Database abstracts the logical administration from the physical administration; you continue to administer databases, logins, users, and roles, but Microsoft administers the physical hardware such as hard drives, servers, and storage.
This approach helps Windows Azure SQL Database provide a large-scale multi-tenant database service that offers enterprise-class availability, scalability, security, and self-healing.
Because Microsoft handles all of the physical administration, there are some differences between Windows Azure SQL Database and an on-premise instance of SQL Server in terms of administration, provisioning, Transact-SQL support, programming model, and features.
Features and Types
Windows Azure SQL Database does not support all of the features and data types found in SQL Server.
Analysis Services, Replication, and Service Broker are not currently provided as services on the Windows Azure platform.
Because Windows Azure SQL Database performs the physical administration, any statements and options that attempt to directly manipulate physical resources will be blocked, such as Resource Governor, file group references, and some physical server DDL statements.
It is also not possible to set server options and SQL trace flags or use the SQL Server Profiler or the Database Tuning Advisor utilities.
Windows Azure SQL Database supports many SQL Server 2008 data types; it does not support data types that have been deprecated from SQL Server 2008.
For more details you can follow below mentioned links.
Windows Azure SQL Database Overview
Tools and Utilities Support (Windows Azure SQL Database)
Guidelines and Limitations (Windows Azure SQL Database)
Deploying an ASP.NET Web Application to a Windows Azure Cloud Service and SQL Database
I hope this will help to you.
I have a WP7 app idea that requires a connection to a server database (running SQL Server 2008 R2). I checked online and accordingly it is usually done by using WCF that expose the database for the phone to be used.
I would like to know if the new mango update provide anything new to the process I already mentioned. I am aware of the local database, but in my case I need the SQL Server database for the bigger size.
Thanks,
(Even in mango) there is no way to directly connect to a SQL Server database.
The easiest way is to use oData to expose your database on the wire. The oData client library is built into the Mango APIs under System.Data.Services.Client.
However, be aware of the requirements of your application and architect approrpriately. There may be a need to provide some sort of caching plan as network connectivity is never guaranteed on a mobile device.
I have a Silverlight app which needs to talk to a local SQL database, we plan on deploying this Silverlight app to Azure. Users will navigate to the app and install the app using the Out-of browser feature.
How should we plan on installing the SQL database on the local user’s machine in such cases? This app runs in offline mode for the most part except when synchronizing with the remote server, so a local SQL database is required.
You won't be able to use anything like SQL Express or similar on the machine from an OOB application (unless you are running elevated) as you will still be constrained by the sandbox and the libraries available to you in Silverlight are limited.
Instead consider using a compact database that can be stored in Isolated Storage, something like Siaqodb, vistadb, or silverdb.
One other thing to look at is the forthcoming Sync framework for Silverlight, which is designed to offer offline support for data from SQL or SQL Azure. See this webcast: Building Offline Web Apps using Microsoft Sync Framework.
If you are running elevated, then you can use COM to interact with the local system, so you would be able to access a full-fledged database that way. However, making sure the prerequisites were in place and dealing with managing the database would be a lot of work. I wouldn't recommend it for your scenario.