Differences Between SQL Azure Database and SQL Server in Azure VM

SQLServerF1

Microsoft is making huge investments in cloud technology and is betting big for future growth in this area. Microsoft has started providing cloud services for various products, applications, Operating System or hardware support. Based on the type of service, Microsoft has made available different offerings which include Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). Microsoft cloud support many applications or products out of which SQL Server is one of the Microsoft product which is supported on cloud by Microsoft. There are two different kind of offerings provided by Microsoft for SQL Server, which are Infrastructure as a Service (IaaS), Platform as a Service (PaaS).

Among these two services Infrastructure as a Service (IaaS), Platform as a Service (PaaS) offered by Microsoft, we a DBA or management, we need to understand what best suits our requirement and based on that we can choose the offering. It is important to understand the differences between these two offerings available for SQL Server, so that we can make an informed decision. Each offering for SQL Server from Microsoft has its own advantages and disadvantages interms if features, cost, High Availability, Disaster recovery, which operations tasks are taken care by Microsoft, etc. Below are some of the differences between SQL Azure SQL Database (PaaS) and SQL Server in Azure VM (IaaS).

SQL Azure database as service is best suited for new applications designed or optimized for cloud solutions or which depend on other cloud technologies, so that they can be used together. Developers building software-as-a-service (SaaS) applications can use Azure SQL Database to provide flexibility to support both explosive growth and profitable business models. On the other hand with Infrastructure as a Service (IaaS) is for applications which are already existing ones and cannot be changed easily and need to be migrated on to cloud without much changes to be made. Applications which are dependent on other on-premise resources are best suited for Infrastructure as a Service (IaaS) compared to SQL Azure database as service.

SQL Azure database as service does not support all features available in SQL Server and has many limitations for each feature, many of the features cannot be controlled by DBAs or developers and there is not much control for DBAs for operational tasks like patching, backups, HA or DR. Infrastructure as a Service (IaaS) is just like on-premise SQL Server instance on which DBAss or developers can make configuration changes, performs backups/restores, use required technologies for HA and DR purposes, etc. There are some limitations with SQL Azure database as service like max database size supported as of 2015 is only 500 GB, but this limitation does not apply for Infrastructure as a Service (IaaS). Another limitation include, SQL Azure database as service does not allow resources to be accessed from Azure to on-premise. Infrastructure as a Service (IaaS) does not have any such limitations.

In Infrastructure as a Service (IaaS), hardware, its maintenance costs are eliminated as it is taken care by Microsoft. SQL Azure database as service also eliminates the costs mentioned before, in addition to that, in SQL Azure database as service also eliminates maintenance and administration efforts and costs of patching, backups, HA, DR, etc. in SQL Azure database as service, there are different services available to choose for High Availability and disaster recovery where Point in Time Restore, Geo-Restore, and Geo-Replication to increase can be chosen to increase business continuity. In Infrastructure as a Service (IaaS), the High availability and disaster recovery is to be taken care by DBAs and we can choose any technology of our choice and we are responsible for administering, monitoring and fixing any problems.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Different offers from Microsoft Azure for SQL Server

SQLServerF1

Cloud solutions has been gaining increased support and many customers moving their data on to cloud technologies or planning to move in future. The reason for increase in popularity of the cloud technologies include that it reduces the operational and maintenance cost of hosting the own hardware and its day to day maintenance. Many operation tasks such as backups, patching, etc can also be taken care by the cloud solutions depending on the kind of offering selected. Microsoft and other companies like Amazon are investing a lot on the cloud technologies and trying to provide features that match the on-premise servers and applications or more than that.

Microsoft is offering its cloud services in different types depending on the services offered. These include Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). These offerings are generic and is applicable for different applications which include SQL Server too. Coming specifically to SQL Server, Microsoft is offering two services SQL Server on Azure VMs (IaaS) and SQL Azure Database (PaaS).
SQL Server on Azure VMs (IaaS) – This is similar to on-premise SQL Server running on a virtual machine which is running on a host system whose hardware is maintained in Microsoft’s data center. In on-premise servers, DBAs or management discuss and decide on the hardware required like CPU, Memory and storage and the Operating System required, on top of which DBAs install SQL Server instances and create or restore databases. in SQL Server on Azure VMs (IaaS), Microsoft provides required hardware(CPU, Memory, Storage) and provides a VM with required Operating System too. DBAs can install SQL Server instance on this VM, configure and manage and administer it just like an on-premise SQL Server instance. If any support is required related to hardware, then DBAs are required to contact the Microsoft support. This is best suited for applications which does not need much changes after moving to cloud technology and where management want more control on the SQL Server.

