Deleting old data won't reduce Windows Azure SQL Database usage

My Windows Azure SQL Database usage keeps increasing. Deleting old data didn't help much. I was wondering how to figure out the distribution of the usage. All tables in my DB should not occupy more than 5GB and now it is most 12GB. Please help!
http://yanflex.com

Hello,
The database fee is amortized over the month and charged daily. The daily fee depends on the peak size that each database reached that day and the maximum number of databases you use. So, if the peak size of database is 12 GB and then you delete data
to reduce the size, it still charge based on 12GB this day.
You can use the following statement to get the database size:
SELECT SUM(reserved_page_count)*8.0/1024 as DBsizeinMB
FROM sys.dm_db_partition_stats;
Reference:Accounts and Billing in Windows Azure SQL Database
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Similar Messages

Adding Windows Azure SQL Database to Virtual network

Hi Azure team,
Is there any provision available in Azure to map the SQL Azure database to Azure virtual network?
Scenario:
Azure virtual netowrk has been already created. Worker role can be add to that network. Likely to add the SQL Azure database to that network.
Is it possible? Pleade let us the stpes to do it.
Thanks,

You cannot add a SQL Database to an Azure Virtual Network, see
http://msdn.microsoft.com/en-US/library/windowsazure/dn133803.aspx

Windows Azure SQL Databases Statistics Best practices

ON SQL Azure is it a good practice to have Statistics auto-update disabled? or otherwise.
Pl do not compare Azure to on premise SQL Engine.. Those who have worked on Azure know what i mean..
It is a pain to maintain the indexes specially if they are have BLOB Type Columns.. No Index online rebuilds are allowed in Azure. I was targetting statistics as i see the data being frequently updated.. so maybe i can have the developers update the stats
as soon as they do major update/insert or i can have a job that can do it on weekly basis if i turn off the suto stats update.
I execute a Stats FULLSCAN Update every week, but i think it is overwritten by the Auto update stats .. So Now back to my question does anyone have any experience with turning off stats on Azure.. (any Benefits)

You can't disable auto stats in WASD. They're on by default and have to stay that way.
Rebuilding indexes is possible, but you have to be careful how you approach it. See my blog post for rebuilding indexes:
http://sqltuna.blogspot.co.uk/2013/10/index-fragmentation-in-wasd.html
As a rule I wouldn't have LOB columns as part of an index key - is that what's causing you issues?
Statistics work the same as on-premises, in that they are triggered when a certain threshold of changes is reached (or some other triggers). That's not a bad thing though, as it means they're up to date. Is there any reason you think this is
causing you issues?

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.

Consistently getting "The wait operation timed out" when connecting to Azure SQL Database from a virtual instance...

I have a web app that is backed by a an Azure SQL Database. The problem is that I had multiple issues when connecting to the database mainly when trying to establish a connection, or timeouts. This is the log I just encountered when trying to use the web
app.
[Win32Exception (0x80004005): The wait operation timed out]
[SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21970; handshake=1; ]
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +671
System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +116
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1012
System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +6712291
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +152
System.Data.SqlClient.SqlConnection.Open() +229
System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +102

Hi Affar2k,
According to your description, we need to verify if there is no network issue and the Sqlclient version is older than .NET 4.5. You can try to connect to the Windows Azure SQL database via SSMS and check if it can run well. When you
connect to the SQL Azure database via ADO.NET, you need to verify that the server name and passwords are right in the connection string.
For more information, you can review the following article about how to connect to Windows Azure SQL Database using ADO.NET.
http://msdn.microsoft.com/en-us/library/windowsazure/ee336243.aspx
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Migrating from Azure SQL Database to SQL Server VM

I'm looking for steps/documentation to migrate a database from Azure SQL Database to SQL Server VM in the cloud. I want to make an app whose data is initially hosted in the former. Due to a few reasons, I might have to migrate to SQL Server VM. I'd
like to design the app such that ideally there is no downtime. Looking for guidance...

