Upgrading to new database tiers in Azure SQL

I have a lot of databases many of which are in older database tiers web/business.
How do I determine which specific new database tier they need to be upgraded to?

Hi askulkarni,
Please see the following: http://azure.microsoft.com/en-us/documentation/articles/sql-database-upgrade-new-service-tiers/

Similar Messages

SCCM 2012 R2 SQL Database Upgrade Fails : Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.

Hi Friends,
We have planned to upgrade our SCCM 2012 SP1 infrastructure to SCCM 2012 R2 so we have setup test environment to test SQL database upgrade before doing same in production.
But while testing SQL database upgrade on test machine, it is getting failed with below error.
ConfigMgrSetupWizard.log
ConfigMgrSetupWizard Verbose: 1 : Scripted setup failure handling callback called. Failure: 29.
ConfigMgrSetupWizard Verbose: 1 : Received error [Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.] from native code.
ConfigMgrSetup.log
ERROR: SQL Server error: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'ContentDistribution_PK'. Cannot insert duplicate key in object 'dbo.ContentDistribution'. The duplicate key value is (921). :
tr_ContentDistributionNotification_insert
ERROR: Failed to execute SQL Server command: ~-- ~-- Rebuild ContentDistribution tables ~-- ~IF (EXISTS(SELECT TOP 1 1 FROM dbo.SMSData WHERE SMSBuildNumber <= 7900) AND dbo.fnIsSecondary() != 1) ~BEGIN ~ exec spRebuildContentDistribution
@TruncateTables=0 ~END
Failed to create process of SetupWpf.exe.
Can anyone please help to get this resolved.
Thanks.

We found out that there were duplicate entries in the PkgStatus_G and the PkgServers_G tables in the SCCM DB. We identified them, deleted them , and then we were able to run the /TESTDBUPGRADE command and it went through fine. We performed
all of this on a COPY of the PROD DB and then moved the changes in PROD. Hope this helps someone.
- Dave

Problem to create "New Database Diagram" in Microsoft SQL Server Management Studio for SQL Server 2012 SQL Express

Hi,
I have installed SQL Server 2012 Express edition (name of installation media: en_sql_server_2012_express_edition_with_advanced_services_x64.exe) from MSDN and I have installed the application on my pc with Windows 7 Exterprise.
Everything is working fine except when I am trying to create "New Database Diagram", where I recieve following error message:
TITLE: Microsoft SQL Server Management Studio
Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft.VisualStudio.OLE.Interop)
BUTTONS:
OK
I have tried two times to reinstall SQL Server 2012 Express and I have installed Cumulative Update #3 for SQL Server 2012 and restarted the machine, but I have still the same problem with the same error message.
Installed the following fixes:
1) 2012_RTM_DAC_CU3_2723749_11_0_2332_x64
2) SQLServer2012_RTM_CU3_2723749_11_0_2332_x64
These files was installed successful.
How can I solve the problem?
BR
Jan Nilsson

Hi Jan,
Have you installed Visual Studio in your machine?
The problem seems to be related to installing and uninstalling the VS 2011 RC0 program.
The workaround involves copying the files from another PC with SQL 2008 or 2012 from one machine to another. Just replace this folder:
C:\Program Files (x86)\Common Files\microsoft shared\MSDesigners8
See also the following for further details:
http://social.msdn.microsoft.com/Forums/en-GB/vstsdb/thread/d65c71f5-3887-4f2a-bbd3-e799a4ac6fdc
Best Regards,
Iric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

How do I upload my SQL to Azure SQL?

How do I upload my MS-SQL data into Azure SQL?

Hi,
Migrating a database requires careful planning in order to ensure the application continues to run well. Consider the following:
1.If your database contains objects that are not supported by Azure SQL Database, application changes may be required.
2.Dependencies on features that are not supported in Azure SQL Database, such as SQL Server replication, will need to be removed.
3.Dependencies on Transact-SQL syntax that is not supported in Azure SQL Database, such as distributed queries, will need to be removed.
4.Understand your workload. This will be useful when selecting an appropriate service tier and performance level for your database.
Use the information in Upgrade SQL Database Web/Business Databases to New Service Tiers and Azure SQL Database Service Tiers and Performance Levels to determine the appropriate service tier and performance level for your database.
5.Application changes may be required to operate effectively when moving your database from on-premises into an external datacenter. For example, network latency can be affected, which may require modifying your application to minimize the amount of data
transmitted across the network.
Please check this
document which talks about Migrating Databases to Azure SQL Database.
After you have successfully synchronized the converted objects with SQL Server or SQL Azure, you can migrate data from MySQL to SQL Server or SQL Azure. Please refer to this
document.
Additional information :
http://azure.microsoft.com/en-us/documentation/articles/sql-database-deploy/
Regards,
Mekh.