SQL Azure Database (PaaS) – SQL Azure on the other hand is a Database as a Service offering of SQL Server. This SQL Server runs on a VM which is maintained by Microsoft and this server will be hosted on Microsoft Data Center. In this offering DBAs does not need to install, or manage things like patches, backups, upgrades, etc, as these things are taken care by Microsoft team either through automated scheduled tools to by manual maintenance depending on the type of the task. There are many things which are offloaded from DBA like high availability, disaster recovery, patch maintenance, etc. If high availability is required, we need to choose the right offering and license which provides the high availability. Here we can choose which server needs which features and based on the features used and the usage the price will be decided. DBAs or managers get access to Azure portal where we can setup new SQL Azure instances, configure them, choose required features, and find the connection strings to be used in the application or to use in SSMS to connect to this instance locally from out laptop or other devices. From SSMS or other applications, we can create databases, tables, users, etc and use the databases to store and retrieve the data. This is best suited for new applications which just need access to data and does not want to spend time and efforts on maintaining SQL Server like backups, patches, high availability, etc. One of the major limitation in this is that the existing applications are required to be rewritten to able to work on SQL Azure.

During initial stages when the SQL Azure service was introduced, there were lot of limitations, so was not used much, but as in 2015, the offerings have increased a lot and can support many applications to move their data to SQL Azure and use it without much issues. However there are still many limitations, when compared to on-premise SQL Server instances, which almost does not have any limitations.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Introduction to SQLAzure for SQL Server DBAs

SQLServerF1

Microsoft has been aggressively focussing on promoting cloud technology. As a SQL Server DBA, one might wonder what is all about this cloud and how this works and how this impacts their role as a DBA. Although the terminology may be different, but a lot about cloud may already known to you or worked on, but may be not able to correlate to what you already know. For SQL Server Microsoft is offering two cloud platforms, one of which is Infrastructure as a service and the other one is database as a service.

Infrastructure as a service – This is similar like a hyper-v or VMWare VM, where you have a VM machine on which you install and manage SQL Server instances, databases and jobs, etc. The only difference is the VMWARE or Hyper-V management is taken care by your client company or your company, where in case of Microsoft Azure cloud the infrastructure is taken care by Microsoft and as a DBA, we need to take care of installing SQL Server, patching, maintenance, administration similar to what we used to do, but just on a Microsoft data centre.

Database as a service – This might be something different and which many DBAs may not be familiar about. In this the OS, Network, Storage and also SQL Server installation, patching, Backups, etc are taken care by Microsoft and we as DBAs are not responsible for such tasks, instead we can focus on other tasks such as migrating data from on-premise SQL Server to SQL Azure cloud and checking and working on making the SQL Server database resilient for performance. Database as a service is not a regular SQL Server instance which we used to manage on-premise, instead there are lot of limitations on what we can do and what changes we can make, for example, we cannot change many instance settings directly, we cannot alter storage configuration, or tempdb configuration, etc, instead we focus more at the database level and at data level.

If you are wondering what are the advantages for choosing SQLZure cloud solution is mainly reduction in cost of maintaining hardware and SQL Server maintenance of patches/backups, etc. Depending on the criticality of our database server and application, we can choose different kind of licensing based on our requirement of performance, data recovery and Disaster recovery features. So, for small test/dev servers you can choose servers with basic or minimal cost configuration and for productions servers depending on the size and usage of the database we can choose appropriate license. Different types of licensing includes, Basic, Standard and Premium and these are sub divided into S0-S1-S2-S3 for Standard and P1-P2-P3 for Premium.

As our data is stored on cloud on third party vendor place, it is important to understand how quickly we can recover our data and how much of data loss can occur in case there is a disaster, for which there are different types of Disaster recovery strategies to choose from, which include Geo-Restore, Standard Geo-Replication, Active Geo-Replication. In Geo-Restore, a copy of database can be restored on another region, but this will have data older than 24 hours, thus may not be good option for production data, instead can be used for dev. In Standard Geo-Replication, we can recover data up to 30 minutes before crash and can take up to 2 hours for the restore to complete and database to be available, but this will increase the cost. Finally, Active Geo-Replication, the data loss could be reduced to 5 minutes and amount of time to restore would about about an hour, this further increases the cost. Depending on our requirement, we can choose the best solution that suits.