You can create bacpac file from Azure SQL database and Restore this bacpac file into SQL Server VM or any other place.
Please refer below URL for more details:
http://blogs.msdn.com/b/mast/archive/2013/03/04/different-ways-to-backup-your-windows-azure-sql-database.aspx
dharampal sikhwal

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.

How can I delete old data in citadel

How can I delete old data from Citadel so that HDD is not full when data is continously being logged in the database ?

Hi there,
I could see different possible ways to limit the database size on a LabVIEW DSC system.
a) You could limit the lifespan of your logged data to a certain time by adjusting the option 'Days to keep historical data' in the Tag Configuration Editor>Configure>Historical... tab.
b) You could use the Citadel Database VIs. Archive Database.vi would allow you to archive a database or a part (certain traces/tags, or certain time interval) to another location. With the archive option 'destructive', it would delete the source of the data from the original database.
Delete Traces.vi would delete a traces from a database.
c) The same/similar functionality you can have throught the Measurement and Automation Explorer and its Historical Data Viewer plug-in
b) and c) are NEW features of LabVIEW DSC 6.1!
Hope this helps
Roland
PS: There is a nice link about archiving Citadel on ni.com :
http://zone.ni.com/devzone/conceptd.nsf/webmain/2F24997EAD7C53A686256B6E00686D64?opendocument&node=DZ52101_US

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.

Can No Longer Connect to Azure SQL Databases

As of this morning, I am no longer to connect to any of my Azure SQL databases by any (apparent) means. I checked the configuration in the azure portal and my IP address is listed as an allowed IP, however:
I am unable to connect via SQL Server Management Studio
My request times out when attempting to visit https://{server_name}.database.windows.net
What might have caused this?

Hi ,
Thanks for posting here.
To resolve the issue you can try the following steps (in that order):
                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.
                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).
                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 the previous steps do not resolve your problem, follow these 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.
Please write back with the exact Error message/ Error Code if this doesn't help.
Regards,
Shirisha Paderu.

Best size for VM SQL Server for a start or maybe Azure SQL Database?

Hello Everyone,
My question is quite general but some of You may have already considered similar issues. Let's say or assume I have the website and mobile application - social kind - used by:
1. 10 K users
2. 100 K users
3. 1 K K users
4. 20 K K users MAX
I am strongly considering use of VM SQL Server mostly because of its PARTITIONING functionality, some advantages in the context of INDEXING compared to Azure SQL Database and JOBs availibility.
Question: what would be the best size and count of VMs related to SQL Server for the start and later?
Question 2 - I am able to move JOBs functionality to my Worker role if I wanted to consider use of Azure SQL Database. SQL Server still has at least those 2 advantages (Partitioning, better Indexing) - is it worth considering Azure SQL Database service for
100 K users and more?
Regards,

Hello Jambor,
Considering the number of users i wouldnt recommend an Azure SQL database, because of certain limitations like Max worker threads, Max sessions, etc. Also the maximum size of the database can be 500GB.
Please refer http://msdn.microsoft.com/en-us/library/azure/dn741336.aspx and http://msdn.microsoft.com/en-us/library/azure/dn369873.aspx for the Azure SQL database options and limitations.
If your application needs to scale-out, Azure SQL Databases are recommended. If it needs scaling-up - then the choice is SQL Server on Azure VM. Please refer http://azure.microsoft.com/blog/2012/06/26/data-series-sql-server-in-windows-azure-virtual-machine-vs-sql-database/
and http://azure.microsoft.com/en-us/documentation/articles/data-management-azure-sql-database-and-sql-server-iaas/ for comparison.
If you already have your application running successfully on your on-premise server, you could use a similar machine on Azure for hosting your SQL server instance. The options are at http://azure.microsoft.com/en-us/pricing/details/virtual-machines/. You could
start with a SQL Server enterprise edition on an A3 VM and then scale-up as needed.
Regards,
Kumar Bijayanta

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

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

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

Deleting old data won't reduce Windows Azure SQL Database usage

Similar Messages

Maybe you are looking for