Problem in Azure SQL Database Basic Tier

I have a WinForms Application was using Azure SQL Database (Web)
It was working fine with web version (for last 2.5 years).
After Microsfot's new offerings of New Tiers of Azure SQL Database,
I tried Basic Tier.
Observation for last 24 hours according to Azure Portal when Database in
BASIC state :::
Successful Connections : 2 (Max), 1.5(Avg), 3(Total)
Failed Connections : 0 (Max), 0 (Avg), 0 (Total)
Throttled Connections : 0 (Max), 0 (Avg), 0 (Total)
Deadlocks : 0 (Max), 0 (Avg), 0 (Total)
Storage : 23.38MB (Min), 23.75MB (Max), 23.47MB (Avg)
CPU Percentage : 0 (Min), 3.34 (Max), 1.14 (Avg)
Log Writes Percentage : 0 (Min), 0.05 (Max), 0.02 (Avg)
Physical Data Reads Percentage : 0 (Min), 0.01 (Max), 0 (Avg)
The WinForm Application working fine but there is some problem:
When a Report is generated (local .rdlc), the connection gives "Timeout Expired"
This problem occurs only in 25% cases (in 75% cases works fine)with same data.
If I upgrade database to Standard (S1) it works fine.
QUESTION IS :
Resource Stats show it is using very low resources.
like CPU percentage 3.34 (Max), Log Writes Percentage 0.05 (Max)
and Physical Data Reads Percentage 0.01 (Max)
Why the report not works in 25% cases in BASIC state but works in STANDARD S1 state ?
The price of Standard S1 is 8 timeshigher then BASIC
Thanks

Hello Fanny,
Thanks for reply.
I know it and that's why I mentioned different resource stats.
My database (BASIC) using only :
CPU Percentage : 3.34
(Max)
Log Writes Percentage :
0.05 (Max)
Physical Data Reads Percentage :
0.01 (Max)
While Microsoft says if any parameter goes beyond 80% usage then you need to upgrade tier
Please see following video on Channel 9:
Azure SQL Database and the new Database Throughput Unit
by Tobias Ternstrom – Principal Program Manager Lead for performance in Azure SQL Database
Thanks

Can't select the new Azure sql service tiers when creating a new database or upgrading an existing one

Hi all,
I have set up the preview for the new Azure SQL tiers on both of the subscriptions we have for Azure. The one under my MSDN subscription to and a pay as you go subscription
The pay as you go subscription works fine but when I try to upgrade an existing Azure sql database or create a new one on my MSDN subscription it doesn't give me the option of the new tiers.
Using the new portal it says I need to sign up to the preview, but I already have and when I go to try to add a new subscription to the preview for Azure SQL it says all my active subscriptions are on the preview.
Any idea what the issue could be?
Cheers
Ash

Hi,
Apologies for the inconvenience.
I suggest you open a Billing Support Ticket. They will be able to check this for you.
http://azure.microsoft.com/en-us/support/options/
Regards,
Mekh.

Concerns over switching between new Azure SQL Database Service Tiers