in SQLZure, there is something known as DTU(Database Throughput Unit), which is used to measure the performance we get out of our SQLZure instance. DTU is a combined measure of CPU, Memory and IO of a database on a server and we can use this to compare the performance of database between different servers.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Microsoft Windows Azure Error Codes from HTTP status code 400 to 400

SQLServerF1

Windows Azure Error code: ShareNotFound
Windows Azure HTTP status code: Not Found (404)
The specified share does not exist.
Windows Azure Error code: ShareAlreadyExists
Windows Azure HTTP status code: Conflict (409)
The specified share already exists.
Windows Azure Error code: ShareDisabled
Windows Azure HTTP status code: Forbidden (403)
The specified share is disabled by the administrator.
Windows Azure Error code: ShareBeingDeleted
Windows Azure HTTP status code: Conflict (409)
The specified share is being deleted. Try operation later.
Windows Azure Error code: DeletePending

Windows Azure HTTP status code: Conflict (409)
The specified resource is marked for deletion by an SMB client.
Windows Azure Error code: DirectoryNotEmpty
Windows Azure HTTP status code: Conflict (409)
The specified directory is not empty.
Windows Azure Error code: ParentNotFound
Windows Azure HTTP status code: Not Found (404)
The specified parent path does not exist.
Windows Azure Error code: SharingViolation
Windows Azure HTTP status code: Conflict (409)
The specified resource may be in use by an SMB client.
Windows Azure Error code: CannotDeleteFileOrDirectory

Windows Azure HTTP status code: Conflict (409)
The file or directory could not be deleted because it is in use by an SMB client.
Windows Azure Error code: FileLockConflict
Windows Azure HTTP status code: Conflict (409)
A portion of the specified file is locked by an SMB client.
Windows Azure Error code: ReadOnlyAttribute
Windows Azure HTTP status code: Conflict (409)
The specified resource is read-only and cannot be modified at this time.
Windows Azure Error code: ClientCacheFlushDelay
Windows Azure HTTP status code: Internal Server Error (500)
The specified resource state could not be flushed from an SMB client in the specified time.
Windows Azure Error code: InvalidFileOrDirectoryPathName
Windows Azure HTTP status code: Bad Request (400)
File or directory path is too long.
Windows Azure Error code: InvalidFileOrDirectoryPathName
Windows Azure HTTP status code: Bad Request (400)
File or directory path has too many subdirectories.

Above are list of Microsoft Windows Azure Status and FILE service Error Codes and Error Messages or Warning messages from HTTP status code 400 to 400 received while performing certain operation against Microsoft Windows Azure or related products.

What are Microsoft Windows Azure General Error Messages?

Microsoft Windows Azure is Microsoft’s operating system for cloud computing, which is intended to simplify IT management and minimize up-front and ongoing expenses. Microsoft Windows Azure cloud platform is ranked by Gartner as an industry leader for both infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS). This powerful combination of managed and unmanaged services lets you build, deploy and manage applications any way you like for unmatched productivity.

There may be errors received while using Microsoft Windows Azure which include errors like Common REST API Error Codes, Blob Service Error Codes, Queue Service Error Codes, Table Service Error Codes, File Service Error Codes, etc.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Microsoft Windows Azure Error Messages or Warning Messages on Windows Azure Operating Systems.

 

Microsoft Windows Azure Error Codes from HTTP status code 400 to 400

SQLServerF1

Windows Azure Error code: PropertyNameTooLong
Windows Azure HTTP status code: Bad Request (400)
The property name exceeds the maximum allowed length.
Windows Azure Error code: PropertyValueTooLarge
Windows Azure HTTP status code: Bad Request (400)
The property value is larger than the maximum size permitted.
Windows Azure Error code: TableAlreadyExists
Windows Azure HTTP status code: Conflict (409)
The table specified already exists.
Windows Azure Error code: TableBeingDeleted

Windows Azure HTTP status code: Conflict (409)
The specified table is being deleted.
Windows Azure Error code: TableNotFound
Windows Azure HTTP status code: Not Found (404)
The table specified does not exist.
Windows Azure Error code: TooManyProperties
Windows Azure HTTP status code: Bad Request (400)
The entity contains more properties than allowed.
Windows Azure Error code: UpdateConditionNotSatisfied

