azure-sql-database

Windows 8 64 bit DAta sync agente ver. 4.0.89.0 Error message , I tried reinstall 3 times data sync and 4 tiems new agent and new key also. No prosy or internet fire wall one no other fire wall software also. Please enter a valid agent key to proceed. The key must be generated from SQL DAta Sync web portal agent key 16f25226-2a20-49c3-acfc-062057c42b41:gWpFO0NHm4Xq9bw7fLzo8YS49iSowEDQToYpbMCKqFk= id:LocalAgentUX_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Warning, version:4.0.0.0, methodName:AgentModel_AgentStatusChanged, message:Agent UI stopped polling for the latest

I get the following error when trying to select a database with php's standard mssql_select_db function: USE statement is not supported to switch between databases. Use a new connection to connect to a different Database. (severity 16) . So i'm stumped as in where to go from here. Connection Code: $link = mssql_connect('dsn', 'user@server', 'password'); if (!$link) { die('Unable to connect!'); } if (!mssql_select_db('db', $link)) { die('Unable to select database!'); } $result = mssql_query('SELECT * FROM yourtable'); while ($row = mssql_fetch_array($result)) { var_dump($row); } My system setup

My needs are following: - Need to fetch data from a 3rd party API into SQL azure. The API's will be queried everyday for incremental data and may require pagination as by default any API response will give only Top N records. The API also needs an auth token to work, which is the first call before we start downloading data from endpoints. Due to last two reasons, I've opted for Function App which will be triggered daily rather than data factory which can query web APIs. Is there a better way to do this? Also I am thinking of pushing all JSON into Blob store and then parsing data from the JSON

Ive come up against a major problem. I am building a system which emloys a ASP.NET 4 Web App > Azure SQL > Azure Mobile Service > Windows Phone 8 app. The data is inputed into the Web Site which is already hosted on azure and which employs the Membership Provider and hence its default tables. This data is stored already successfully on Azure SQL db. My major obstacle is Azure Mobile Services requires each and every table on it to have their primary key to be called "id" - lower case! Crazy in my opinion. And of course the Membership Provider has different names for PK's. Question - Should I

I want to start using SQL Azure and SQL Azure Data Sync (for both on-premises SQL 2008 and Azure). The Azure Portal still labels data sync 'Preview' - so is it even production ready? If not when will it be? Anything labeled as "In-Preview" is considered not supported for production use, though you may opt to do so; just realize that it is currently not recommended. As for timing, I suggest keeping tabs on the SQL team's blog: http://blogs.technet.com/b/dataplatforminsider/ 来源： https://stackoverflow.com/questions/18994419/is-sql-azure-data-sync-production-ready

I'm using Azure Functions with queue triggers for part of our workload. The specific function queries the database and this creates problems with scaling since the large concurrent number of function instances pinging the db results in maximum allowed number of Azrue DB connections being hit constantly. This article https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections lists HttpClient as one of those resources that should be made static. Should database access also be made static with static SqlConnection to resolve this issue, or would that cause some other problems by

I am currently creating an Environment Deployment Package using ARM and I want to be able copy an existing Azure SQL Database (schema and data) to another Azure SQL Database in a new Resource Group. I created a .bacpac file from the original SQL Database and uploaded it into a Storage Account. I then added a SQL Database Import Resource to my Template and pointed it at the URI of the .bacpac file I created. When I try to run the Deployment, I get this error. A project which specifies Microsoft Azure SQL Database v12 as the target platform cannot be published to Microsoft Azure SQL Database {