Windows Azure's new SQL Database
service tier pricing model will be put into effect in less than 12 months. We currently have SQL Databases on the Business and Web Edition pricing models.
We recently asked Azure Support a number of questions around the scalability and ability to switch between these tiers. The responses so far have been far from encouraging:
Q: If we exceed the criteria for a given tier (see http://msdn.microsoft.com/library/azure/dn741336.aspx), how will Azure respond? For example, if we are on the S1 service tier, and we exceed the maximum number of sessions (200), will any new sessions be
blocked until we manually increase the service tier? Or will you automatically move (and bill) us to/for the next tier level?
A: If you exceed the criteria of the existing tier, you shall be notified of performance issue like throttling. Users may experience slowness and blocking. There will not be any automatic upgrade.
Q: So to confirm, if we suddenly experience increased, unanticipated client activity overnight due to our web site becoming more popular, you will be blocking any user sessions over and above our performance level limit, until we manually make the transition
to the next level? Is there no “overdraft” facility/scalability in this respect? If this scenario took place within a short space of time, how would we have time to react? Simply blocking new sessions and preventing customers from using our site is not acceptable.
A: I’m sure you understand that SQL Azure database is a shared resource and hence we cap the resources for individual subscription so that a fair service is provided to all the concurrent users. If you feel that you cannot compromise on the user experience
then you shall think of an edition that best suits you. Please refer to the following document to best understand the throttling and its impact. http://social.technet.microsoft.com/wiki/contents/articles/1541.windows-azure-sql-database-connection-management.aspx#Throttling_Limits
Q: Since the changing of the performance level could take several minutes/hours depending on the size of the database, would we experience any downtime/degradation of performance of the database during this period?
A: You might
Q: If downtime/degradation of performance are a possibility whilst we switch service tiers, what do Microsoft recommend we do to safeguard against this? Should we create a second database on a higher tier level and then export the data from the lower tier and
import to the higher, before switching over? How do Microsoft recommend we switch tiers in a production environment with minimal disruption?
A: If you want to upgrade the tiers due to degradation of performance, you will have to create another database on a higher tier and import the data.
One of our key reasons for moving to Azure hosting was the seamless scalability it appeared to offered. As you can imagine, the responses above are a major concern for our production environment. Does anyone else have any thoughts or concerns in this respect?

James,
I reviewed the support incident you referred to and believe that the questions you asked may have been answered later in the interaction you had with the engineer. For the benefit of others viewing this forum I want to reiterate the answers
to your key questions here as well.
Q. What is the behavior when you reach the limits for the service tier?
A. Each service tier currently has limits on 4 different dimensions (CPU, physical reads, log writes and memory) of resource consumption. When you reach one of the limits, the behavior depends on which resource limit you are hitting, but
generally speaking is consistent with the behavior you would see with a similar hardware limit in the SQL Server box product. For example, when you reach the CPU limit your queries will start showing more SOS_SCHEDULER_YIELD waits,
the memory limit will cause a higher percentage of pages to be read from disk instead of the buffer cache (PAGEIOLATCH_xx waits), etc. This set of limits does not directly abort any of your queries--they just run longer as they
vie for the fixed set of resources made available to your database. In a system where the load greatly exceeds the resources, queries may start to time out.
The new service tiers continue with the Web/Business edition behavior of limiting the number of sessions and concurrent requests (worker threads) you can have. When you exceed these limits you'll get error 10928. Note that
each tier in Basic/Standard/Premium have different values for these limits (http://msdn.microsoft.com/en-us/library/azure/dn369873.aspx) than Web/Business and thus may encounter the errors at different usage levels. The key is choosing the appropriate
service level for the application, and to facilitate that the sys.resource_stats view shows historical usage information so you know where you stand as far as reaching any of the limits. This resource consumption data is also available in the portal.
Q. Is it possible to switch service tiers, and is there any disruption when you do so?
A. Yes, you can change between service tiers as described in this MSDN documentation (http://msdn.microsoft.com/en-us/library/azure/dn369872.aspx). This can be done through the portal, powershell, or REST APIs. [The preview currently has a restriction
where legacy servers don't support switching to Basic/Standard which is expected to be removed in the near future.] The link above outlines the limits on the number of tier changes you can do in a 24 hour period, expected time to perform the change, and
the client disconnect that occurs.
If you have further questions, feel free to re-engage on the support incident or reply to this forum thread.

Contained Database Users are now available in Azure SQL Database Update preview

Contained Database Users should be of particular help for people migrating to Azure SQL Database. At the moment, this is a preview release but you can start testing. Here is the announcement of the
preview with links to more information.
New SQL Database public preview with new Standard-tier performance level
Previously announced in November 2014 and now available for customers to try, the
new
public preview of SQL Database improves the compatibility of SQL Server applications for Azure SQL Database. Details of this preview are available on the
SQL
Database documentation webpage, including the following key enhancements: easier management of large databases to support heavier workloads with parallel queries
and online indexing, support for programmability functions like CLR and XML index to support more robust application design, improved monitoring and troubleshooting with XEvents and 100 new Dynamic Management Views (DMV), and more performance in the Premium
tier.
To try this preview, please sign up via the Preview
features webpage. Only SQL Database servers with a mix of one or more Basic, Standard, or Premium (not Web or Business) databases are compatible and eligible to
upgrade to the preview. Please note that any move of an existing Basic, Standard, or Premium database into this preview is irreversible; we recommend that you create a database copy or leverage test databases on any server enrolled in this preview.
A new Standard-tier performance level, S3, is also available in this preview which gives you more pricing flexibility between Standard and Premium. S3 will deliver 100 Database Throughput Units (DTU) and all the features available in the Standard tier. Please
note that S3 will appear on your bill as a multiple of S2 until further notice.
For more information, please visit the SQL
Database webpage and the
Microsoft
Azure Blog. For a comprehensive look at pricing, please visit the
SQL
Database pricing webpage.
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Hello Rick
That is great, one thing I'd like to ask, does it support SSMS,SSDT?
No sign of that yet, that I’ve seen.....
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Azure SQL Database

Folks,
Not sure if this is the right forum to ask these questions, I am planning to sign up for Azure SQL Database and VMs. I am trying answers to following. Any information is appreciated.
What is the reliability measure of the Azure SQL Database. Is it five 9’s ?
What is the "MAX Worker Threads” performance measure as mentioned here:
http://msdn.microsoft.com/en-us/library/azure/dn741336.aspx
Does “MAX session” correspond to maximum number simultaneous of DB JDBC connections.
Is it tenant based service where multiple tenants are hosted on the Azure database.
What is the architecture of Azure SQL database, Is it centralized on a single server or over a cluster of machines ?
What is the high level architecture of the VMs and SQL DB.
What is the nature, bandwidth and reliability of connectivity between Azure VMs and Azure SQL DB.
Is this network capacity between VMs and SQL DB shared between multiple tenants.
How are the SLAs guaranteed (ensured) and throttled/enforced (to curb over-utilization).
If we horizontly scale Azure VMs to twice number of current VMs, will the temporal locality of the new VMs has lower network performance in terms of latency or bandwidth than the existing VMs.
Are there any per Azure VM limits on access to Azure SQL DB.
If for some reason SQL DB crashes experiences, Is the Data recoverable.
Can the Azure SQL DB be backed up in Azure Cloud/ or Amazon S3
Thanks,
Ajay

Hi Ajay,
These msdn forums are the actually the best place to ask questions.
I guess you have some scenario in back of your mind that makes you ask these questions, if you can share that with us we may better answer your questions instead of giving you information that may not be most usable for you, regardless here it goes.
I will do my best to answer all your questions
What is the reliability measure of the Azure SQL Database. Is it five 9’s ?
VS: It's 4 nines (99.99) The 99.99% uptime SLA applies to Basic, Standard, and Premium service tiers only.
SQL Database Web and Business Editions have an established uptime SLA of 99.9%.
http://azure.microsoft.com/en-us/services/sql-database/
What is the "MAX Worker Threads” performance measure as mentioned here:
http://msdn.microsoft.com/en-us/library/azure/dn741336.aspx
VS: SQL Database governs the limit on the number of concurrent worker threads (requests) to a database.
Any database with more than the allowed limit of concurrent requests will receive error 10928, and further requests on this database can be denied.
http://msdn.microsoft.com/en-us/library/azure/dn338078.aspx
Does “MAX session” correspond to maximum number simultaneous of DB JDBC connections.
VS: Yes, SQL Database governs the limit on the number of concurrent sessions that can be established to a database. When concurrent session limit for a database is reached, new connections to the database are denied and user will receive error
code 10928. However, the existing sessions to the database are not terminated.
http://msdn.microsoft.com/en-us/library/azure/dn338078.aspx
Is it tenant based service where multiple tenants are hosted on the Azure database.
VS: Yes and No, Yes because its offered as SAAS, yes multiple tenants are hosted on Azure DB, but they are isolated and also depends on the tier you choose. SQL Azure is designed for Massive scaling, so if you were worried about slowness due
to multi tenant hosting, trust me that should last thing to be worried about.
No, because you can choose to go all the way to premium (now that does not mean you are the only db on the server but its super high performing database out there)
What is the architecture of Azure SQL database, Is it centralized on a single server or over a cluster of machines ?
VS: Its hosted in Microsoft Datacenters and offered as a service, although we can go in detail of architecture of SQL Azure but for this set of questions its irrelevant. Performance is massive on SQL Azure, it can be scaled out or scaled down
on demand.
What is the high level architecture of the VMs and SQL DB.
VS: Not following your question here, what is meant by architecture of VM?
What is the nature, bandwidth and reliability of connectivity between Azure VMs and Azure SQL DB.
VS: The connectivity in general is great unless you decide to host one service in part of the world and other totally other corner, in that case also I have seen good connectivity between the two given normal latency.
Is this network capacity between VMs and SQL DB shared between multiple tenants.
VS: Not following your question in entirty, do you mean network capacity in terms of GB/Sec? if your vm and sql are in same Data Center its the fastest connectivity you can get out there in market on any cloud or for that matter on prem :)
they apparantely have a faster network in their DC than many giant companies have on prem.
How are the SLAs guaranteed (ensured) and throttled/enforced (to curb over-utilization).
VS: MS have protection against many threats, DOS being one of them, Microsoft has done the best job among all the cloud providers out there to inform thier customers about outages, in a recent summit this was also discussed in detail and suggestions
were made to improve on the portal feature.
Each time an service goes down its reported on the portal on service health page, they are improving on the SLA breach report, at this moment its part of your invoice. I have personally not seen a single breach on my services, I am actively using Azure for
last 5+ years.
If we horizontly scale Azure VMs to twice number of current VMs, will the temporal locality of the new VMs has lower network performance in terms of latency or bandwidth than the existing VMs.
VS: number of VMs have nothing to do with network performance, keep in mind the fabric underneath is build for massive scale, network performance and latency will vary (they keep improving) if you choose to create your VMs in a different DCs
then you would come across some latency and that's normal.
Are there any per Azure VM limits on access to Azure SQL DB.
VS: these are not per VM limits, they are driven by MAx_THREAD and MAX_SESSION, please refer to the link above in the question for Max worker thread
If for some reason SQL DB crashes experiences, Is the Data recoverable.
VS: I would be careful to answer this, if you choose to use SQL Azure (which is offered as SAAS) then yes MS takes care of data replication to ensure SLA. if you choose to host your own SQL DB on your VM in Azure, MS is not responsible for
the data recovery, you will have to take care of it (because now you are not talking about PAAS, instead you are going for IAAS)
Can the Azure SQL DB be backed up in Azure Cloud/ or Amazon S3
VS: Ofcourse, I am not very familiar with Amazon S3 but i see no reason why it can't be done.
hope this helps
Please mark as answered if it helped
Vishal Narayan Saxena http://twitter.com/vishalishere http://www.ogleogle.com/vishal/

Database Initialiser does not create azure sql database

I have a WPF application In the OnStartup in the app.cs I set the Database initializer and forced the context the initialise my database:
Debug.WriteLine("Setting Initializer");
Database.SetInitializer<MyContext>(new MyDatabaseInitializer());
Debug.WriteLine("Declaring new context");
using (MyContext c = new MyContext("MyContext"))
Debug.WriteLine("Force the initialization");
c.Database.Initialize(true);
Debug.WriteLine("Done!");
I created a sql database in the management portal of the azure.
Copied the connectionstring it provided for ADO.net.
But my database is not created.
I also added a firewall rule but nothing happens. I Have no clue what to do.
Can anybody please help me with this?
If you need more information please ask i really have to get this sorted out.
Thanks in advance!

Hi Turkstra,
I have tried to use EF to create Azure SQL database, it works as expect, the database 'jambordbcreate' appear in my SQL Azure, below is the detailed codes.
using System;
using System.Collections.Generic;
using System.Data.Entity;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
namespace CodeFirst
class Program
static void Main(string[] args)
Database.SetInitializer(
new CreateDatabaseIfNotExists<SchContext>());
using (var db = new SchContext("Server=tcp:****.database.windows.net,1433;Database=jambordbcreate;User ID=vote@***;Password=***;Trusted_Connection=False;Encrypt=True;Connection Timeout=30"))
string name = "jambor";
var student=new Student(){Name=name, ID="1a"};
db.Students.Add(student);
db.SaveChanges();
db.Database.Initialize(true);
public class Student
public string ID { get; set; }
public string Name { get; set; }
public string age { get; set; }
public string sex { get; set; }
public class School
public string ID { get; set; }
public string Name { get; set; }
public virtual List<Student> Students { get; set; }
public class SchContext : DbContext
public SchContext(string connection):base(connection)
public DbSet<Student> Students { get; set; }
public DbSet<School> Schools { get; set; }
I suggest you check your SQL connection, after run your code, please refresh azure portal to see whether your database is exist. Hope this give you some help.
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Which is better for performance Azure SQL Database or SQL Server in Azure VM?

Hi,
We are building an ASP.NET app that will be running on Microsoft Cloud which I think is the new name for Windows Azure. We're expecting this app to have many simultaneous users and want to make sure that we provide excellent performance to end users.
Here are our main concerns/desires:
Performance is paramount. Fast response times are very very important
We want to have as little to do with platform maintenance as possible e.g. managing OS or SQL Server updates, etc.
We are trying to use "out-of-the-box" standard features.
With that said, which option would give us the best possible database performance: a SQL Server instance running in a VM on Azure or SQL Server Database as a fully managed service?
Thanks, Sam

hello,
SQL Database using shared resources on the Microsft data centre. Microsoft balance the resource usage of SQL Database so that no one application continuously dominates any resource.You can try the
Premium Preview
for Windows Azure SQL Database which offers better performance by guaranteeing a fixed amount of dedicated resources for a database.
If you using SQL Server instance running in a VM, you control the operating system and database configuration. And the
performance of the database depends on many factors such as the size of a virtual machine, and the configuration of the data disks.
Reference:
Choosing between SQL Server in Windows Azure VM & Windows Azure SQL Database
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Cannot Connect to Azure SQL Database in Visual Studio 2013

Beyond Frustrated here.
I am trying to connect to an Azure SQL database - it has been created, has tables etc. I am trying to create a new Data Connection from within Visual Studio 2013, latest release for VS and Azure. I continue to receive the following error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
I have ensured that TCP is allowed and above Named Pipes in the Configuration Manager. The associated IP address is allowed on Azure Firewall. Certificate has been added to VS etc. But still no connection. I can see the database in the Azure section in Server
Explorer, but cannot add a Data Connection. What is equally as frustrating is I have a MacBook Pro running Win 7 sitting right next to my office computer and it can access Azure fine, not problems.
If anyone has any other ideas on how I might be able to solve this I would love to hear them. Thanks in advance.
Jeff

Hi,
The Error message "   A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is
configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53) "
The issue comes up mainly because the application is not able to connect to the server.
To resolve this issue, try the following steps (in that order):
Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).
2. Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port (1433) and the fully qualified server name.
Note You can follow these steps to obtain the connection string from the Azure Management Portal:
                      Log on to the