Windows Azure HTTP status code: Precondition Failed (412)
The update condition specified in the request was not satisfied.
Windows Azure Error code: XMethodIncorrectCount
Windows Azure HTTP status code: Bad Request (400)
More than one X-HTTP-Method is specified.
Windows Azure Error code: XMethodIncorrectValue
Windows Azure HTTP status code: Bad Request (400)
The specified X-HTTP-Method is invalid.
Windows Azure Error code: XMethodNotUsingPost
Windows Azure HTTP status code: Bad Request (400)
The request uses X-HTTP-Method with an HTTP verb other than POST.

Above are list of Microsoft Windows Azure Status and Table service Error Codes and Error Messages or Warning messages from HTTP status code 400 to 400 received while performing certain operation against Microsoft Windows Azure or related products.

What are Microsoft Windows Azure General Error Messages?

Microsoft Windows Azure is Microsoft’s operating system for cloud computing, which is intended to simplify IT management and minimize up-front and ongoing expenses. Microsoft Windows Azure cloud platform is ranked by Gartner as an industry leader for both infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS). This powerful combination of managed and unmanaged services lets you build, deploy and manage applications any way you like for unmatched productivity.

There may be errors received while using Microsoft Windows Azure which include errors like Common REST API Error Codes, Blob Service Error Codes, Queue Service Error Codes, Table Service Error Codes, File Service Error Codes, etc.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Microsoft Windows Azure Error Messages or Warning Messages on Windows Azure Operating Systems.

 

Microsoft Windows Azure Error Codes from HTTP status code 400 to 400

SQLServerF1

Windows Azure Error code: DuplicatePropertiesSpecified
Windows Azure HTTP status code: Bad Request (400)
A property is specified more than one time.
Windows Azure Error code: EntityAlreadyExists
Windows Azure HTTP status code: Conflict (409)
The specified entity already exists.
Windows Azure Error code: EntityTooLarge
Windows Azure HTTP status code: Bad Request (400)
The entity is larger than the maximum size permitted.
Windows Azure Error code: HostInformationNotPresent

Windows Azure HTTP status code: Bad Request (400)
The required host information is not present in the request. You must send a non-empty Host header or include the absolute URI in the request line.
Windows Azure Error code: InvalidValueType
Windows Azure HTTP status code: Bad Request (400)
The value specified is invalid.
Windows Azure Error code: JsonFormatNotSupported
Windows Azure HTTP status code: Unsupported Media Type (415)
JSON format is not supported.
Windows Azure Error code: MethodNotAllowed

Windows Azure HTTP status code: Method Not Allowed (405)
The requested method is not allowed on the specified resource.
Windows Azure Error code: NotImplemented
Windows Azure HTTP status code: Not Implemented (501)
The requested operation is not implemented on the specified resource.
Windows Azure Error code: PropertiesNeedValue
Windows Azure HTTP status code: Bad Request (400)
Values have not been specified for all properties in the entity.
Windows Azure Error code: PropertyNameInvalid
Windows Azure HTTP status code: Bad Request (400)
The property name is invalid.

Above are list of Microsoft Windows Azure Status and BLOB service Error Codes and Error Messages or Warning messages from HTTP status code 400 to 400 received while performing certain operation against Microsoft Windows Azure or related products.

What are Microsoft Windows Azure General Error Messages?

Microsoft Windows Azure is Microsoft’s operating system for cloud computing, which is intended to simplify IT management and minimize up-front and ongoing expenses. Microsoft Windows Azure cloud platform is ranked by Gartner as an industry leader for both infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS). This powerful combination of managed and unmanaged services lets you build, deploy and manage applications any way you like for unmatched productivity.

There may be errors received while using Microsoft Windows Azure which include errors like Common REST API Error Codes, Blob Service Error Codes, Queue Service Error Codes, Table Service Error Codes, File Service Error Codes, etc.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Microsoft Windows Azure Error Messages or Warning Messages on Windows Azure Operating Systems.

 

Microsoft Windows Azure Error Codes from HTTP status code 400 to 409

SQLServerF1

Windows Azure Error code: MessageTooLarge
Windows Azure HTTP status code: Bad Request (400)
The message exceeds the maximum allowed size.
Windows Azure Error code: InvalidMarker
Windows Azure HTTP status code: Bad Request (400)
The specified marker is invalid.
Windows Azure Error code: PopReceiptMismatch
Windows Azure HTTP status code: Bad Request (400)

The specified pop receipt did not match the pop receipt for a dequeued message.
Windows Azure Error code: QueueNotFound
Windows Azure HTTP status code: Not Found (404)
The specified queue does not exist.
Windows Azure Error code: MessageNotFound
Windows Azure HTTP status code: Not Found (404)
The specified message does not exist.
Windows Azure Error code: QueueDisabled

Windows Azure HTTP status code: Conflict (409)
The specified queue has been disabled by the administrator.
Windows Azure Error code: QueueAlreadyExists
Windows Azure HTTP status code: Conflict (409)
The specified queue already exists.
Windows Azure Error code: QueueBeingDeleted
Windows Azure HTTP status code: Conflict (409)
The specified queue is being deleted.
Windows Azure Error code: QueueNotEmpty
Windows Azure HTTP status code: Conflict (409)
The specified queue is not empty.

Above are list of Microsoft Windows Azure Status and Queue service Error Codes and Error Messages or Warning messages from HTTP status code 400 to 409 received while performing certain operation against Microsoft Windows Azure or related products.

What are Microsoft Windows Azure General Error Messages?

Microsoft Windows Azure is Microsoft’s operating system for cloud computing, which is intended to simplify IT management and minimize up-front and ongoing expenses. Microsoft Windows Azure cloud platform is ranked by Gartner as an industry leader for both infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS). This powerful combination of managed and unmanaged services lets you build, deploy and manage applications any way you like for unmatched productivity.

There may be errors received while using Microsoft Windows Azure which include errors like Common REST API Error Codes, Blob Service Error Codes, Queue Service Error Codes, Table Service Error Codes, File Service Error Codes, etc.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Microsoft Windows Azure Error Messages or Warning Messages on Windows Azure Operating Systems.

 

Azure SQL Database Federation Error Messages From Error 45005 to 45023

SQLServerF1

Error: 45005 Severity: 16 State: 1 Line: 1,
Msg 45005 Level 16 State 1 Line 1,
<statement> cannot be run while another federation operation is in progress on federation <federation_name> and member with id <member_id>
Wait for the concurrent operation to finish
Error: 45006 Severity: 16 State: 1 Line: 1,
Msg 45006 Level 16 State 1 Line 1,
<statement> operations failed. Foreign key relationships in reference tables referencing federated tables are not allowed in federation members
Unsupported
Error: 45007 Severity: 16 State: 1 Line: 1,
Msg 45007 Level 16 State 1 Line 1,
<statement> operation failed. Foreign key relationships between federate tables must include the federation key column(s).
Unsupported
Error: 45008 Severity: 16 State: 1 Line: 1,
Msg 45008 Level 16 State 1 Line 1,
<statement> operation failed. Federation key data type does not match the column data type
Unsupported

Error: 45009 Severity: 16 State: 1 Line: 1,
Msg 45009 Level 16 State 1 Line 1,
<statement> operation failed. The operation is not supported on filtering connections
Unsupported
Error: 45010 Severity: 16 State: 1 Line: 1,
Msg 45010 Level 16 State 1 Line 1,
<statement> operation failed. Federation key cannot be updated
Unsupported
Error: 45011 Severity: 16 State: 1 Line: 1,
Msg 45011 Level 16 State 1 Line 1,
<statement> operation failed. Federation key schema cannot be updated
Unsupported
Error: 45012 Severity: 16 State: 1 Line: 1,
Msg 45012 Level 16 State 1 Line 1,
Value specified for the federation key is not valid
Value must be in the range that the connection is addressing.
If filtered, the federation key value specified.
If unfiltered, the range covered by the federation member

Error: 45013 Severity: 16 State: 1 Line: 1,
Msg 45013 Level 16 State 1 Line 1,
The SID already exists under a different user name
The SID for a user in a federation member is copied from the SID of the same user account in the federation root. Under certain conditions, the SID may already be in use.
Error: 45014 Severity: 16 State: 1 Line: 1,
Msg 45014 Level 16 State 1 Line 1,
%ls is not supported on %ls
Unsupported operation
Error: 45022 Severity: 16 State: 1 Line: 1,
Msg 45022 Level 16 State 1 Line 1,
<statement> operation failed. Specified boundary value already exists for federation key <distribution_name> and federation <federation_name>
Specify a value that is already a boundary value
Error: 45023 Severity: 16 State: 1 Line: 1,
Msg 45023 Level 16 State 1 Line 1,
<statement> operation failed. Specified boundary value does not exists for federation key <distribution_name> and federation <federation_name>
Specify a value that is not already a boundary value