Azure Management Portal.
                      In the left navigation pane, click
SQL Databases.
                      Select your Azure SQL Database server.
                      Click
Dashboard.
                      On the right side, go to the
quick glance section, and then click Show connection strings.
Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this, see
Azure SQL Database connectivity troubleshooting guide and
Troubleshooting SQL Server connectivity issues.
Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.
Try increasing the connection timeout. Microsoft recommends using a connection timeout of at least 30 seconds.
As a best practice ensure retry logic is in place. For more information about the retry logic, see
Azure SQL Database best practices to prevent request denials or connection termination.
      If these steps do not resolve your problem, follow the below steps to collect more data and contact support:
   If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing ID.
Microsoft Customer Support Services can use this information.
   For more information about how to enable the logging, see
how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
Azure SQL Database Development Considerations.
  Check out
the list of best practices for Connecting to Windows Azure SQL Database.
Regards,
Shirisha Paderu.

Connecting to an Azure SQL Database from a Windows C# Form

Hi,
Is it possible to connect to an SQL database in Azure from Visual Studio C# 2010 or 2012? If so how is this done. Is it the same as if you were connecting to SQL Express database with the use of a connection string? Any directions or tutorials would be of
great help!
Thanks!

Hi,
>>Thanks for the reply Paul, That is disappointing. I am trying to get my students to create a C# application that will connect with a database in Azure. Is there another approach besides SQL that I could use?
Using SQL Azure will work fine (see below), if the students are familiar with SQL Server and SQL Databases it will be great for them to see how it works in the cloud. As an alternative you could explore Azure Storage, using Table Storage, Blob Storage or
the new Document Database features.
>>Azure enforces a firewall that prevents direct external access to the database server. You can add a firewall rule allowing external access, but the rules only support connecting from a fixed IP address because you have to specify the numeric IP
from which connection will be allowed.
You can specify ranges here, so you could cover a range of IP addresses. You can even specify 0.0.0.0 to 255.255.255.255 and allow all IP addresses, this could be an option if you don't know where the students will be connecting from, and you are using a
database for the exercise where you don't care too much about the security.
When I have run classes I typically use an IP address range, for example XXX.YYY.ZZZ.0 to XXX.YYY.ZZZ.255 if the students are accessing from the same classroom, and the external IP address may vary. You may find that they all have the same external IP address
if they are on the same internal network.
Also, with many students accessing the same database, you may get throttling if they place a lot of load on it. This is cool, as you can also teach them about transient fault handling and resource throttling :-).
Regards,
Alan
Free e-book: Windows Azure Service Bus Developer Guide.