Above are list of Microsoft Azure SQL Database Federation Error Messages or Warnings from Error 45005 to 45023 received while performing certain operation against Azure Database or related products.

What are Microsoft Azure SQL Database General Error Messages?

SQL Azure is Microsoft’s cloud database services which is based on the SQL Server technology and built on top of Microsoft’s Windows Azure cloud computing platform which serves as Operating System, SQL Azure technology enables organizations to store relational data in the cloud and quickly scale to the size of the databases upside or downside as per their business needs which may change over a period of time.

There may be errors received while using SQL Azure which include errors like General Errors, Database Copy Errors, Connection Loss Errors, Federation Errors, etc.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Azure SQL Database Federation Error Messages or Warning Messages on Windows Azure Operating Systems.

 

Azure SQL Database Federation Error Messages From Error 266 to 45004

SQLServerF1

Error: 266 Severity: 16 State: 1 Line: 1,
Msg 266 Level 16 State 1 Line 1,
<statement> statement not allowed within multi-statement transaction
Check that trancount is 0 on the connection before issuing the statement
Error: 2072 Severity: 16 State: 1 Line: 1,
Msg 2072 Level 16 State 1 Line 1,
Database ‘%.*ls’ does not exist
Check sys.databases for the database state before issuing USE FEDERATION
Error: 2209 Severity: 16 State: 1 Line: 1,
Msg 2209 Level 16 State 1 Line 1,
%s Syntax error near ‘%ls’
FEDERATED ON can only be used when creating tables in federation members.

Error: 2714 Severity: 16 State: 1 Line: 1,
Msg 2714 Level 16 State 1 Line 1,
There is already an object named ‘%.*ls’ in the database
Federation name already exists
Error: 10054 Severity: 20 State: 1 Line: 1,
Msg 10053 Level 20 State 1 Line 1,
A transport-level error has occurred when receiving results from the server. An established connection was aborted by the software in your host machine
Implement retry logic in your application
Error: 40530 Severity: 15 State: 1 Line: 1,
Msg 40530 Level 15 State 1 Line 1,
<statement> needs to be the only statement in the batch
Ensure that no other statements are in the batch

Error: 40604 Severity: 16 State: 1 Line: 1,
Msg 40604 Level 16 State 1 Line 1,
Could not CREATE DATABASE because it would exceed the quota of the server
Expand the server db count quota
Error: 45000 Severity: 16 State: 1 Line: 1,
Msg 45000 Level 16 State 1 Line 1,
<statement> operation failed. Specified federation name <federation_name> is not valid
Federation_name does not comply with federation name rules or is not a valid identifier
Error: 45001 Severity: 16 State: 1 Line: 1,
Msg 45001 Level 16 State 1 Line 1,
<statement> operation failed. Specified federation name does not exist
Federation name does not exist
Error: 45002 Severity: 16 State: 1 Line: 1,
Msg 45002 Level 16 State 1 Line 1,
<statement> operation failed. Specified federation key name <distribution_name> is not valid
Non-existent or invalid federation key
Error: 45004 Severity: 16 State: 1 Line: 1,
Msg 45004 Level 16 State 1 Line 1,
<statement> operation failed. Specified value is not valid for federation key <distribution_name> and federation <federation_name>
USE FEDERATION:Use a boundary value that is in the domain of the federation key data type, or that is not NULL.
ALTER FEDERATION SPLIT: Use a valid value in the domain of the federation key that is not already an existing split point
ALTER FEDERATION DROP: Use a valid value in the domain of the federation key that is already a split point

Above are list of Microsoft Azure SQL Database Federation Error Messages or Warnings from Error 266 to 45004 received while performing certain operation against Azure Database or related products.

What are Microsoft Azure SQL Database General Error Messages?

SQL Azure is Microsoft’s cloud database services which is based on the SQL Server technology and built on top of Microsoft’s Windows Azure cloud computing platform which serves as Operating System, SQL Azure technology enables organizations to store relational data in the cloud and quickly scale to the size of the databases upside or downside as per their business needs which may change over a period of time.