Connecting to Azure SQL database in Access 2010

I've recently purchased a new computer and I had an OBDC connection set up to link to a sql database in azure through access. I am trying to set it up on my new computer but I'm unable to define the specific database. I'm able to make the connection but
it only allows me into the master database. I've added my IP address in the configure servers but still can't get things to work. Any help would be greatly appreciated.
thanks
Lynn

Hi,
The following guidelines apply to SQL Database connections using ODBC:
• When using SQL Server Native Client from SQL Server 2008 R2 or SQL Server 2008, the connection string must include the server name as part of the user name (user@server).
• You must use TCP/IP as the protocol when connecting to an Azure SQL Database.
• You cannot create a table in the master database, so therefore you must create a user database to create a table.
• You cannot execute a use database command to switch to your user database. You must disconnect and connect directly to the user database.
• You must have a primary key or clustered index on your table to be able to insert data.
Ref:
https://msdn.microsoft.com/en-us/library/azure/hh974312.aspx?f=255&MSPPError=-2147217396
http://blogs.office.com/2010/06/07/access-2010-and-sql-azure/
https://support.microsoft.com/en-us/kb/2028911/
Hope this helps you.
Girish Prajwal

Failing to create new SQL farm with FSconfig.exe for ADFS federation Services on an Azure SQL

I'm building ADFS in Azure. My plan is to use the Azure SQL. The problem is that FSconfig seams not to work with Azure SQL. Here's what i did untill now:
- I followed the documentation and created a new login and user (adfslogin, adfsuser) in a new
"adfsv21" database. Then i added the user to db_owner role.
- From c:\windows\adfs i run FSconfig: FSConfig.exe CreateSQLFarm /ServiceAccount mysa /ServiceAccountPassword ******** /SQLConnectionString "database=Adfsv21;server=[azureServer];User Id=mysa;Password=********" /AutoCertRolloverEnabled. I
tried it with both accounts, mysa and adfsuser with the same poor results.
The result is: "The following error occurred: The specified service account mysa is not valid. Specify
a different service account, and try again."
- I configured odbc and tested the connection. mysa can connect but adfsuser caanot. Why?
To be short, its not working. See this post with similar problems: google to "SQL server farm configuration error"...
So, is Azure SQL & ADFS not complatible? Really not?

My apologies for take a super long time to reply. Are you still having issues here? How can we help?
Thanks Guy

Upgrading to new database tiers in Azure SQL

Similar Messages

Maybe you are looking for