There may be errors received while using SQL Azure which include errors like General Errors, Database Copy Errors, Connection Loss Errors, Federation Errors, etc.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Azure SQL Database Federation Error Messages or Warning Messages on Windows Azure Operating Systems.

 

Azure SQL Database Connection Loss Error Messages From Error 10928 to 40613

SQLServerF1

Error: 10928 Severity: 20, State: 1 Line: 1,
Msg 10928 Level 20 State 1 Line 1,
Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637.
The Resource ID indicates the resource that has reached the limit. For worker threads, the Resource ID = 1. For sessions, the Resource ID = 2.
Error: 10929 Severity: 20, State: 1 Line: 1,
Msg 10929 Level 20 State 1 Line 1,
Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again later.
The Resource ID indicates the resource that has reached the limit. For worker threads, the Resource ID = 1. For sessions, the Resource ID = 2.
Error: 40197 Severity: 17 State: 1 Line: 1,
Msg 40197 Level 17 State 1 Line 1,
The service has encountered an error processing your request. Please try again. Error code %d.
You will receive this error, when the service is down due to software or hardware upgrades, hardware failures, or any other failover problems. The error code (%d) embedded within the message of error 40197 provides additional information about the kind of failure or failover that occurred. Some examples of the error codes embedded within the message of error 40197 are 40020, 40143, 40166, and 40540.
Reconnecting to your SQL Database server will automatically connect you to a healthy copy of your database. Your application must catch error 40197, log the embedded error code (%d) within the message for troubleshooting, and try reconnecting to SQL Database until the resources are available, and your connection is established again.
Error: 40501 Severity: 20 State: 1 Line: 1,
Msg 40501 Level 20 State 1 Line 1,
The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d.
Error: 40544 Severity: 20 State: 1 Line: 1,
Msg 40544 Level 20 State 1 Line 1,
The database has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions.
Error: 40549 Severity: 16 State: 1 Line: 1,
Msg 40549 Level 16 State 1 Line 1,
Session is terminated because you have a long-running transaction. Try shortening your transaction.
Error: 40550 Severity: 16 State: 1 Line: 1,
Msg 40550 Level 16 State 1 Line 1,
The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction.
Error: 40551 Severity: 16 State: 1 Line: 1,
Msg 40551 Level 16 State 1 Line 1,
The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce the temporary table space usage.
If you are using temporary objects, conserve space in the TEMPDB database by dropping temporary objects after they are no longer needed by the session.

Error: 40552 Severity: 16 State: 1 Line: 1,
Msg 40552 Level 16 State 1 Line 1,
The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction.
If you perform bulk inserts using the bcp.exe utility or the System.Data.SqlClient.SqlBulkCopy class, try using the –b batchsize or BatchSize options to limit the number of rows copied to the server in each transaction. If you are rebuilding an index with the ALTER INDEX statement, try using the REBUILD WITH ONLINE = ON option.
Error: 40553 Severity: 16 State: 1 Line: 1,
Msg 40553 Level 16 State 1 Line 1,
The session has been terminated because of excessive memory usage. Try modifying your query to process fewer rows.
Reducing the number of ORDER BY and GROUP BY operations in your Transact-SQL code helps reduce the memory requirements of your query.

Error: 40613 Severity: 17 State: 1 Line: 1,
Msg 40613 Level 17 State 1 Line 1,
Database ‘%.*ls’ on server ‘%.*ls’ is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of ‘%.*ls’.

Above are list of Microsoft Azure SQL Database Connection Loss Error Messages or Warnings from Error 10928 to 40613 received while performing certain operation against Azure Database or related products.

What are Microsoft Azure SQL Database General Error Messages?

SQL Azure is Microsoft’s cloud database services which is based on the SQL Server technology and built on top of Microsoft’s Windows Azure cloud computing platform which serves as Operating System, SQL Azure technology enables organizations to store relational data in the cloud and quickly scale to the size of the databases upside or downside as per their business needs which may change over a period of time.

There may be errors received while using SQL Azure which include errors like General Errors, Database Copy Errors, Connection Loss Errors, Federation Errors, etc.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Azure SQL Database General Error Messages or Warning Messages on Windows Azure Operating Systems.

 
1 2